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

Normally, the socket trace is output to the CUP execution 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 socket trace is not output.

Whether socket trace collection is used depends on the DCTRCSOC specification of the client environment definition. The file size also depends on the DCTRCSOC specification of the client environment definition. The data size is specified in DCTRCSOCSIZE of the client environment definition.

When socket trace collection is enabled, two files (dcsoc1.trc and dcsoc2.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 socket trace files are binary files. To convert them into text files, use the cltdump or cltdmp32 command.

The DCTRCSOC entry in the client environment definition determines whether the socket trace collection is enabled. The DCTRCSOC entry in the client environment definition specifies the file size. The DCTRCSOCSIZE entry in the client environment definition specifies the data size.