Figure 48 shows an example of a work manager state section for the CICSLONG service class. All data shows a 0.0 value.
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
There are two possible explanations:
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%.
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.
The following are some actions you could take for reports of this type:
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.
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.