TP1/Client/J outputs method trace information to the directory specified in the TrcPath argument of the setMethodTraceMode method or the directory specified in the dcmethodtracepath operand of the TP1/Client/J environment definition; the file names are DCMTD1.TRC and DCMTD2.TRC. You specify the file size with the size argument of the setMethodTraceMode method or the dcmethodtracesize operand of the TP1/Client/J environment definition.

Many methods are executed within a TP1Client class. A method trace outputs to the file the execution order and times of these internal methods. In a Java environment, only a limited amount of information can be obtained in the event of an error. You can use the method trace information about the internal processing resulting in an error to determine the cause of an error.

The output format of a method trace file is as follows:

 
yyyy/mm/dd hh:mm:ss.uuu Location = lll ThreadName = ttt
MethodName = nnnnnnnnnnnnnnnnnnnn
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 ......|.........
 

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

Character string following ADDRESS: Name of the method that was called