Nonstop Database, HiRDB Version 9 UAP Development Guide
When an error occurs during communication between a client and the HiRDB server or in the XA interface specified by X/Open, error information is collected as a client error log in a client error log file.
When the current client error log file becomes full, a new file is swapped in and the oldest information in that file is overwritten.
You can collect client error logs by specifying appropriate values in PDCLTPATH and PDUAPERLOG in the client environment definitions. For details about client environment definition, see 6.6 Client environment definitions (setting environment variables).
The two client error log files in which information is to be collected are created under a specified directory. The files that are created depend on whether or not an X/Open-compliant API (TX_function) is used.
The following table shows the relationship between use of an X/Open-compliant API (TX_ function) and the error log files that are created.
Table 11-3 Relationship between use of an X/Open-compliant API (TX_ function) and error log files that are created
Use of TX_function | Client error log files that are created |
---|---|
No | pderr1.trc and pderr2.trc |
Yes | pderrxxxxx-1.trc and pderrxxxxx-2.trc |
Client error log information is output whenever an error occurs during SQL statement execution, during communication, and during execution of an X/Open-compliant XA interface function.
An example of client error log information that is output is shown below, followed by an explanation of the output items.
If the client error log file becomes full while client error log information is being output, HiRDB stops writing to that file and resumes output of client error log information to the other client error log file. Any information that already exists in the switched-in client error log file is overwritten (beginning with the oldest information) by the new client error log information. To prevent information from being lost by overwriting, you should copy the contents of the client error log file into a backup file whenever execution of a UAP is completed.
To determine the client error log file that is being used currently, check the most recent update dates/times of files. The client error log file that was updated most recently is the current file.
For a Windows edition HiRDB client, you use the dir command or the Explorer to check the file update dates/times.
For a UNIX edition HiRDB client, you use the OS's 1s -1 command to check the file update dates/times.
All Rights Reserved. Copyright (C) 2011, Hitachi, Ltd.