RMF report example: large SWITCH percentage in CICS execution phase

The following report shows a work manager state data section for a CICSPROD service class.

The LOCAL value in the SWITCHED SAMPLE(%) section shows a value of 7092.

Figure 1. Large SWITCH precentage in a CICS execution environment

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                  150
 MPL        0.00   EXECUTION               134
 ENDED      3599   ACTUAL                   16
 END/S      4.00   R/S AFFINITY              0
 #SWAPS        0   INELIGIBLE                0
 EXECUTD    2961   CONVERSION                0
 AVG ENC    0.00   STD DEV                 446
 REM ENC    0.00
 MC ENC     0.00

            RESP  ---------------------------RESPONSE TIME BREAKDOWN IN PERCENTAGE--------------   ------STATE------
 SUB    P   TIME  --ACTIVE-- READY  IDLE  ---------------------------WAITING FOR----------------   SWITCHED TIME (%)
 TYPE        (%)   SUB  APPL              MISC  PROD  CONV  I/O                                    LOCAL SYSPL REMOT
 CICS  BTE  26.8K  0.3   0.0   0.4   2.5  96.3   0.0   0.6  0.0                                      0.6   0.0   0.0
 CICS  EXE  93.7  41.2   0.0   6.0   0.0   0.0  52.7   0.0  0.0                                     7092   0.0   0.0

Possible explanations

Distributed transaction processing: If a program initiates distributed transaction processing to multiple back-end regions, there can be many AORs all associated with the original transaction. each of these multiple back-end regions can indicate they are switching control back to the front-end region (SWITCH to another region on the LOCAL MVS image, or to a region on another MVS image in the sysplex). Thus, with a one-to-many mapping like this, there are many samples of the execution phase of requests switched - long enough to exceed 100% of the response time of other work completing in the service class.
Distributed program link (DPL): The distributed program link function builds on the distributed transaction functions available in CICS by enabling a CICS program (the client program) to call another program (the server program) in another CICS region.; While the service program is running, the client program will reflect that it is switched to another CICS region.

There are no possible actions.