RMF report example: response time breakdown data is all zero

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

The RESP TIME (%) field shows a 0.0 value.

Figure 1. Response time breakdown percentages all 0.0

 REPORT BY: POLICY=HPTSPOL1  WORKLOAD=PRODWKLD SERVICE CLASS=CICSLONG  RESOURCE GROUP=*NONE  PERIOD=1 IMPORTANCE=1

                                                            CICS Long Running Internal Trxs
 
 -TRANSACTIONS--  TRANS.-TIME   HHH.MM.SS.TTT.SS.TTT
 AVG        0.00  ACTUAL                           0
 MPL        0.00  EXECUTION                        0
 ENDED         0  QUEUED                           0
 END/S      0.00  R/S AFFINITY                     0
 #SWAPS        0  INELIGIBLE                       0
 EXCTD         0  CONVERSION                       0
 AVG ENC    0.00  STD DEV                          0
 REM ENC    0.00
 MS ENC     0.00

            RESP  -------------------------------STATE SAMPLES BREAKDOWN (%)---------------   ---------STATE---
 SUB    P   TIME  --ACTIVE-- READY IDLE  ----------------------------WAITING FOR----------------   SWITCHED SAMPL (%)
 TYPE        (%)   SUB  APPL             CONV  I/O  PROD  DIST  REMT  LOCK                         LOCAL SYSPL REMOT
 CICS  BTE   0.0  70.8   0.0   1.4  0.7  11.2  9.2   0.3   5.3   1.2   0.0                          11.2   0.0   0.0
 CICS  EXE   0.0  43.2   0.0   0.2  0.1  31.8  10.4  8.7   0.0   2.9   2.8                           0.0   0.0   0.0

Possible explanations

No transactions completed: While a long-running or never-ending transaction is being processed, RMF stores the service class state samples in SMF 72.3 records. But when no transactions have completed, the average response time is 0. However, the calculations for the state samples breakdown will result in values greater than 0.
RMF did not receive data from all systems in the sysplex: The postprocessor might have been given SMF records from only a subset of the systems running in the sysplex. The report might 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, on this MVS image.

Possible actions

Do nothing: You might have created this service class to prevent the state samples of long-running transactions from distorting data for your production work.
Combine all SMF records for the sysplex: When a single MVS image that does not have TORs is combined with another MVS image that does have TORs and therefore does report response times, the states and response time from the first image will be combined by RMF with the states and response time from the second.