The online tester collects the same UAP trace information as OpenTP1. However, trace information specific to the online tester (tester information) can also be collected at the entrance to each OpenTP1 function.

To collect tester information, perform one of the following:

• Specify target or simmhp in the test_mode operand of the user service definition, or specify usable and activate the UAP in test mode.
• Specify 1 or a higher value in the uap_trace_max operand of the user service definition (or omit specification).
• Activate the UAP for which traces are to be collected by executing the OpenTP1 dcsvstart command or by specifying dcsvstart in the user service configuration definition.

Trace information is grouped by the online tester and output to a trace file at the times shown below. Tester information is output once only when the trace information is output to the trace file.

• At the start of the dc_rpc_mainloop function
• At the start of the dc_mcf_mainloop function
• At the start of the dc_rpc_call function
• At completion of the dc_rpc_close function
• At completion of an RPC service function
• At the start of the tpcall function
• At the start of the tpacall function
• At the start of the tpconnect function
• At completion of an XATMI service function

When the information for a group fills the UAP trace area, the information is output to the trace file. The UAP trace area is then reused from the beginning.

A trace file is created for each OpenTP1 system and for each test user ID. Therefore, if a number of UAPs that output trace information are executed in parallel, the UAP trace information is mixed and difficult to check. Parallel execution also results in waiting for release of locks and a timeout condition may occur before a reply can be made to a service request. For these reasons, parallel execution should be avoided when using the online tester.

A swap message is output when the size of one of the two trace files exceeds the value specified in the max_trace_file_size operand of the tester service definition. UAP traces are then collected in the other trace file. When both trace files are full, no further UAP trace information can be collected.

To prevent this situation, the user must copy the full trace file to another file when the swap message is output, and then delete the full trace file. If the second trace file subsequently becomes full, create a new file, specifying the name of the deleted trace file, and continue collecting trace information.

Do not delete a trace file while traces are still being collected. Deletion during trace collection means that no further information can be collected.

Note also that trace information for the dc_trn_info function is not collected.