How CICS PA builds the DB2 report

CICS PA processes CMF performance data from multiple CICS® systems along with associated DB2® Accounting data, correlating the data by network unit-of-work. For each network unit-of-work with DB2 activity, CICS PA attempts to match each DB2 Accounting record to a CMF task.

In the DB2 List report, a data line is presented for each CMF performance class record (column format), and a block of data lines is presented for each associated DB2 Accounting record (row format). Records that are part of the same network unit-of-work are printed sequentially in groups separated by blank lines. A network unit-of-work will only be presented if it involved some DB2 activity, that is, at least one CMF record is present with DB2 Request Count greater than zero (DB2REQCT>0).

The DB2 List report is presented in the same sequence as the Cross-System Work report so you can correlate the two reports. Also, the printed information allows you to find the corresponding records in the CICS PA Performance List report and the DB2 PM reports.

Two summary reports (Long Summary and Short Summary) offer a summary of the CMF performance and DB2 Accounting data presented in the DB2 List report. The data is collated by APPLID, transaction and program for CMF data, and additionally by SSID and plan for DB2 data. Generally there is only one DB2 plan per APPLID/transaction/program combination, but it is possible for there to be more than one (via Dynamic Plan Switching), or for multiple plans to be used over time (via Dynamic Plan Selection, or system modification). Only DB2 Accounting data that matches a single CMF task is accumulated for the summary reports. There is no attempt to statistically apportion DB2 Accounting data that represents more than one CMF task.

The DB2 report is produced from the following process:
  1. Record Selection. CMF performance records that are part of a network unit-of-work that involves DB2 activity are selected. Associated DB2 Accounting records are selected. See CMF-DB2 record selection.
  2. Sort. The selected records are sorted using an EXTERNAL sort process. See Sorting the CMF-DB2 records.
  3. Group by Network UOW. Records are grouped by network unit-of-work NETNAME and network unit-of-work ID.
  4. Match CMF-DB2 Records within Network UOW. For each network unit-of-work, DB2 Accounting records are matched (where possible) to CMF tasks. See Matching CMF-DB2 records for a Network UOW.
  5. Report/Summarize.
    • If requested, the DB2 List report is produced. For each network unit-of-work, one line is presented per CMF performance class record followed by the DB2 Accounting data for that network unit-of-work.
    • If requested, the DB2 Summary reports accumulate statistics for each APPLID, transaction, and program combination. Then the DB2 statistics are accumulated for each SSID and plan used by the APPLID/transaction/program. The Summary reports are produced after the List report (if requested) is complete.