When you execute an OpenTP1 operation command, information such as the times of command execution and termination are output to cmdlog1 and cmdlog2 in $DCDIR/spool/cmdlog, cmdlog1 and cmdlog2 wrap around when the size of data exceeds 1 MB.

You can use an editor such as vi to view cmdlog1 and cmdlog2. Because the times when a command starts and ends are output in a command log, you can measure the length of time required to execute the command.

Information is output in the following format:

> AAAA BBBB C DDDD/DD/DD EE:EE:EE.EEEEEE FFFFFFFF : GGGGGGGG : HHHHHHH

>

Command log record start identifier. This symbol indicates the beginning of a line in the command log.

AAAA

Process ID of the executed command, in one-byte numerics

BBBB

User ID of the person who executed the command

C

Message sequence number in the process (sequence number of the command log information that is output by the executed command process). This is a one-byte number from 0 to 65,535. If the number exceeds 65,535, numbering starts again at 0.

DDDD/DD/DD

Date when information is output to the command log in the YYYY/MM/DD format, in one-byte numerics

EE:EE:EE.EEEEEE

Time when information is output to the command log in the HH:MM:SS.mmmmmm format, in one-byte numerics. mmmmmm indicates a value in microseconds.

FFFFFFFF

Command line information at the time the command was executed. A command executed internally in OpenTP1 may be output here.

GGGGGGGG

Identification information, which is one of the following:

start

Information on starting the command.

end

Information on termination of the command.

info

Maintenance information generated during command execution

HHHHHHH

Maintenance information for the command

To acquire command logs for MCF-related operation commands, you need to assign a value to an environment variable. For details of which commands require the environment variable to be set, see Table 12-1. To set the environment variable:

• When executing operation commands manually
  While logged in as an OpenTP1 system administrator, set the following environment variable:
  Variable: DCMCFCMDLOG
  Value: Y
  If you do not assign a value to this environment variable, or assign a value other than Y, command logs will not be acquired.
  
• When executing operation commands automatically
  In environments where operation commands are executed by issuing the dc_adm_call_command function from a UAP running on OpenTP1, add the following line to the user service definition of the relevant UAP, or to the user service default definition.
  

  putenv DCMCFCMDLOG Y

  If you do not assign a value to the environment variable, or assign a value other than Y, command logs will not be acquired. The same applies to commands executed through COBOL and DML interfaces.
  

Note the following regarding the acquisition of command logs for MCF-related operation commands:

• If a UAP or shell file executes a large number of commands concurrently, a bottleneck might develop in the command log output, reducing system performance. Do not set the DCMCFCMDLOG environment variable if this is likely to occur.
• If an operation command results in an error, a command log may be acquired for that command regardless of the setting of the DCMCFCMDLOG environment variable.