Scenario A: One transaction in each DB2 accounting record, with its own transaction ID
In this scenario, you know that each DB2 accounting record contains information relating to a single, identifiable CICS transaction. If the transaction accessed DB2 resources more than once, DB2 might have created more than one accounting record for it. You must match the DB2 accounting records relating to the transaction, to the CICS performance record for the transaction.
The user for the transaction can be identified from the CICS performance record. This record contains the CICS activities related to this transaction. You can identify the DB2 accounting records that apply to this transaction by using any of the data items listed in Using data in the DB2 accounting record to identify the corresponding CICS performance class records.
As all these transactions are identical, you can expect that they consume comparable amounts of resources. For accounting purposes, you could create model transactions for each transaction type. Because you can identify which DB2 accounting records apply to which CICS transactions, you can match up the DB2 accounting records and the CICS performance record for one transaction, and then assign the amount of DB2 resources used in those accounting records, to each subsequent transaction of that type. You should validate the correctness of your models on a regular basis, in case the resource usage changes.