Using data in the Db2 accounting record to identify the corresponding CICS performance class records

Use fields in Db2® accounting records to identify the corresponding CICS® performance records.

About this task

The fields in the Db2 accounting records that you might want to use are as follows:
  • The CICS LU6.2 token. If you specify either ACCOUNTREC(TASK) or ACCOUNTREC(UOW) in the DB2ENTRY or DB2CONN, CICS passes its LU6.2 token to Db2 to be included in the Db2 trace records. The token is written to QWHCTOKN in the correlation header. The presence of this token makes matching the two sets of records much more simple.
  • The thread correlation ID, which contains the CICS 4-character transaction ID. Remember that if you have not specified ACCOUNTREC(TASK) or ACCOUNTREC(UOW), the Db2 accounting record might contain information about more than one transaction that used this ID. If you have specified ACCOUNTREC(TASK) or ACCOUNTREC(UOW), the Db2 accounting record might only contain part of a transaction (a single UOW), and you need to locate the other records relating to the transaction. If different types of CICS transaction use the same transaction ID, you cannot make a positive identification from this item alone.
  • The authorization ID field. As for the thread correlation ID, the Db2 accounting record might contain information about more than one transaction that used this authorization ID, or it might only contain part of a transaction. The authorization ID that a CICS transaction uses is determined by the AUTHID or AUTHTYPE parameter in the DB2CONN or DB2ENTRY. If different types of CICS transaction use the same authorization ID, you cannot make a positive identification from this item alone
  • The timestamp fields. The start and end time for the thread can help identify the CICS transactions that the Db2 accounting record covers.