TP1/Client/J outputs error trace information to the directory specified in the TrcPath argument of the setErrorTraceMode method or the directory specified in the dcerrtracepath operand of the TP1/Client/J environment definition; the file names are DCERR1.TRC and DCERR2.TRC. You specify the file size with the size argument of the setErrorTraceMode method or the dcerrtracesize operand of the TP1/Client/J environment definition.

For an error trace, the errors detected by TP1/Client/J are recorded in the files in message format. If an error occurs during method execution, its cause is reported as an exception, but this information may not be sufficient to identify the cause. An error trace provides detailed error information in the file; you can use this information to determine the cause of an error.

A memory trace is a facility for storing error information in the String array specified in the setTraceArray method when you use a Java applet for which an error trace cannot be collected. In the event of an error, you can obtain error information by referencing the String array.

The output format of an error trace file or the format of data stored in a String array for a memory trace is as follows:

 
(ttt)yyyy/mm/dd hh:mm:ss.uuu eeeeeeeeeeee
 

• ttt: Name of the executing thread
• yyyy/mm/dd hh:mm:ss.uuu: Date and time the error trace or memory trace was collected
• eeeeeeeeeeee: Message

The following table lists the messages that are collected.

Table 2-42 Messages collected in error and memory traces

Message	Description
Invalid message received. method=aaaaaaaa	An invalid message was received from the TP1/Server. aaaaaaaa: Name of the method that issued this message. For a memory trace, this is a code corresponding to the name of the method that issued this message.
Error reply received. inf=aaaaaaaa, method=bbbbbbbb	An error reply was received from the TP1/Server. aaaaaaaa: Received error code bbbbbbbb: Name of the method that issued this message. For a memory trace, this is a code corresponding to the name of the method that issued this message.
Exception occurred. inf=aaaaaaaa, exception=bbbbbbbb(cc...cc), method=dddddddd	An exception was received from the Java system in the TP1Client class. Or, an exception was returned to the Java applet, application, or servlet from the TP1Client class. aaaaaaaa: Maintenance information when the exception occurred. bbbbbbbb: Name of the exception that was received from Java or that was returned to the Java applet, application, or servlet. For a memory trace, this is a code corresponding to the name of the exception. cc...cc: Detailed message for the exception. This information is output only when there is a detailed message. dddddddd: Name of the method that issued this message. For a memory trace, this is a code corresponding to the method name.
Invalid data received. (aa...aa), method=bbbbbbbb	The cltAssemReceive method received invalid data from the remote system. aa...aa: Invalid data When the message length is invalid receive message length=message-length (decimal) bbbbbbbb: Name of the method that issued this message. For a memory trace, this is a code corresponding to the name of the method that issued this message.
Receiving message was canceled. aaaaaaaa (bb...bb) method=cccccccc	The message received by the cltAssemReceive method from the remote system was discarded. aaaaaaaa: Reason for discarding the message bb...bb: Data detail When the receive buffer overflowed receive buffer overflowed. (receive buffer size=receive-buffer-size (decimal), receive message body length=receive-message-body-length (decimal) cccccccc: Name of the method that issued this message. For a memory trace, this is a code corresponding to the name of the method that issued this message.
User data did not compress, group=aa...aa, service=bb...bb, reason= cc...cc	User data was not compressed. The service request is issued without compressing the user data. aa...aa: Target service group name bb...bb: Target service name cc...cc: Reason why the user data was not compressed: NO EFFECT: Compressing the user data would have no effect. NOT SUPPORT VERSION: The target TP1/Server version does not support the data compression facility. If NO EFFECT is displayed, the size of the data obtained after compression exceeds the size of the uncompressed data. In such a case, check to see if this message has been output more than once for the same CUP, and re-evaluate the use of the data compression facility for each CUP. If NOT SUPPORT VERSION is displayed, check whether the target TP1/Server version supports the data compression facility (TP1/Server Base 03-03 or later).

The following table lists the method names that correspond to the codes that are output to a memory trace.

Table 2-43 Correspondence of codes to method names

Code	Method name
1	TP1Client.openConnection
2	TP1Client.closeConnection
3	TP1Client.rpcCall
4	TP1Client.setDccltinquiretime
5	TP1Client.setDccltdelay
6	TP1Client.setDcwatchtim
7	TP1Client.setDcselint
8	TP1Client.setDccltextend
9	TP1Client.rpcOpen
10	TP1Client.rpcClose
11	TP1Client.setRpcextend
12	TP1Client.setDchost
13	TP1Client.rpcCallTo
14	TP1Client.trnBegin
15	TP1Client.trnChainedCommit
16	TP1Client.trnChainedRollback
17	TP1Client.trnUnchainedCommit
18	TP1Client.trnUnchainedRollback
19	TP1Client.trnInfo
20	TP1Client.getTrnID
37	TP1Client.cltAssemSend
38	TP1Client.cltAssemReceive
100	TP1ClientSocketCommunicator.openConnection
101	TP1ClientSocketCommunicator.closeConnection
102	TP1ClientSocketCommunicator.sendData
103	TP1ClientSocketCommunicator.sendData
104	TP1ClientSocketCommunicator.recvData
105	TP1ClientSocketCommunicator.recvData
106	TP1ClientSocketCommunicator.recvDummyData
107	TP1ClientSocketCommunicator.flush
108	TP1ClientSocketCommunicator.recvSelect
109	TP1ClientSocketCommunicator.openServerSocket
110	TP1ClientSocketCommunicator.acceptServerSocket
111	TP1ClientSocketCommunicator.closeServerSocket
112	TP1ClientSocketCommunicator.getServerPort
113	TP1ClientSocketCommunicator.getLocalIPAddress
114	TP1ClientSocketCommunicator.getLocalPort
300	TP1ClientProperties.TP1ClientProperties
301	TP1ClientProperties.TP1ClientProperties
302	TP1ClientProperties.getValue
400	TP1ClientRpc.rpcOpen
401	TP1ClientRpc.cltConnect
402	TP1ClientRpc.rpcCall
403	TP1ClientRpc.rpcClose
404	TP1ClientRpc.cltDisconnect
405	TP1ClientRpc.defAnalyze
406	TP1ClientRpc.rapConnect
407	TP1ClientRpc.rapDisconnect
408	TP1ClientRpc.rapRpcCall
409	TP1ClientRpc.scdRpcCall
410	TP1ClientRpc.setDccltextend
411	TP1ClientRpc.rapMngConnect
412	TP1ClientRpc.rapMngDisconnect
413	TP1ClientRpc.setRpcextend
414	TP1ClientRpc.setDchost
415	TP1ClientRpc.namRpcCall
416	TP1ClientRpc.getHostEntry
417	TP1ClientRpc.getNextEntry
500	TP1ClientConManage.openMngConnection
501	TP1ClientConManage.closeMngConnection
502	TP1ClientConManage.changeMngConnection
503	TP1ClientConManage.getConnection
504	TP1ClientConManage.putConnection
505	TP1ClientConManage.cancelConnection
506	TP1ClientConManage.registCheck
507	TP1ClientConManage.getMngConInfo
512	TP1ClientConManage.getSync
513	TP1ClientConManage.registConnNum
600	TP1ClientConnectionHost.addTP1ClientConnectionHost
601	TP1ClientConnectionHost.removeTP1ClientConnectionHost
602	TP1ClientConnectionHost.removeTP1ClientConnectionHostAll
603	TP1ClientConnectionHost.changeTP1ClientConnectionHost
604	TP1ClientConnectionHost.getConnection
605	TP1ClientConnectionHost.putConnection
606	TP1ClientConnectionHost.addConnection
700	TP1ClientNam.Lookup
900	TP1ClientTrn.trnBegin
901	TP1ClientTrn.trnChainedCommit
902	TP1ClientTrn.trnChainedRollback
903	TP1ClientTrn.trnUnchainedCommit
904	TP1ClientTrn.trnUnchainedRollback
905	TP1ClientTrn.conTrnCall
1001	Socket.Socket
1002	Socket.getInputStream
1003	Socket.getOutputStream
1004	Socket.close
1005	DataInputStream.read
1006	DataInputStream.available
1007	DataInputStream.close
1008	DataOutputStream.write
1009	DataOutputStream.close
1010	InetAddress.getLocalHost
1013	InputStream.read
1014	InputStream.close
1015	OutputStream.write
1016	OutputStream.close
1019	Socket.setTcpNoDelay
1102	TP1ClientSndRcv.cltAssemSend
1103	TP1ClientSndRcv.cltAssemReceive

The following table lists the exception names that correspond to the codes that are output to a memory trace.

Table 2-44 Correspondence of codes to exception names

Code	Exception name
1	ErrInvalidArgsException
2	ErrProtoException
3	ErrNoBufsException
4	ErrNetDownException
5	ErrTimedOutException
6	ErrMessageTooBigException
7	ErrReplyTooBigException
8	ErrNoSuchServiceGroupException
9	ErrNoSuchServiceException
10	ErrServiceClosedException
11	ErrServiceTerminatingException
12	ErrServiceNotUpException
13	ErrNotUpException
14	ErrSyserrAtServerException
15	ErrNoBufsAtServerException
16	ErrSyserrException
17	ErrInvalidReplyException
18	ErrInitializingException
19	ErrServerBusyException
20	ErrTestmodeException
21	ErrSecchkException
22	ErrServiceTerminatedException
23	ErrIOErrException
24	ErrHostUndefException
25	ErrInvalidPortException
26	ErrConnfreeException
29	ErrFatalException
30	ErrSecurityException
31	NumberFormatException
32	EOFException
33	FileNotFoundException
34	SocketException
35	InterruptedIOException
36	ErrNotPoolingException
45	ErrTrnchkException
76	ErrServerTimedOutException
77	ErrClientTimedOutException
78	ErrNotTrnExtendException
79	ErrTrnchkExtendException
80	ErrNetDownAtServerException
81	ErrNetDownAtClientException
84	ErrInvalidMessageException
85	ErrBufferOverflowException
86	ErrCollisionMessageException
1001	IOException
1002	UnknownHostException