RMF report example: response time breakdown data is all zero

Figure 48 shows an example of a work manager state section for the CICSLONG service class. All data shows a 0.0 value.

Figure 48. Response time breakdown percentages all 0.0
 REPORT BY: POLICY=HPTSPOL1  WORKLOAD=PRODWKLD SERVICE CLASS=CICSLONG  RESOURCE GROUP=*NONE  PERIOD=1 IMPORTANCE=HIGH
                                                            CICS Long Running Internal Trxs
 
 -TRANSACTIONS--  TRANSACTION TIME   HHH.MM.SS.TTT
 AVG        0.00  ACTUAL             000.00.00.000
 MPL        0.00  QUEUED             000.00.00.000
 ENDED         0  EXECUTION          000.00.00.000
 END/SEC    0.00  STANDARD DEVIATION 000.00.00.000
 #SWAPS        0
 EXECUTD       0
 
            -------------------------------RESPONSE TIME BREAKDOWN IN PERCENTAGE---------------   ---------STATE---
 SUB    P   TOTAL  ACTIVE  READY  IDLE  ----------------------------WAITING FOR----------------   SWITCHED TIME (%)
 TYPE                                   LOCK  I/O  CONV  DIST LOCAL SYSPL REMOT TIMER PROD MISC   LOCAL SYSPL REMOT
 CICS  BTE   0.0     0.0    0.0    0.0  0.0   0.0  0.0   0.0   0.0   0.0   0.0   0.0   0.0  0.0    0.0   0.0   0.0
 

Possible explanations

There are two possible explanations:

  1. No transactions completed in the interval
  2. RMF™ did not receive data from all systems in the sysplex.

No transactions completed in the interval

While a long-running or never-ending transaction is being processed, RMF saves the service class state samples to SMF Type 72 records, (subtype 3). But when no transactions have completed, (and average response time is 0), the calculations to apportion these state samples over the response time result in 0%.

RMF did not receive data from all systems in the sysplex.

The RMF post processor may have been given SMF records from only a subset of the systems running in the sysplex. For example, the report may represent only a single MVS™ image. If that MVS image has no TOR, its AORs receive CICS® transactions routed from another MVS image or from outside the sysplex. Since the response time for the transactions is reported by the TOR, there is no transaction response time for the work, nor are there any ended transactions.

Possible actions

The following are some actions you could take for reports of this type:

Do nothing

You may have created this service class especially to prevent the state samples of long running transactions from distorting data for your production work. In this case there is no action to take.

Combine all SMF records for the sysplex

The state data is contained in the SMF records. If you combine the data from an MVS image that doesn't have a TOR with another MVS image that does, the state data from the two MVS images is analyzed together by RMF. This ensures that the response time distribution data is no longer reported as zeros.

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: execution time greater than response time
RMF report example: large SWITCH LOCAL Time in CICS execution phase
RMF report example: fewer ended transactions with increased response times
[[ Contents Previous Page | Next Page Index ]]