Interpreting the Accounting report and making changes

An example of a short Accounting report is evaluated and key fields are emphasized.

Short Accounting report

The output from your short Accounting report could look similar to the following report:



   LOCATION: STM4D61Y                  OMEGAMON FOR DB2 PERFORMANCE EXPERT (V5R5M0)                    PAGE: 1-1
      GROUP: N/P                                 ACCOUNTING REPORT - SHORT                      REQUESTED FROM: NOT SPECIFIED
     MEMBER: N/P                                                                                            TO: NOT SPECIFIED
  SUBSYSTEM: Y71Y                                                                                INTERVAL FROM: 02/14/15 10:20:09.30
DB2 VERSION: V11                                                                                            TO: 02/14/15 10:20:09.30

ELAPSED TIME SPENT IN APPLICATION                                 TOP NUMBER REQUESTED:     20       

                                   
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
---------------------------------- ------- ------- ------- ------- ------- ------- -------------- -------------- -------- -------- --------
JUSTIN                                   6       0    0.00    0.00    0.00    0.00    2:01.610942    1:05.002506 10553.33   272.00     6.83 
 JUSDOIT3                                0      12    2.00    1.00    1.00    1.00    1:06.879690      39.838561  2585.33   140.80        0
                                        
 JUSTIN                                  6       1    0.00    0.00    0.00    0.00    1:51.610942    2:02.005506   993.53    84.33     3.51 
 JUSDOIT1                                0       8    3.00    1.00    1.00    1.00      56.879690      56.838591  3985.37   240.50        0 
                                        
 JUSTIN                                  6       0    0.00    0.00    0.00    0.00    1:24.096142      42.125542 12285.31    84.33     8.63
 JUSDOIT2                                0      12    2.00    1.00    1.00    1.00      45.687990      38.746239  3958.38   240.50        0
                                        
 ANDREW                                  1       0    0.00    0.00    0.00    0.00    1:10.506675    1:09.849935 11822.00    84.33     3.00
 AWSPLAN3                                0       2    2.00    1.00    1.00    1.00    1:03.779540    1:03.737837  3084.00   270.00        0
                                        
 ANDREW                                  6       0    0.00    0.00    0.00    0.00    1:01.610942    1:22.057438 10553.33    84.33     1.89
 AWSPLAN1                                0      12    2.00    1.00    1.00    1.00      56.879690      56.838591  3864.34   240.50        0
                                                                                                                                            
 ANDREW                                  5       0    0.00    0.00    0.00    0.00      59.831795      59.233317 10299.60    46.80     0.40
 AWSPLAN1                                0      10    2.00    1.00    1.00    1.00      55.499719      55.458742  2485.60   234.60        0
                                        
  .....
  .....
  
  .....
  .....
    
ACCOUNTING REPORT COMPLETE

In this example, the application with the highest elapsed time is JUSTIN-JUSDOIT3. There are a couple of points of interest for this user application that can give you an idea of what to look for in a more detailed report:

Elapsed times and CPU times
Large differences between class 1 and class 2 times
Synchronous reads
Lock suspensions

All of JUSTIN's applications in this example show similar symptoms. It is also possible that these applications could be affecting other applications. If these problems could be solved, general thread throughput can be improved.

Generate an Accounting trace report to have a closer look at JUSTIN's jobs. Use the same input data to create the report output. The JCL looks like this:

Figure 1. Specifying a job stream using ISPF/PDF editor


EDIT ---- ANDREW.OMPE.JOBS.ACTRALON------------------------- Columns 001 072
Command ===> ________________________________________________ Scroll ===> CSR_
****** ***************************** TOP OF DATA ******************************
0001  /*  JCL to produce an accounting LONG trace report  */
0002  //AWOMPEA JOB  (TTS1,YUS7),'ANDREW', 
0003  //             MSGCLASS=V,CLASS=D,NOTIFY=ANDREW
0004  //        EXEC PGM=FPECMAIN 
0005  //STEPLIB  DD  DSN=OMPE.RKANMOD,DISP=SHR
0006  //INPUTDD  DD  DSN=ANDREW.OMPE.TRACES.TRACE2,DISP=SHR
0007  //DPMOUTDD DD  DSN=ANDREW.OMPE.OUT.ACTRC01,DISP=OVR
0008  //JOBSUMDD DD  SYSOUT=A 
0009  //SYSIN    DD  *  
0010  ACCOUNTING
0011      TRACE
0012        LAYOUT(LONG)
0013        INCLUDE(PRIMAUTH(JUSTIN) PLANNAME(JUSDOIT1 JUSTDOIT2 JUSTDOIT3))
001  EXEC
****** **************************** BOTTOM OF DATA ****************************
 F1=Help     F2=Split    F3=Exit     F5=Rfind    F6=Rchange  F7=Up
 F8=Down     F9=Swap    F10=Left    F11=Right   F12=Cancel