Interpreting data entries for the RW component of trace job

 

The RW component of the i5/OS^® licensed program includes most of the Distributed Relational Database Architecture™ (DRDA^®) support.

RW component produces certain types of diagnostic information when the Trace Job (TRCJOB) command is issued with TRCTYPE(*ALL) or TRCTYPE(*DATA). RW trace points can be located easily by doing a find operation using the string >> as the search argument.

The end of the data dumped at each trace point can be determined by looking for the <<<... delimiter characters. There are one or more of the < delimiter characters at the end of the data, enough to fill out the last line. Figure 1. An example of job trace RW component information

DATA   FF  6E6ED9E6D8E840D9C37A0016D052000100102205000611490000  *>>RWOQ RC:  }             *
DATA   FF  0006210224170025D0530001001F241A0C76D00500023100030A  *        }        }        *
DATA   FF  00080971E0540001D000010671F0E00000002CD0530001002624  *    \   }   0\    }       *
DATA   FF  1BFF0000000100F1F1F14110000000000000FF0000000200F2F2  *       111             22 *
DATA   FF  F241200000000000000026D05200010020220B00061149000400  *2         }               *
DATA   FF  162110C4C2F2C5E2E8E240404040404040404040400056D00300  *   DB2ESYS            }   *
DATA   FF  01005024080000000064F0F2F0F0F0C4E2D5E7D9C6D54000C4C2  *  &      02000DSNXRFN  DB *
DATA   FF  F2C5E2E8E24040404040404040404040FFFFFF92000000000000  *2ESYS             k       *
DATA   FF  0000FFFFFFFF0000000000000000404040404040404040404000  *                          *
DATA   FF  0000004C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C4C  *   <<<<<<<<<<<<<<<<<<<<<< *
 

There is an exception to the use of the < delimiters to determine the end of data. In certain rare circumstances where a received data stream is being dumped, the module that writes the trace data is unable to determine where the end of the data stream is. In that case, the program dumps the entire receive buffer, and as a warning that the length of the data dumped is greater than that of the data stream, it replaces the <<<... delimiter with a string of ( characters.

Following the >> prefix is a seven-character string that identifies the trace point. The first two characters, RW, identify the component. The second two characters identify the RW function being performed. The QY indicates the query function which corresponds to the DDM commands OPNQRY, CNTQRY, and CLSQRY. The EX indicates the EXECUTE function which corresponds to the DDM commands EXCSQLSTT, EXCSQLIMM, and PRPSQLSTT.

Which program module corresponds to each of these functions depends on whether the job trace was taken at the application requester (AR) end of the distributed SQL access operation, or at the application server (AS) end. The modules performing the process and query functions at the AR are QRWSEXEC and QRWSQRY. The modules at the AS are QRWTEXEC and QRWTQRY.

The last two characters of the seven-byte trace point identifier indicate the nature of the dumped data or the point at which the dump is taken. For example, SN corresponds to the data stream sent from an AR or an AS, and RC corresponds to the data stream received by an AR.

• Example: Analyzing the RW trace data
  This discussion examines the elements that make up the data stream in the example.

• Description of RW trace points
  This topic collection discusses the RW trace points.

 

Parent topic:

Interpreting trace job and first-failure data capture data

 

Related reference

Trace Job (TRCJOB) command