dcdefchk [-r] [-l] [-c] [-w] [-e]

The dcdefchk command checks the values specified in the system definition files (including the domain definition file) in the directories that store definitions ($DCCONFPATH and $DCUAPCONFPATH). For details about the items to be checked and the procedure, see 1.3.1 Creation and checking of the system definition.

The command outputs the results of checking the definitions in the form of messages with one of the following indicating the message type labels. Note that some output messages might not be assigned a category.

Labels indicating the message types:

• ERROR: This type of message is output on detection of a problem that prevents OpenTP1 from starting or stopping, or impairs some aspects of OpenTP1 operation.
• WARNG: This type of message is output when a specified value is not the recommended value.
• CHECK: This type of message is output to prompt the user to check the validity of a specified definition.

-r

Outputs a message (KFCA00254-R) asking you whether you want to continue command processing if an error is found during the syntax check of system definition files.

-l

Checks the definitions in the system definition files.

Before using this option, we recommend that you first execute the command dcdefchk command without the -l option. If the command outputs an error message (of type E) at this time, take the appropriate action to resolve it. If you execute the dcdefchk command with the -l option without first resolving such errors, the same error message might be output multiple times.

-c

Disables outputting a CHECK message when a problem is detected in a definition in the system definition files.

-w

Does not output a WARNG message when a problem is detected in a definition in the system definition files.

-e

Does not output an ERROR message when a problem is detected in a definition in the system definition files.

Message ID	Description	Output destination
KFCA00200-E	An unspecifiable option is specified.	Standard error output
KFCA00253-I	The definition check command starts.	Standard output
KFCA00254-R	An error was found in a value specified in the definition.	Standard output
KFCA00255-E	An error occurred during command execution.	Standard error output
KFCA00256-I	Help message	Standard output
KFCA00257-E	A directory that has the same name as a definition file was found.	Standard error output
KFCA00258-I	The applicable definition was treated as the system service definition and the syntax of set-format operands in the system service definition was checked.	Standard output
KFCA00283-W	An error occurred during the definition check.	Standard error output
KFCA00284-W	An insignificant error occurred during the definition check.	Standard error output
KFCA00285-W	A mandatory operand is not specified.	Standard error output
KFCA00286-W	A mandatory definition file does not exist.	Standard error output

Note

In addition to the above messages, the messages KFCA00215-E to KFCA00223-E, KFCA00240-E to KFCA00252-E, and KFCA00259-W to KFCA00282-W might be output, as well as the messages mentioned in the description of definition checks in the manual OpenTP1 System Definition.

• You can execute the dcdefchk command while OpenTP1 is operating. If you do so, the command checks the values specified in the system definition before the command is executed, not the values that are valid for the current operation of OpenTP1. For example, when you use the prcpath command to change the value of prcsvpath specified in the process service definition, the dcdefchk command checks the original value specified in the process service definition.
• The dcdefchk command uses the directory specified in the $DCDIR environment variable as the OpenTP1 directory. The $DCDIR environment variable is set in the environment where the dcdefchk command is to be executed. Therefore, if the directory specified in the $DCDIR environment variable differs from the path name for the OpenTP1 directory set in the environment where the dcstart command is to be executed, the dcdefchk command cannot correctly check definitions.
• If the directory paths specified in $DCCONFPATH and $DCUAPCONFPATH are longer than 50 bytes, only part of a definition file name is output in the message (KFCA00242-E) that is output if an error is found during the syntax check. To avoid this, copy the target definition file to a directory whose path name is 50 bytes or less, specify the copy destination directory in the DCCONFPATH environment variable that is specified in putenv format in $DCDIR/conf/env, and execute the dcdefchk command.
• In the directory for storing definitions, store only the files for which you want to perform a definition check. If you store files other than system definition files and user service definition files under the directories for storing system definitions ($DCCONFPATH and $DCCUAPCONFPATH), the dcdefchk command cannot correctly check definitions. This precaution does not include the directories for storing domain definition files and domain definition files.
• For files other than system service definition files under the directories for storing system definitions ($DCCONFPATH and $DCCUAPCONFPATH), the dcdefchk command does not check files whose names begin with periods (.) and underscores (_) and names that are 9 or more bytes.
• The dcdefchk command only checks the definition of the operands that are listed in the manual OpenTP1 System Definition.
• Do not execute the dcdefchk command at the same time as a command that creates OpenTP1 files (such as jnlinit).
• If a syntax check detects a problem with a value specified for an operand, the logic check will proceed as if the default is specified for that operand.
• The dcdefchk command checks file and directory access permissions based on the UID/GID of the user who executed the command.
• A message may be output during a logic check if the OpenTP1 file system is inaccessible for some reason, such as being in a standby state.
• Some of the messages output by the dcdefchk command during the checking process do not belong to any of the message types associated with the dcdefchk command. For this reason, if you run the dcdefchk command with the -e option specified, messages with the message type E may still be output.
• The dcdefchk command may be unable to check the logic of environment variables (definitions in putenv or dcputenv format) correctly.