Accounting in a CICS DB2 environment: Overview
Accounting in a CICS® DB2® environment can be used to analyze the transactions being executed in the system, and to charge back the total amount of resources consumed for a given set of transactions to a well-defined set of users. The user can be a real user, groups of users, transactions, or any other expression for the unit to which the resources must be appointed.
Typically the units of consumption include the processor, I/O, and main storage in some weighted proportion. A typical CICS transaction that accesses DB2, consumes resources in the operating system, the CICS system, the application code, and the DB2 address spaces. Each of these components can produce data, which can be used as input to the accounting process. You can combine the output from the different sources to create a complete picture of resource usage for a transaction.
A typical requirement of an accounting procedure is that the results calculated are repeatable, which means that the cost of a transaction accessing a set of data is be the same whenever the transaction is executed. In most cases, this means that the input data to the accounting process must also be repeatable.
- Decide the types of DB2 accounting data to use in your accounting process (processor usage, I/O, calls, and so on). Accounting information provided by the DB2 accounting facility tells you about the accounting data that you can obtain from the DB2 accounting facility.
- Decide how you are going to relate the data from the DB2 accounting record for each transaction to the CICS performance class data for that transaction, to create a complete picture of resource usage for the transaction. Relating DB2 accounting records to CICS performance class records tells you how you can match up the two types of data.
- Decide whether you are going to relate the CICS performance records and the DB2 accounting records for each transaction back to the specific user, or whether you are going to 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. Strategies to match DB2 accounting records and CICS performance class records and charge resources back to the user gives suggestions for when each method is most appropriate.