Requirements for combining CICS and Db2 data

UIE provides an option to process CICS and Db2 data and match the transactions in CICS to the Db2 transactions that executed on behalf of CICS.

When the input data is processed, UIE matches CICS and Db2 records based on the CICS Unit-of-Work ID (UOWID) that is contained in the Db2 and CICS data. The resulting applications that are created for the XML profile contain information about the CICS and Db2 resources that were consumed by the application.

Related topic

Working-with-UIE

For UIE to match CICS and Db2 transactions, the Db2 trace data must contain the CICS UOWID. When Db2 accounting trace is active, Db2 begins collecting data at successful thread allocation and writes the completed record when the thread terminates. In the case of CICS, threads can be reused by authorized transactions. The thread terminates when no additional authorized transactions are waiting for the thread.

If threads are reused, one accounting record might contain data for many transaction occurrences, and the UOWID would not be usable. However, Db2 can write an accounting record for each thread use. The ACCOUNTREC parameter tells the CICS Db2 attachment facility to do the following actions:

  • Write an accounting trace record for each transaction occurrence, regardless of thread reuse.
  • Passes the CICS UOWID to Db2 and records it in the Db2 accounting trace data.

When ACCOUNTREC is active, UIE can collect and report on the number of Db2 transaction occurrences. If Unit-of-work ID matching is requested, UIE can also match a CICS transaction to the Db2 transaction that executed on its behalf.

If a CICS transaction calls Db2, the application CPU in the CICS transaction data includes CICS application CPU, and the CPU used by a Db2 thread on behalf of the CICS transaction. 

If UIE matches a CICS transaction to a Db2 transaction, the Db2 CPU is subtracted from the original USRCPUT value to avoid double counting the Db2 CPU. The Class 1 CPU in the CICS transaction record in the Visualizer file contains only CICS CPU and a separate Db2 transaction record will contain the Db2 Class 1 CPU. If the CICS-Db2 matching is turned off or does not occur due to missing UOWID values or missing Db2 data, the Class 1 CPU in the CICS transaction record in the Visualizer file will contain the original USRCPUT value.  

In the UIE Summary report, the Unit-of-work ID Summary report shows the number of transactions that matched in a unit-of-work. The SETOPTION UOWIDMSG command can request that UIE produce an error message when the CICS-Db2 unit-of-work ID matching percentage is below 50%.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*