TP1/Client/J normally collects debug trace information in its memory buffer and outputs the information to a debug trace file only when an exception occurs. TP1/Client/J outputs a debug trace to the TP1ClientJ directory under the home directory of the user executing the Java VM; the file name is dcCltXXXXXXXXXXXX.dmp (where XXXXXXXXXXXX is a time stamp).

When a debug trace file is to be output, if the total number of debug trace files exceeds the file count specified in the dccltdbgtrcfilecount operand of the TP1/Client/J environment definition, the file with the oldest update date is deleted. The existing debug trace files are deleted until the total number of debug trace files reaches (file-count-specified-in-the dccltdbgtrcfilecount-operand - 1).

If debug traces cannot be output to files, such as when a CUP is operated as a Java applet or when the deletion of old debug trace files fails, debug traces are output to the standard output. When debug trace files are output to the standard output, you can view the debug trace information by opening the Java console using a browser facility, for example.

The output format of a debug trace is as follows:

 
(ttt)yyyy/mm/dd hh:mm:ss.uuu MethodName = nnnnnnnnnnnnnnnnnnnn(ii) Location = lll
ADDRESS +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +a +b +c +d +e +f 0123456789abcdef
00000000 00 00 00 00 c7 0b 49 17 00 00 00 00 00 06 00 05 ......|.........
 

• ttt: Thread ID
• yyyy/mm/dd hh:mm:ss.uuu: Date and time the debug trace was collected
• nnnnnnnnnnnnnnnnnnnn: Name of the executing thread
• ii: Instance ID
• lll: Type of entry or exit point

Character string following ADDRESS: Debug trace information