|
|
|
The DB2 Interface provides a mechanism for:
The data used to assess and charge DB2 costs is obtained from class 1 accounting data produced by the DB2 accounting trace. This data is recorded by SMF in type 101 records. DB2 does not produce accounting data by default. You must specify that you want accounting data produced using either of the procedures described in the DB2 Install Guide or the procedures for "Updating DB2 Install and Migration Parameters" as described in DB2 System Planning and Administration Guide. In either case, you must specify the following:
Once you have done this, DB2 trace begins collecting accounting data when a thread connects to DB2. DB2 trace writes a completed record when the thread terminates or when the authorization identifier changes.
SMF type 101 records are processed by the DB2 extract program (JSZS0000), an additional optional feature of the report writer that is activated by coding a Y (yes) in position 37 of the OPTION statement. In order to avoid multiple passes on the SMF data, the exit should be activated as part of the routine report program SMF processing procedure. The exit produces two output files; one required and one optional. The required file, ddname CAIJDB2X, contains the DB2 accounting extract for subsequent processing by the Wizard Report Writer All DB2 accounting data elements from the SMF record are included in the extract record. Therefore, you can use it for more than just chargeback accounting. For instance, you can develop your own CA JARS Wizard programs to monitor:
The RECFM is FB, the LRECL is 372, and the default BLKSIZE is 2976. BLKSIZE may be overridden on the DD statement to any acceptable BLKSIZE desired.
The optional file, ddname CAIJDB2P, contains a formatted dump of each DB2 accounting record for problem determination purposes. If not used, the DD statement should be removed; not dummied. The RECFM is VBA, LRECL is 137 and the default BLKSIZE is 1100, but BLKSIZE can be overridden.
The interface uses the Wizard Report Writer to read the DB2 extract file. A CA JARS Wizard glossary, CAWGJRD2, is provided for this purpose. Two sample reports, created using CA JARS Wizard, are also provided with the interface. The report samples shown in this chapter are intended to illustrate the use of CA JARS Wizard not how to charge for DB2 usage.
Caution: Prior to the CICS Transaction Server (CTS) Release 2.2, double billing for CPU Usage occurs if you use SMF record type 30 and the DB2 Interface. CPU time utilization for database access is included in the SMF record type 30.
This section contains the following topics:
Distributed Sample Source Code
JARSDB21: Debit Record Creation
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |