Strategies to match DB2 accounting records and CICS performance class records and charge resources back to the user

There is not one ideal way of matching DB2 accounting records and CICS performance class records. In a few cases, it might be impossible to make the matching correct, because transactions are being run concurrently. In most situations however, there are strategies that you can use to match up the two types of records with reasonable accuracy.

If the resources used in the individual transaction are the basis for accounting, then when you have matched up the CICS performance records and the DB2 accounting records, you can relate them back to the specific user. Alternatively, you can define and calibrate a number of model transactions, measure these transactions in a controlled environment, and count only the number of model transactions executed by each user.

The two main factors that determine what strategies you should use are:
  • Whether each CICS transaction ID represents only one possible transaction path (and so it always represents the same amount of resources consumed), or whether many different transaction paths share the same CICS transaction ID (so it can represent different amounts of resources consumed.
  • Whether each DB2 accounting record relates to only one transaction or a part of one transaction (because you have taken one of the measures described in Controlling the relationship between DB2 accounting records and CICS performance class records), or whether it contains information about more than one transaction.
Figure 1 shows how these factors combine to create four typical scenarios that you might encounter when matching DB2 accounting records and CICS performance class records. The following sections suggest strategies for matching the records in each case, and for charging the resources used back to the user.
Figure 1. Different accounting scenarios
Case A is where there is one transaction in each DB2 accounting record, and each transaction path has its own transaction ID. Case B is where there are many transactions in each DB2 accounting record, and each transaction path has its own transaction ID. Case C is where there is one transaction in each DB2 accounting record, and many different transaction paths share the same transaction ID. Case D is where there are many transactions in each DB2 accounting record, and many different transaction paths share the same transaction ID.


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