The information about the functions issued by users is output to a UAP trace. The UAP trace lets you check the sequence of the functions issued, the specified values of arguments, and the return values of functions.

A UAP trace is usually output to the CUP executing directory. However, when you specify DCTRCPATH in the client environment definition, the UAP trace is output to the directory specified by DCTRCPATH. No UAP trace is output when the specified directory does not exist.

Whether UAP trace collection is used depends on the specification of DCTRCUAP in the client environment definition. If you specify DCTRCUAP to output a UAP trace, two files (dcuap1.trc and dcuap2.trc) are created. If there is no information to be output, no file is created.

The two files are switched in accordance with the round-robin method, and are output chronologically. Thus, old information is deleted in units of files. If a write exceeds the file size specified for DCTRCUAP in the client environment definition, the files are switched. If a write does not exceed the specified file size at the beginning of the write, the information is output. Thus, the actual file size may be greater than the specified file size.

UAP traces are output in binary format. You must use the command for editing traces (cltdump command or cltdmp32 command) to edit the UAP traces in text format.