Investigating bottlenecks
Bottlenecks can be caused by various components of CICSPlex SM.
You need to be aware of how these components are defined and how they interact, as well as of the transactions underway when the bottleneck occurs.
Use the information in this section to help you isolate the cause of a bottleneck
or to report the condition to customer support personnel.
- Questions to ask
-
- What type of request was being processed?
- How big was the CICSplex involved?
- How many CMASs and MASs were involved?
- What types of monitoring, real-time analysis, and workload management were active?
- What are the dispatching priorities of the CMASs and MASs?
The priority of a CMAS must be higher than that of the MASs it manages.
- Are the CICS® SIT parameters correctly specified for the CMASs and MASs?
- How is the communications network performing?
- Documentation to collect
- To diagnose a performance problem such as a bottleneck, customer support personnel may ask you to turn on trace level 16 in selected CICSPlex SM components. Many components use trace level 16 to determine how long a request takes to complete. It may be possible, based on that data, to isolate the problem to outgoing or incoming processes. For information on controlling the trace levels in CICSPlex SM components, see Controlling the amount of tracing in a CMAS or MAS.