Interpreting Strobe performance profile for a CICS System

This section describes a typical CICS application and the base Strobe Performance Profile. The Performance Profile in this chapter includes selected reports from the CICS Performance Supplement. These reports provide a broader range of information about CICS system-level activity than the Transaction Profiling reports. These are examples of situations when the CICS Performance Supplement reports are most helpful:

• The performance of an entire CICS region does not meet your standards, and you want to see an overall view of activity within the region.
• One or more CICS transactions is performing inadequately, but you are not sure of their identities.
• You question whether one or more application programs is consuming more CPU time than it should be.

The Strobe Performance Profile is enhanced through the CICS Performance Supplement by adding a set of reports that shows how specific CICS resources are utilized during the measurement session and a summary that accounts for all transaction activity within a CICS address space.

If you measure a CICS region and Strobe reports low CPU usage, you can obtain information about what is causing wait time by examining the CICS region-level wait reports described in Region-Level Reports. If you suspect that one or more specific transactions are displaying poorer than average performance, specify their names on the Strobe - CICS Data Collector Options panel as explained in Using-Strobe-for-CICS, and then use the Transaction Profiling subreports shown in Interpreting-Strobe-CICS-transaction-profile to see detailed information about what is affecting the transaction’s performance.