The DB2 Interface

The DB2 Interface provides a mechanism for:

accounting for DB2 system usage
adding DB2 charges to your CA JARS reports

DB2 accounting trace produces that class 1 accounting data that is used to assess and charge DB2 costs. The SMF type 101 records record this data. DB2 does not produce accounting data by default. To specify which accounting data DB2 trace can produce, see the IBM DB2 Installation Guide or Updating DB2 Install and Migration Parameters as described in DB2 System Planning and Administration Guide. In either case, specify the following parameters:

YES for TRACE AUTO START. This action assures that the accounting trace is automatically invoked when DB2 is started.
YES for SMF accounting.

Once these parameters are set, 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.

Compressed SMF Type 101 records that are decompressed and the DB2 Extract Program (JSZS0000) processes these records. This program is an additional optional feature of the report writer. To activate this program, code a Y (yes) in position 37 of the OPTION statement. In order to avoid multiple passes on the SMF data, activate the exit 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:

definitional SQL statements usage (CREATE, DROP, and ALTER) by application programs
the use of the 32-KB buffer pool
DB2 lock contention

The RECFM is FB, the LRECL is 372, and the default BLKSIZE is 2976. BLKSIZE can 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, remove the DD statement; 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.

Important! Before 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 a database access is included in the SMF record type 30.

This section contains the following topics:

Distributed Sample Source Code

JARSDB21: Debit Record Creation

JARSDB22: Sample Report