CICS workload activity reporting

CICS® records the transaction ID, the associated terminal ID, and the elapsed time at the end of each transaction. When more detailed reports are needed, Use the MVS™ Performance Management (MVSPM) component of System Performance feature of Tivoli® Decision Support.

Transaction data is useful when you require only transaction statistics, rather than the detailed information that CMF produces. In many cases, it is sufficient to process only this data, since RMF™ records it as part of its SMF type-72 record. Analysis (and even recording) of SMF records from CMF can then be reserved for those circumstances when the detailed data is needed. Use the MVSPM component of the System Performance feature of Tivoli Decision Support to report on this data.

When running under goal mode in MVS 5.1.0 and later, CICS performance can be reported in workload groups, service classes, and periods. These are a few examples of Tivoli Decision Support reports for CICS in this environment. Figure 1 shows how service classes were served by other service classes. This report is available only when the MVS system is running in goal mode. The headings are Workload group, Service class, Served class, No of times served, No of transactions, and No of times served per transaction.

Figure 1. Example of an MVS Performance Management served service classes overview report
                         MVSPM Served Service Classes, Overview                         
                         Sysplex: 'SYSPLEX1' System: IP02                         
                         Date: '2001-01-18' Period: 'PRIME'                         
 
 
      Workload Service  Served    No of times         No of    No of times
       group    class   class       served            tx's    served per tx
      -------- -------- -------- ------------  ------------  --------------
      CICS     CICSREGS CICS-1          15227           664            22.9
                        CICS-2           6405           215            29.8
                        CICS-3          24992          1251            20.0
                        CICS-4          87155          1501            58.1
                        CICSTRX         67769          9314             7.3
 
                        Tivoli Decision Support report: MVSPM79

Figure 2 shows the average transaction response time trend and how the various transaction states contribute to it. (The times shown for the various transaction states are calculated based on transaction state samples, and so are not necessarily a precise record of the time spent in each state.) Adding the time spent in each of the transaction states (the shaded areas on the graph) gives the average execution time, which is shorter than the average response time (the line on the graph). The difference between the response time and the execution time is mainly made up of switch time — for example, the time the transactions spend being routed to another region for processing.

This report is available when the MVS system is running in goal mode and when the subsystem is CICS or IMS™.

Figure 2. Example of an MVS Performance Management response time breakdown, hourly trend report
The graph shows the average response time, in seconds, over the course of a day. The average response time is shown as a line, and it varies between about 1.5 seconds and nearly 2.5 seconds. The various transaction states are shown as shaded areas stacked above each other, and added, they represent between a half and two-thirds of the average response time, depending on the time of day. The transaction states shown are Active, Ready, Idle, Lock wait, I/O wait, Conv wait, Distr wait, Syspl wait, Timer wait, Other wait, and Miscellaneous wait. For any time of day, you can read off the average response time, and the average proportion of that time spent in each transaction state state. For example, at 1300 hours, there was an average response time of just over 2 seconds. On average, about 0.5 seconds of that time were spent in an I/O wait. For 0.2 seconds, the transaction was idle. For 0.4 seconds, the transaction was ready. About 0.3 seconds were spent in a number of the other wait states. Adding all the time spent in the different transaction states gives an execution time of 1.4 seconds, leaving a difference of about 0.6 seconds between the response time and the execution time.

Figure 3 shows how much the various transaction states contribute to the average response time. This report is available when the MVS system is running in goal mode and when the subsystem is CICS or IMS. The report gives information on Workload group, Service class/Period, Ph, MVS sys ID, and Total state, followed by the percentage of response time spent in each of the states listed in Figure 2.

Figure 3. Example of an MVS Performance Management response time breakdown overview report
                                     MVSPM Response Time Breakdown, Overview
                                     Sysplex: 'SYSPLEX1' Subsystem: IP02
                                     Date: '2001-01-18' Period: 'PRIME'
 
 
          Service        MVS  Total Activ Ready Idle   Lock  I/O   Conv Distr Local  Netw Syspl Timer Other  Misc
 Workload  class         sys  state state state state  wait  wait  wait wait  wait   wait wait  wait  wait   wait
   group   /Period    Ph  ID    (%)   (%)   (%)   (%)   (%)   (%)   (%)   (%)   (%)   (%)   (%)   (%)   (%)   (%)
 -------- ---------- --- ---- ----- ----- ----- ----- ----- ----- --     --- ----- ----- ----- ----- ----- ----- -----
 CICS     CICS-1  /1 BTE CA0    6.6   0.0   0.0   0.0   0.0   0.0   6.5   0.0   0.0   0.0   0.0   0.0   0.0   0.0
                         C80   29.4   0.0   0.0   0.0   0.0   0.0  14.7   0.0   0.0   0.0   0.0   0.0  14.6   0.0
                         C90    3.8   0.4   1.3   1.5   0.0   0.2   0.5   0.0   0.0   0.0   0.0   0.0   0.0   0.0
                              ----- ----- ----- ----- ----- ----- -----  --- ----- ----- ----- ----- ----- ----- -----
                            *  13.3   0.1   0.5   0.5   0.0   0.1   7.2   0.0   0.0   0.0   0.0   0.0   4.9   0.0
 
 
                  /1 EXE CA0   16.0   0.1   0.2   0.1   0.0  15.5   0.0   0.0   0.0   0.0   0.0   0.0   0.1   0.0
                         C80   14.9   0.1   0.1   0.1   0.0   3.7   0.0   0.0   0.0   0.0   0.0   0.0  11.0   0.0
                         C90   14.0   1.6   4.5   4.8   0.0   3.2   0.0   0.0   0.0   0.0   0.0   0.0   0.0   0.0
                              ----- ----- ----- ----- ----- -----   --- ----- ----- ----- ----- ----- ----- -----
                            *  14.9   0.6   1.6   1.7   0.0   7.4   0.0   0.0   0.0   0.0   0.0   0.0   3.7   0.0
 
 
 IMS      IMS-1   /1 EXE CA0   20.7   0.4   0.7   0.0   0.0   0.0  19.6   0.0   0.0   0.0   0.0   0.0   0.0   0.0
                         C80    1.1   0.2   0.1   0.7   0.0   0.1   0.0   0.0   0.0   0.0   0.0   0.0   0.0   0.0
                         C90   22.2   5.3  11.9   1.2   0.0   0.2   3.6   0.0   0.0   0.0   0.0   0.0   0.0   0.0
                              ----- ----- ----- ----- ----- -----  ---- ----- ----- ----- ----- ----- ----- -----
                            *  14.7   2.0   4.2   0.6   0.0   0.1   7.8   0.0   0.0   0.0   0.0   0.0   0.0   0.0
 
                          Tivoli Decision Support report: MVSPM73


dfht3c0057.html | Timestamp icon Last updated: Monday, 5 June 2017