Correlating and synchronizing accounting records

You can match Db2 accounting records with CICS® or IMS accounting records.

About this task

If a performance problem is outside of Db2, you can check the appropriate reports from a CICS or IMS reporting tool.

When CICS or IMS reports identify a commit, the timestamp can help you locate the corresponding IBM® OMEGAMON® for Db2 Performance Expert on z/OS® accounting trace report.

Procedure

To simplify the task of correlating CICS and Db2 accounting records, use any of the following approaches:

  • For reused threads (protected and unprotected threads), specify ACCOUNTREC(UOW) or ACCOUNTREC(TASK) on the DB2ENTRY RDO definition to help match CICS and Db2 accounting records.
    The CICS LU 6.2 token is included in the Db2 trace records, in field QWHCTOKN of the correlation header.
  • Produce IBM OMEGAMON for Db2 Performance Expert on z/OS accounting reports that summarize accounting records by CICS transaction ID. Use the IBM OMEGAMON for Db2 Performance Expert on z/OS function Correlation Translation to select the subfield that contains the CICS transaction ID for reporting.
  • Set the value of the STATIME subsystem parameter to 1.
    This setting specifies a one-minute interval for statistics collection. The more granular statistics can simplify the task of identifying short term spikes issues. Some records are always written at one-minute intervals, at the beginning of each minute, regardless of the value that you specify.
  • Set the value of the SYNCVAL subsystem parameter to 0.
    This setting synchronizes statistics reporting with the SMF reporting interval, at the beginning of each hour (minute :00).