Analyzing a CICS Performance Profile

The procedure for analyzing a base Performance Profile is outlined in Using-the-Strobe-Application-Performance-Measurement-System. The procedure involves:

• Validating measurement session parameters
• Identifying critical activities
• Analyzing task execution activities
• Analyzing file access activities.

When you apply the analysis procedure to the CICS environment, you must refer to both the standard Performance Profile reports and the CICS Performance Supplement reports, which provide more data to help you focus on specific CICS application performance problems.

When interpreting your CICS Performance Profile, you can follow the general guidelines provided in this chapter. However, keep in mind that your CICS region probably has its own type of CPU and I/O facility usage inefficiencies.

The Performance Profile described here resulted from an examination of a cost accounting system, which revealed a CICS application with the following characteristics:

• Acceptable transaction response time
• Excessive CPU usage for its two principal transactions, CDUN and CSRV
• Erratic and long response times for transaction BACK.

To determine why these conditions exist, a Strobe measurement request was sent to the CICS region where the application was running, and a Performance Profile was generated from the sample dataset.