Scenario C: One transaction in each DB2 accounting record, but several types of transaction use the same transaction ID

In this scenario, you know that each DB2 accounting record contains information relating to a single CICS transaction, but because several types of transaction use the same transaction ID, you cannot be sure which type of transaction is shown by a particular DB2 accounting record.

You cannot match up a set of records for one instance of a transaction and then reuse those figures, as you could in Scenario A. You must match all the individual CICS performance records with their corresponding DB2 accounting records. Unless you do this, you cannot know what type of transaction is represented by each DB2 record.

You can match each of the DB2 accounting records to the relevant CICS performance record by using the data items listed in Using data in the DB2 accounting record to identify the corresponding CICS performance class records. If you have specified either ACCOUNTREC(TASK) or ACCOUNTREC(UOW) in the DB2ENTRY or DB2CONN, so that CICS passes its LU6.2 token to DB2, then you can match the records together easily. If not, you must match the records based on their time stamps. In this case, the matching might not be accurate if transactions are being run simultaneously.

You can then use your matched sets of records to charge back the resources used for each transaction, to the user identified by the CICS performance record.



dfhtkc0082.html | Timestamp icon Last updated: Sunday, 4 June 2017