RMF report example: execution time is greater than response time

The following report shows an example of a work manager state section for the CICSPROD service class.

In the example, there is a response time of .091 seconds, but an execution time of .113 seconds. The example also shows 1731 ENDED transactions, yet the EXCTD field shows that only 1086 transactions have been executed.

Figure 1. Execution time greater than response time
 REPORT BY: POLICY=HPTSPOL1  WORKLOAD=PRODWKLD  SERVICE CLASS=CICSPROD RESOURCE GROUP=*NONE   PERIOD=1 IMPORTANCE=1
                                          
 -TRANSACTIONS--   TRANS.-TIME   HHH.MM.SS.TTT
 AVG        0.00   ACTUAL                   91
 MPL        0.00   EXECUTION               113
 ENDED      1731   QUEUED                    0
 END/S      1.92   R/S AFFINITY              0
 #SWAPS        0   INELIGIBLE                0
 EXCTD      1086   CONVERSION                0
 AVG ENC    0.00   STD DEV                  92
 REM ENC    0.00
 MS ENC     0.00
 

Possible explanations

Mixed routed and non-routed CICS transactions
The AORs might have recorded states which account for more time than the average response time of all the transactions. The non-routed transactions do not show up in the EXE phase. In addition, most non-routed transactions end very quickly and decrease the actual response time. The response time (ACTUAL field) shows 0.091 seconds as the average of all 1731 transactions, while the AORs can only describe the execution of the 1086 transactions they participated in.

Possible actions

Classify routed and non-routed transactions to different service classes
If you classify routed and non-routed transactions separately, the numbers will be consistent with the expectation.


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