The file that stores abnormal termination information that OpenTP1 collects for each UAP process is called a core file. If UAP abnormally terminates and there is a core file, the UAP trace is automatically edited and output to a file called the UAP trace output file.

Table 15-1 shows the directories and file names of the core file and UAP trace output file.

Table 15-1 Directories and file names of core file and UAP trace output file

Name	Directory	File name
Core file	$DCDIR/spool/save/	server-name-n#
UAP trace output file	$DCDIR/spool/save/	server-name-n.uat#

#: n: Sequence number of the core file (1 to 3)

Note that a sequence number is not assigned to the core file output if OpenTP1 is forcibly terminated (when the dcsvstop -df command is executed or the real monitoring time expires).

Figure 15-2 shows an overview of automatically editing and outputting a UAP trace to a file.

Figure 15-2 Overview of automatic edit and output of UAP trace

When the uatdump command is entered, the UAP trace is edited and output to the standard output. For details on how to use the uatdump command, see Subsection 15.2.3 uatdump (edited output of UAP trace).

Figure 15-3 shows an overview of editing and outputting the UAP trace to the standard output by a command.

Figure 15-3 Overview of editing and outputting UAP trace to standard output by a command