The following table lists the options that can be specified for the trace files and the output file names.

Table 2-8 Options and names for trace files

Trace file	Options	Where to specify the file destination	Output file name
UAP trace	File output directory Size of trace file	TrcPath argument of the setUapTraceMode method or dcuaptracepath operand	DCUAP1.TRC DCUAP2.TRC
Data trace	File output directory Size of trace file Maximum size of data	TrcPath argument of the setDataTraceMode method or dcdatatracepath operand	DCDAT1.TRC DCDAT2.TRC
Error trace	File output directory Size of trace file	TrcPath argument of the setErrorTraceMode method or dcerrtracepath operand	DCERR1.TRC DCERR2.TRC
Method trace	File output directory Size of trace file	TrcPath argument of the setMethodTraceMode method or dcmethodtracepath operand	DCMTD1.TRC DCMTD2.TRC

TP1/Client/J cannot output a trace file if the specified directory does not exist or if there is no write authority for the specified directory. If the specified target directory does not contain a file with the predefined output file name, TP1/Client/J creates the trace file in the applicable directory. Data is written into a file in the addition mode. TP1/Client/J uses two trace files with the round robin method. When the amount of data exceeds the specified trace file size, TP1/Client/J swaps the files and restarts the write operation from the beginning of the other file.

If you output the trace files for multiple CUPs to the same directory, the trace information for the various CUPs is intermingled, making troubleshooting difficult. For this reason, you should output the trace files for each CUP to a separate directory. Note that the actual size of a trace file may be larger than the specified value depending on the output size of one trace data item.