Using the Product in a CICS Environment › CICS Summary Statistics

CICS Summary Statistics

CICS summary statistics are normally automatically collected at regular intervals (default 1 minute) by the COLLECT_TRANSACTION (collect CICS requested statistics) - see the Installation Guide. If you want to obtain summary statistics that contain data for a given monitoring run, you need to wait until that run has completed; wait until at least 1 COLLECT_TRANSACTION has completed (message TN0846I), and then analyse summary statistics for a subsequent monitoring run.

If it has not been excluded from analysis, you can assess the impact of the COLLECT_TRANSACTION (default name is TUNC) on your system using TranView. However, the COLLECT_TRANSACTION will not appear in TranView if it has not completed during a monitor run.

Use one of the following methods to obtain the CICS summary statistics:

• Enter STC from the TranView panel.
• Select option 14 from the Interactive Analysis panel.

  You will then see the CICS Summary (requested) Statistics panel shown following.

   CA MAT -------- CICS Summary (requested) Statistics ---
   COMMAND ===>                                                  SCROLL ===> CSR
   Place cursor on topic and press ENTER :                       Profile: CICSA
  
   DB2    DB2                             DISP  Dispatcher
   FILE   Files                           JAVA  JAVA
   LOGS   Logstreams                      PAUT  Program autoinstall
   RECV   Recovery Manager                SDMP  System dumps
   TDMP   Transaction Dumps               STOR  Storage (DSA)
   TCPI   TCP/IP                          TDQ   Transient Data (TDQ)
   TRNM   Transaction Manager             TSQ   Temporary Storage (TSQ)
   URIM   URIMAP                          VTAM  VTAM
   TCLS   Transaction Class (TCLASS)      ENQ   Enqueues
   LSRF   LSRPOOL (by file)               LSRP  LSRPOOL (by pool)
   CONN   IRC/ISC connections
  

The CICS Summary statistics allow you to check if problems in the CICS environment in which a given transaction runs might be affecting that transaction’s performance. These statistics can give you insight into the causes of poor transaction performance. Some examples of such problems are:

• Excessive transaction or system dumps pre-empting CICS resources
• Excessive DB2 aborts
• Storage waits
• Transaction Class queueing
• Temporary Storage waits due to insufficient strings or buffers

You can request summary statistics in the categories listed following.