As an aid to handling possible UAP errors, OpenTP1 collects a log of the library functions used by the UAP. This information shows which functions returned an error and which resources the UAP attempted to access. By editing and outputting this information, the user can analyze the cause of UAP errors and then correct the UAP or rebuild the system. This facility is called the UAP trace facility.

UAP traces are collected for each SUP, SPP, or MHP process.

If either of the following files is available when a UAP terminates abnormally, the UAP traces are automatically edited and output to that file.

• UAP trace data file
• Core file

If a UAP terminates abnormally and a core file exists, the UAP trace is automatically edited and output to a file. The user can edit and output the UAP trace to the standard output by using the uatdump command of TP1/Server Base. See Subsection 15.2.2 UAP trace output methods for details of the uatdump command.

UAP traces can also be collected when using an online or offline tester to test a UAP. Such information is useful for analyzing the processing flow in a UAP test.

For the online tester, UAP traces are collected for TP1/Server Base. For the offline tester, specialized trace information is collected.