Identifying CICS performance constraints
Major constraints on a CICS® system are often identified by external symptoms such as stress conditions and longer response times. CICS can resolve some constraint problems; others must be resolved manually.
- Transactions that perform data set activity accumulate
- Waits on strings occur
- More transactions are waiting in the system
- Demands on virtual storage increase
- Demands on real storage increase
- Increased paging occurs
- The task dispatcher uses more processor power scanning task chains
- Task constraints occur
- The MXT or transaction class limit is exceeded; the processor is required to do additional work because more retries are required
As a result the system shows heavy use of all resources, resulting in typical system stress. This situation does not indicate problems with all resources; it shows that a constraint has yet to be found. To identify the constraint, you must find out what is affecting task life.
If performance is unacceptable, the performance constraints (the causes of the symptoms) must be identified so that they can be tuned.
When dealing with limit conditions, you might find it helpful to check the various hardware and software locations in the system where performance constraints are occurring.