What are the issues when matching DB2 accounting records and CICS performance records?

Because CICS and DB2 have different accounting needs, it is not always easy to match up DB2 accounting records and CICS performance class records.

There are two main issues involved when trying to match these records:
  1. There is not necessarily a one-to-one relationship between the CICS performance class records and the DB2 accounting records. A DB2 accounting record can contain information about one CICS transaction, multiple CICS transactions, or part of a CICS transaction.
  2. The DB2 accounting records do not have a field that matches exactly with the corresponding CICS performance records.

For the purpose of charging resources back to users, it is possible to give each user a different authorization ID from a DB2 viewpoint, by specifying the DB2ENTRY or DB2CONN parameter AUTHTYPE as OPID, USERID, GROUP, or TERM. In this case, a DB2 accounting record is generated that contains data only for the authorization ID. You can then collect together all the DB2 accounting records by authorization ID, and charge the resources consumed directly to the user. This method means that you do not need to match the DB2 accounting records with the CICS performance class records. However, from a usability and performance viewpoint, using OPID, USERID, GROUP, and TERM is not an attractive solution, for the reasons discussed in Controlling users' access to plans. For large networks, specifying these authorization IDs can complicate maintenance and result in performance overhead. It is preferable to plan your use of authorization IDs with performance in mind, and assign DB2 accounting records to the end user by matching them to the CICS performance class records.

This section tells you:
  • What you can do to make the relationship between DB2 accounting records and CICS performance class records more straightforward.
  • What information in a DB2 accounting record can be used to identify the corresponding CICS performance class records.
  • What strategies you can use to match DB2 accounting records and CICS performance class records in four typical scenarios.