Accounting CLASS 2 processor time

For accounting CLASS 2, the timer is checked on every entry and exit from DB2 to record the 'IN DB2' time in the SMF type 101 record. In this case, it is the difference that is stored in the record. The field in the SMF type 101 record used for accounting CLASS 2 processor time is QWACAJST.

In Figure 1 and Figure 2, CLASS 2 is the sum of the times 2, 5, and 8.

For a description of the contents of the DB2 statistics records, see the DB2 for z/OS: Application Programming Guide and Reference for Java.

The elapsed time (start and end times between the defined points) is also reported in the SMF type 101 record (QWACASC).

When CICS is connected to DB2 there can be a significant difference between CLASS 1 and CLASS 2 processor time, as there is for IMS and TSO. This is because when CICS is connected to DB2, the CLASS 1 processor time includes processor time spent in the CICS-DB2 attachment facility, including trace calls, and also includes processor time spent running threadsafe application code and threadsafe CICS commands on the open TCB. All this processor time occurs in the CICS address space, and so is not reported for accounting CLASS 2. The CLASS 2 processor time itself is not affected by the open transaction environment.

Unlike accounting CLASS 1, the CLASS 2 elapsed times and processor times accurately reflect the elapsed times and processor times spent 'IN DB2'. Accounting CLASS 2 information is therefore very useful for monitoring the performance of SQL execution. However, the processor overhead associated with having class accounting is quite considerable.

To reduce the overhead, it was usually recommended that the CLASS 2 trace be limited to trace data for plans and locations of specific authorization IDs. The processor overhead is 0-5%, with 2% being typical.



dfhtkc0085.html | Timestamp icon Last updated: Sunday, 4 June 2017