Offline tester trace information is collected in a trace file according to the output specifications (output file, content to be output, and so on) set as options at offline tester startup. Collected trace information can be output for each service or service group by executing the utftrcpic command.

The dc_rpc_open function executes the processing, such as opening the trace file, to prepare for trace collection. Therefore, trace information for functions issued before the dc_rpc_open function cannot be collected. Also, trace information cannot be collected for the following simulation functions for DAM file access:

• dc_dam_create
• dc_dam_get
• dc_dam_iclose
• dc_dam_iopen
• dc_dam_put

For a UAP written in COBOL, API trace information may not be output if the request code, DML, or other specification is incorrect. In such cases, the system outputs error message KFCA20016-E or KFCA20018-E. If the DML is incorrect, error information is also output by the COBOL compiler and the program may terminate abnormally.

When UAPs run in parallel during main function execution, for example, each output line may contain mixed trace information. To avoid this problem, activate each service group at a different point.