Example of producing an Accounting exception report
The example shows the benefits of using exception reporting. It also describes how to produce an Accounting exception report.
Accounting report - without Exception
Assume that you would regularly produce a short Accounting report, such as the following example, and that the report would normally be fairly long.
LOCATION: DSNDB0G OMEGAMON for DB2 Performance Expert (V5R5M0) PAGE: 1-1
GROUP: DSNDB0G ACCOUNTING REPORT - SHORT REQUESTED FROM: NOT SPECIFIED
MEMBER: DB1G TO: NOT SPECIFIED
SUBSYSTEM: DB1G ORDER: PRIMAUTH-PLANNAME INTERVAL FROM: 05/15/15 22:35:07.26
DB2 VERSION: V11 SCOPE: MEMBER TO: 05/15/15 22:56:45.89
PRIMAUTH #OCCURS #ROLLBK SELECTS INSERTS UPDATES DELETES CLASS1 EL.TIME CLASS2 EL.TIME GETPAGES SYN.READ LOCK SUS
PLANNAME #DISTRS #COMMIT FETCHES OPENS CLOSES PREPARE CLASS1 CPUTIME CLASS2 CPUTIME BUF.UPDT TOT.PREF #LOCKOUT
---------------------------------- ------- ------- ------- ------- ------- ------- -------------- -------------- -------- -------- --------
SYSADM 20 0 0.00 0.00 0.00 0.00 0.253473 0.253207 N/P N/P 0.00
'BLANK' 0 20 0.00 0.00 0.00 0.00 0.009828 0.009540 N/P N/P 0
USRT002 7 0 0.00 0.00 1.00 0.00 1:32.664960 1:32.601455 32711.57 8.57 18.14
DSNTEP71 0 7 1.14 0.57 0.57 1.57 46.990679 46.971450 38572.71 1018.14 0
....
If you want to use this Accounting exception report to find out whether the class 1 elapsed time per thread is unacceptably high, you would have to check every entry on every page even though you are not interested in entries that fall within normal bounds.
To save time, you can specify exception thresholds for the class 1 time field per thread, and run Accounting exception reports that show only entries that have exceptionally high values for this field. You can further limit the data by only checking online transactions because you would expect to find a high elapsed time for batch jobs.
In this example transactions have a plan name PLANTRNn and batch jobs have a plan name PLANBATn. The connection ID for the CICS® address space is CICSA.
Access data set member RKO2DATA(DGOETV51) with the IRF and specify the thresholds in the Exception Threshold Field Details panel.
This example specifies that:
- Exceptions are checked for the class 1 elapsed time field ADRECETT.
- The Elapsed Time thresholds are checked for the average value per thread. This means that the value in this field is divided by the number of threads.
- The comparison is
Greater than
. - If the class 1 elapsed time value exceeds three seconds per thread, it is flagged as a warning exception. If it exceeds six seconds per thread, it is flagged as a problem exception.
- Only data with a connection ID of CICSA (CICS transactions) is checked for exceptions.
After you have completed the specifications, press Enter. The exception threshold specification is complete.
Now you can run the Accounting exception report. Remember to specify the name of your Exception Threshold data set for the EXCPTDD ddname in the JCL. Use the following command to produce the report:
⋮
ACCOUNTING
REPORT
EXCEPTION
⋮
Accounting exception report
The following example shows the resulting Accounting exception report.
The exception report is much shorter than the original Accounting report. It only lists transactions with class 1 elapsed times that exceeded the exception threshold, and it flags these transactions as warnings or problems.
If you specify more than one exception threshold, all records that contained any fields that reached an exception threshold value will be listed.
LOCATION: DSNDB0G OMEGAMON for DB2 Performance Expert (V5R5M0) PAGE: 1-1
GROUP: DSNDB0G ACCOUNTING REPORT - SHORT REQUESTED FROM: NOT SPECIFIED
MEMBER: DB1G EXCEPTION TO: NOT SPECIFIED
SUBSYSTEM: DB1G ORDER: PRIMAUTH-PLANNAME INTERVAL FROM: 05/15/15 22:35:07.26
DB2 VERSION: V11 SCOPE: MEMBER TO: 05/15/15 22:56:45.89
PRIMAUTH #OCCURS #ROLLBK SELECTS INSERTS UPDATES DELETES CLASS1 EL.TIME CLASS2 EL.TIME GETPAGES SYN.READ LOCK SUS
PLANNAME #DISTRS #COMMIT FETCHES OPENS CLOSES PREPARE CLASS1 CPUTIME CLASS2 CPUTIME BUF.UPDT TOT.PREF #LOCKOUT
---------------------------------- ------- ------- ------- ------- ------- ------- -------------- -------------- -------- -------- --------
SYSADM 20 0 0.00 0.00 0.00 0.00 0.253473 0.253207 N/P N/P 0.00
'BLANK' 0 20 0.00 0.00 0.00 0.00 0.009828 0.009540 N/P N/P 0
**********************************************************************************************************************************
* TYPE FIELD ID FIELD DESCRIPTION BY VALUE THRESHOLD *
* FIELD QUALIFIER *
* WARNING ADRECETT ELAPSED TIME IN APPLICATION (CLASS 1) TOTAL 5.069463 > 0 *
* *
**********************************************************************************************************************************
LOCATION: DSNDB0G OMEGAMON for DB2 Performance Expert (V5R5M0) PAGE: 2-1
GROUP: DSNDB0G ACCOUNTING REPORT - SHORT REQUESTED FROM: NOT SPECIFIED
MEMBER: DB2G EXCEPTION TO: NOT SPECIFIED
SUBSYSTEM: DB2G ORDER: PRIMAUTH-PLANNAME INTERVAL FROM: 05/15/15 22:47:05.09
DB2 VERSION: V10 SCOPE: MEMBER TO: 05/15/15 22:47:05.09
PRIMAUTH #OCCURS #ROLLBK SELECTS INSERTS UPDATES DELETES CLASS1 EL.TIME CLASS2 EL.TIME GETPAGES SYN.READ LOCK SUS
PLANNAME #DISTRS #COMMIT FETCHES OPENS CLOSES PREPARE CLASS1 CPUTIME CLASS2 CPUTIME BUF.UPDT TOT.PREF #LOCKOUT
---------------------------------- ------- ------- ------- ------- ------- ------- -------------- -------------- -------- -------- --------
USRT002 1 0 0.00 0.00 1.00 0.00 8:59.989315 8:59.871297 45769.00 43.00 62.00
DSNTEP61 0 1 0.00 0.00 0.00 1.00 2:47.027856 2:47.010331 270.0K 1429.00 0
**********************************************************************************************************************************
* TYPE FIELD ID FIELD DESCRIPTION BY VALUE THRESHOLD *
* FIELD QUALIFIER *
* WARNING ADTDDL TOTAL SQL DDL STATEMENTS TOTAL 0 < 1 *
* *
**********************************************************************************************************************************⋮