Accounting in a CICS® DB2® environment
can be used to:
- Analyze the transactions being executed in the system.
- Charge back the total amount of resources consumed for a given
set of transactions to a well-defined set of end users. (For simplification,
the term end user is used in this chapter as the target for charging
resources. The end user can be real end users, groups of end users,
transactions, or any other expression for the unit to which the resources
must be appointed.)
Normally the units of consumption are the processor, I/O, main
storage, and so on, 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 normal 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 should be the same whenever the transaction
is executed. In most cases, this means that the input data to the
accounting process should also be repeatable.
When planning the accounting strategy for your CICS DB2 environment,
you need to:
- 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
end 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 end user. Matching DB2 accounting records and CICS performance class
records to the end user gives suggestions for when
each method is most appropriate.
If you have decided to use processor usage as the basis for your
accounting, Accounting for processor usage in a CICS DB2 environment has more information on the different
classes of processor time that are reported in the DB2 accounting
records, and on how to calculate the total processor time used by
a transaction.
[[ Contents Previous Page | Next Page Index ]]