CICS region problems
- Where is a good starting point to investigate general performance problems?
- Why are there performance problems for a particular CICS region?
- How is the CICS region performing now, over the current interval and since monitoring by BMC AMI Ops Monitor for CICS started on the target?
- Which CICS regions are in danger of reaching Max task?
- Can I change the MAX task setting for a CICS region?
- Which CICS regions are in danger of exhausting (E)DSA?
- Can I modify the DSA limits for a CICS region?
- How can I find the system initialization table (SIT) settings?
- What is the state of my DB2 attachment?
- What is the state of my DBCTL attachment?
- What is the state of my MQ attachment?
Where is a good starting point to investigate general performance problems?
The CREGOVER view provides a good starting point for examining one or more CICS regions that are not performing as well as they should. It provides an overall graphic representation of the CPU usage, the EXCP rate, the transaction rate and the average response time for the regions. A hyperlink on the %CPU field provides access to the CREGDETL view, which provides greater detail on the state of an individual system.
Why are there performance problems for a particular CICS region?
CREGPRB provides general information about any outstanding problems in the CICS regions within the current context, including problem messages. The messages often provide enough information to troubleshoot a problem.
How is the CICS region performing now, over the current interval and since monitoring by BMC AMI Ops Monitor for CICS started on the target?
The CREGDETL view provides information on various real-time performance measurements for the current interval and since monitoring began (session). This information includes the average response time, transaction rate, and %CPU utilization.
Which CICS regions are in danger of reaching Max task?
CREGION provides a performance analysis of each CICS region within the current context, including the percent of MAX task at which the CICS is operating.
Can I change the MAX task setting for a CICS region?
The CREGSYT view provides the current MAX task value and the SET action that can be used to increase or decrease it.
Which CICS regions are in danger of exhausting (E)DSA?
The CREGDSAS view provides the current DSA and EDSA limits and what percent of each is in use. This view and its detail view ( CREGDSA), also provides a breakdown of the individual DSA components (CICS, user, shared and read-only).
Can I modify the DSA limits for a CICS region?
The CREGSYA view provides the current DSA and EDSA limits and the SET action that can be used to increase or decrease them.
How can I find the system initialization table (SIT) settings?
The CREVIEW view provides the gateway to the system initialization views. The hyperlink from the region name goes to a menu that breaks the parameters down by group. There are also several menus containing the alphabetic list of SIT parameters. The details for these views show the setting at initialization (not necessarily current) as well as an indication of whether the assembled SIT was overridden by SYSIN or JCL parameters.
What is the state of my DB2 attachment?
The CDB2CON view shows the state of the CICS to DB2 attachment facility. The data includes whether the facility is started, the DB2 system ID and its release as well as the maximum, current, and high water mark for TCBs managing DB2 threads.
What is the state of my DBCTL attachment?
The CREGDBC view shows the state of the CICS to DBCTL (IBM IMS) attachment facility. The data includes whether the facility is started, the DBCTL system ID and jobname as well as the minimum, maximum, and current thread counts.
What is the state of my MQ attachment?
The CMQCONN view shows the state of the CICS to IBM MQ attachment facility. The data includes whether the facility is started, the MQ system ID, maximum and current server counts, as well as overall task usage of the facility including call types.