Scenario D: Several transactions in each DB2 accounting record, and several transaction types use the same transaction ID
In this scenario, each DB2 accounting record can contain information relating to more than one transaction, and also you cannot use the transaction IDs to identify which types of transaction are present in the accounting record.
This situation is best avoided, because you are unlikely to be able to match records accurately. If you do find yourself in this situation, the best solution is to create model transactions, as described for Scenario B. Next, find a way to mark the CICS performance records with an identifier that is unique to each transaction. For example, the user could supply information in a user field in the performance records that identifies the transaction being executed. Now you can use this field to identify which of the model transactions should be used for accounting in this case.