TP1/Client outputs trace information about processing to a file as a module trace. Although the contents of a module trace are not disclosed, maintenance personnel may use them for troubleshooting.

Normally, the module trace is output to the CUP executing directory. However, you can change the destination directory by specifying it in DCTRCPATH of the client environment definition. If the specified directory does not exist, the module trace is not output.

Whether module trace collection may be used depends on the DCTRCMDL of the client environment definition. When module trace collection is enabled, two files (dcmdl1.trc and dcmdl2.trc) are created. However, no files are created until there is information to be output.

Information is chronologically output to the two trace files on a round-robin basis. When the current destination file becomes full, the destination file is switched to the other. When the destination file is switched, the information existing in the new destination file will be deleted. TP1/Client checks the file size immediately before writing a new entry to the file. After the new entry is written, the file size may be larger than the predefined maximum, depending on the size of the new entry.

The module trace files are binary files. To convert them into text files, use the cltdump or cltdmp32 command.

The DCTRCMDL entry in the client environment definition determines whether the module trace collection is enabled.