TP1/Client/J provides a troubleshooting facility that enables you to collect UAP, data, error, memory, method, debug, performance analysis, and performance verification traces.

The facility outputs UAP, data, error, and method traces to files. A memory trace is stored in the String-type array provided by the CUP. A debug trace is collected in the memory of TP1/Client/J. When a method provided by TP1/Client/J returns an exception, its trace is output to a file or to the standard output. A performance analysis trace is output on the Cosminexus Application Server and a performance verification trace is output on the TP1/Server.

For Java applets, the UAP, data, error, method, and performance verification traces are not available due to Java security limitations. Furthermore, a performance analysis trace cannot be collected.

For Java servlets, some traces are not available to some application servers due to security limitations. For details about the security limitations for Java servlets, see the documentation for the applicable application server.

To output traces, you must set the time zone in the TZ environment variable. If this environment variable is not set, the correct time will not be output for trace information.

Organization of this section

2.11.1 Contents of trace files

2.11.2 UAP trace

2.11.3 Data trace

2.11.4 Error trace and memory trace

2.11.5 Method trace

2.11.6 Debug trace

2.11.7 Performance analysis trace