Reconnect trace information can be obtained by setting a value in the PDRCTRACE client environment definition.

HiRDB creates two reconnect trace files in the directory specified in the PDCLTPATH client environment definition. The names of the created files are pdrcnct1.trc and pdrcnct2.trc.

Reconnect trace information is output when the automatic reconnect facility establishes a connection automatically.

An output example of a reconnect trace is shown below.

 
   [1]  [2]                         [3]                                [4]
40004250 S 2004/04/12 11:10:36.766 - 2004/04/12 11:10:41.846 sds:9:23763 => sds:10:23750
40004250 S 2004/04/12 11:11:07.491 - 2004/04/12 11:11:12.547 sds:10:23750 => sds:11:23765
40004850 F 2004/04/12 11:17:58.285 - 2004/04/12 11:18:23.395 sds:14:23751 =>
40005050 S 2004/04/12 11:27:35.098 - 2004/04/12 11:27:40.152 sds:1:24414 => sds:2:24418

Explanation

1. Connection handle value
   The connection handle value that HiRDB manages internally is output in hexadecimal format.
   The value is 8 digits if the client is operating in 32-bit mode or 16 digits if the client is operating in 64-bit mode. The UAP views traces that have the same connection handle value as the same connection.
   In the output example above, 40004250 is output twice as the connection handle value. When viewed from the UAP that uses this connection handle, this information indicates that reconnect processing was executed twice.
   
2. Reconnect result
   The reconnection result is displayed.
   S: Success
   F: Failure
   
3. Reconnect start and end dates and times
   After a disconnection is detected, the dates and times when the reconnection was started and when it ended normally are displayed in milliseconds. If reconnect processing fails, the date and time immediately before control is returned to the UAP is displayed.
   
4. Connection information before and after reconnect
   Connection information for both before reconnect and after reconnect is displayed. The connection information displays the connection server name, the connection sequence number, and the process ID of the connection server, with the items separated by colons.
   If reconnect processing fails, the connection information for after the reconnect is not displayed (becomes blank).
   

The connection information shown under 4 of the output example is output to the PRF trace information of Cosminexus. If the automatic reconnect facility subsequently executes reconnect processing, match the trace information with PRF trace information as follows.

To match trace information with the PRF trace information of Cosminexus:

1. Get the HiRDB connection information in the PRF trace information.
2. In 4 of the reconnect trace file, search for the connection information obtained in Step 1, and get the corresponding connection handle value.
3. From 1 of the reconnect trace file, track the trace information that has the same connection handle value obtained in Step 2. If the same connection handle value is found, and the connection information before reconnect is the same as the connection information after reconnect for the previous instance of the same connection handle, the connection handle can be used for tracking. If the connection information is different, the connection handle cannot be used for tracking because a new connection (DISCONNECT-CONNECT) was established with the connection handle.

If the reconnect log file becomes full while reconnect trace information is being output, the reconnect log is output to the other reconnect trace file. In this case, the old reconnect trace information stored in the takeover reconnect trace file is erased and overwritten by new reconnect trace information. Therefore, if the system is being operated for a long period of time, copy the contents of the reconnect trace file and back up the information, as necessary.

To determine the reconnect trace file that is being used currently, check the most recent update dates/times of the files. The reconnect trace file that was updated most recently is the current file.

For a Windows version HiRDB client, you use the dir command or the Explorer to check the file update dates/times.

For a UNIX version HiRDB client, you use the OS's 1s -1 command to check the file update dates/times.