2. USAGE GUIDELINES › 2.3 Data Analysis Guidelines › 2.3.2 Analyzing Performance

2.3.2 Analyzing Performance

In terms of CICS, good performance is delivered when:

   o  Short and consistent response time is provided to
      maintain user productivity and satisfaction.

   o  The service level objectives stated by the users
      (explicitly or implicitly) have been met.

   o  There is effective use of hardware resources (CPU,
      main storage, DASD, communication links) in providing
      the service required.

Therefore, the main focus of a CICS performance analysis is
on the CICS response time measures.  The CA MICS Analyzer
Option for CICS provides you with summary and management
reports to analyze response time.  The summary reports are
produced by submitting a batch job after the CA MICS DAILY
update is completed.  The management reports are produced
automatically by the CA MICS operational jobs DAILY, WEEKLY,
and MONTHLY.  In addition, MICF inquiries are provided for
you to analyze response time.  You can modify the inquiries
to suit your data center's needs.  The MICF inquiries are
executed on an ad hoc basis.  See Chapter 3 of this guide for
detailed descriptions and samples of the following reports:

   o  Summary Reports

      -  Daily Activity Overview Report - Response Time
           Distributions
      -  Application Unit Summary Report
      -  Daily User Activity Summary Report

   o  Management Reports

      -  Daily CICS Service Report - All Activity
      -  Daily CICS Service Report - Medium Activity
      -  Daily CICS Service Report - Short Activity

      -  Weekly CICS Service Report - All Activity
      -  Weekly CICS Service Report - Medium Activity
      -  Weekly CICS Service Report - Short Activity

      -  Monthly CICS Service Report - All Activity
      -  Monthly CICS Service Report - Medium Activity
      -  Monthly CICS Service Report - Short Activity

   o  Graphic Inquiries

      -  CICCDT - 8AM - 5PM CICS Service by Type
      -  CICCD2 - Daily CICS Service Report
      -  CICCW2 - Weekly CICS Service Report
      -  CICCM2 - Monthly CICS Service Report

   o  Printer Graphic Inquiries

      -  CICPD2 - Daily CICS Service Report
      -  CICPW2 - Weekly CICS Service Report
      -  CICPM2 - Monthly CICS Service Report

In addition to the reports provided, you can code SAS
programs to analyze response time using the following data
elements:

FILE       ELEMENT     DESCRIPTION
------     -------     -----------

CICCSY     CSYAVSTM    Avg Short Response Time
CICCSY     CSYAVMTM    Avg Medium Response Time
CICCSY     CSYAVLTM    Avg Long Response Time
CICCSY     CSYAVTTM    Avg Response Time All Functions
CICCSY     CSYSDST1-   Count Short Response Within Limit n
           CSYSDST8
CICCSY     CSYMDST1-   Count Medium Response Within Limit n
           CSYMDST8
CICCSY     CSYLDST1-   Count Long Response Within Limit n
           CSYLDST8
CICCSY     CSYTDST1-   Count Total Response Within Limit n
           CSYTDST8
CICCSY     CSYMXSTM    Max Short Response Time
CICCSY     CSYMXMTM    Max Medium Response Time
CICCSY     CSYMXLTM    Max Long Response Time
CICCSY     CSYMXTTM    Max Response Time All function

Note: The same set of data elements are also available from
the CICCAU and CICCSU files.  For example, to display the
average short response time for a specific user, you can use
the data element CSUAVSTM.  For average short response time
for an application unit, use the data element CAUAVSTM.

In addition to the CICS response time measures, you can also
use the following data elements to examine problem conditions
that may affect CICS performance:

FILE       ELEMENT     DESCRIPTION
------     -------     -----------

CICCSY     CSYPAGIN    Page Ins (pre CICS 3.1.1)
CICCSY     CSYMXTSK    Max Tasking Condition Detected
CICCSY     CSYSOS      Short on Storage Condition
CICCSY     CSYPCMDC    Number of Program Compressions
CICCSY     CSYWTIM     CICS Dispatcher Wait Time
CICCSY     CSYWTCPU    CPU Across OPSYS Wait (ASG-TMON)
CICCSY     CSYMEMSZ    High-water Dynamic Area Memory
CICCSY     CSYDAMSC    Damaged Storage Chain
CICCSY     CSYUSRTM    User (application) Dispatched Time
CICCSY     CSYTCUTM    User TCB CPU Time

CICCSU     CSUABEND    Abnormal termination occurrences
CICCSU     CSUFCWAT    File Control Wait Time
CICCSU     CSUIRWAT    MRO/ISC Wait Time
CICCSU     CSUJCWAT    Journal Control Wait Time
CICCSU     CSUSUSTM    Time Transaction was on CICS Susp Chn
CICCSU     CSUTSWAT    Temporary Storage Wait Time
CICCSU     CSUTCWAT    Terminal Control Wait Time
CICCSU     CSUWAITM    Transaction Wait Time

Note: The set of CICCSU data elements are also available from
the CICCAU file if the CICCAU file is active.  For example,
to obtain the number of abnormal termination occurrences for
an application unit, use the data element CAUABEND.