(a) Overview of UAP traces

Some of the procedures described in 11.2 Troubleshooting procedures involve looking at UAP trace information. A UAP trace is trace information acquired when a function provided by OpenTP1 is invoked. By viewing the UAP trace for an OpenTP1 function, you can find out to what stage the function had progressed before the process of the function stopped. dc_*** (entry) appears in the UAP trace if the process stopped inside the function, and dc_*** (exit) appears if the process stopped outside the function. Consequently, by viewing UAP trace information, you can find out whether the processing stopped inside or outside the function.

(b) Checking UAP trace information

UAP trace information is acquired only when a UAP terminates abnormally. If OpenTP1 is running when the UAP terminates, UAP trace information is output to the file user-server-namen.uat^# in the directory $DCDIR/spool/save.

A UAP trace file is in text format, and can be viewed by a standard editor such as vi. To locate a specific UAP trace, search the trace information file for the PID in the message KFCA01820-E that was output when the UAP terminated abnormally.

UAP trace information may not be output to $DCDIR/spool/save if the entire OpenTP1 system goes down when the user server terminates abnormally. If you are unable to find the UAP trace under $DCDIR/spool/save, look for the core file in the current directory ($DCDIR/spool/tmp/home/user-server-name). If you find the core file, execute the command uatdump core > desired-file-name to edit and output the UAP trace file.

#

n

The generation number of the file.

Some of the procedures described in 11.2 Troubleshooting procedures involve acquiring a stack trace. You can acquire a stack trace as follows:

In UNIX:

Examples are given for AIX and Linux. Because the procedure differs for each OS, see the manual for your operating system.

AIX: Execute dbx load-module-name core-file. Enter where at the prompt to display the stack trace.

Linux: Execute gdb UAP-load-module-name core-file | tee-file-name (optional). At the prompt, enter bt. Press Enter to view more lines. Once you have displayed the entire stack trace, enter q to quit. The stack trace is output to the specified file.

In Windows:

From the Command Prompt, execute the drwtsn32 -i command to ensure that Dr Watson logs (which include stack trace information) are output to the specified folder when a process terminates abnormally. For details, see the manual for the applicable operating system.