RMF report example: execution time greater than response time

Figure 49 shows an example of a work manager state section for the CICSPROD service class. In the example, there are 1731 ENDED transactions yet the EXECUTD field shows that only 1086 have been executed. 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 they participated in, giving an execution time of 0.113.

Figure 49. Execution time greater than response time
 REPORT BY: POLICY=HPTSPOL1  WORKLOAD=PRODWKLD  SERVICE CLASS=CICSPROD RESOURCE GROUP=*NONE   PERIOD=1 IMPORTANCE=HIGH
                                                                CICS Trans not classified singly
 
 -TRANSACTIONS--  TRANSACTION TIME   HHH.MM.SS.TTT
 AVG        0.00  ACTUAL             000.00.00.091
 MPL        0.00  QUEUED             000.00.00.020
 ENDED      1731  EXECUTION          000.00.00.113
 END/SEC    1.92  STANDARD DEVIATION 000.00.00.092
 #SWAPS        0
 EXECUTD    1086
 

Possible explanation

The situation illustrated by this example could be explained by the service class containing a mixture of routed and non-routed transactions. In this case, the AORs have recorded states which account for more time than the average response time of all the transactions. The response time breakdown shown by RMF™ for the execution phase of processing can again show percentages exceeding 100% of the response time.

Possible actions

Define routed and non-routed transactions in different service classes.

Related concepts
Interpreting the RMF workload activity data
RMF report examples:
RMF report example: very large percentages in the response time breakdown
RMF report example: response time breakdown data is all zero
RMF report example: execution time greater than response time
RMF report example: fewer ended transactions with increased response times
[[ Contents Previous Page | Next Page Index ]]