Validate Configuration Files
When you manually edit any of the five text-based IBM® Connect:Direct® configuration files, the Configuration Checking Utility (cfgcheck) enables you to validate these files offline. The following files can be validated using this utility: userfile.cfg, initparm.cfg, netmap.cfg, ndmapi.cfg, and sysacl.cfg.
By default, cfgcheck is run with no arguments and attempts to find all five of the configuration files in the current working directory. If all of the IBM Connect:Direct components are not installed, then some of the files will not be found. For example, if the Command Line Interface (CLI) is installed but the IBM Connect:Direct server is not installed, only the ndmapi.cfg file will exist in the installation directory. Therefore, only the ndmapi.cfg file will be validated. When cfgcheck is run with no arguments, the utility will report that the other configuration files were not found.
To invoke cfgcheck, type the following command at the UNIX prompt:
$ cfgcheck -t -h -f filename.cfg
The cfgcheck command has the following arguments:
|No arguments (default)||When no arguments are specified and the cfgcheck utility is run by a non-root user, it searches the cfg/ directory for the following configuration files: initparm.cfg, netmap.cfg, userfile.cfg, and ndmapi.cfg. When a root user runs cfgcheck, the utility also searches the SACL/ directory to locate the sysacl.cfg file.|
Prints the help screen and exits.
Turns on tracing and prints verbose debug information.
Specifies a configuration file name to validate, where filename is the name of one of the configuration files. You can specify multiple -f arguments. When the -f argument is used, cfgcheck will not automatically search for other configuration files from the file specified.