|
|
|
The Sysplex Performance Exceptions report is designed to
bring to light potential performance bottlenecks and tuning
opportunities affecting XCF services and the hardware
coupling facility. A sample report is shown in Figure 2-212.
REPORT OPTIONS
The Sysplex Performance Exceptions report has the standard
options for selecting specific systems and/or time periods to
include. Additionally, the extended options for this report
provide for explicitly setting the thresholds that dictate
when an exception incident will be reported. The selection
options are discussed in Sections 2.8.5 and 2.8.5.3.
REPORT ITEMS
DATE/TIME: The ending time stamp for the period in which
an exception was detected, along with the
duration of the reporting period. The duration
depends on the CA MICS timespan that was used
for generating the report.
DESCRIPTION: Text and pertinent instrumentation data
concerning the exception, including the
measurement item causing the exception, the
threshold for the exception, and relevant
identification data such as the name of the
system or coupling facility involved. The
exceptions that can be tracked are discussed in
section 2.8.5.3
EXPLANATION/ Text that indicates possible causes for the
RECOMMEND- exception condition, and, where applicable,
ATION: possible courses of action that might be taken
to alleviate or solve the condition.
CA MICS Performance Manager SYSPLEX PERFORMANCE EXCEPTIONS SYSTEM = S072 RUNDATE = Feb 1, yyyy XCF SYSTEM = S072 -------------------------------------------------------------------------------------------------------------------------------- | | DATE/TIME | DESCRIPTION | EXPLANATION/RECOMMENDATION | | -------------------------------------------------------------------------------------------------------------------------------- 31JAN95:16:30:00.00 | Requests encountering lock contention exceeds | Lock structures are used by CICS and IMS to DURATION: 2:28:20 | threshold. | implement data sharing and high-speed seriali- | Requests delayed: 166 | zation. Application tuning and/or placement | threshold: 100 | may be needed to reduce locking requirements. | Name of System using CF: S072 | | Coupling Facility Name: COUPLER | | CF Structure Name: JESCF | | | 31JAN95:17:00:00.00 | Requests encountering lock contention exceeds | Lock structures are used by CICS and IMS to DURATION: 0:30:00 | threshold. | implement data sharing and high-speed seriali- | Requests delayed: 36 | zation. Application tuning and/or placement | threshold: 30 | may be needed to reduce locking requirements. | Name of System using CF: S072 | | Coupling Facility Name: COUPLER | | CF Structure Name: JESCF | | | 31JAN95:16:30:00.00 | XCF Messages migrated due to no path exceeds | Most likely, there are no signaling paths DURATION: 2:28:20 | threshold. | assigned to the selected transport class, | Messages migrated: 8873 | incurring additional XCF, overhead for selecting | Threshold specified: 1500 | alternate transport classes. Review signaling | XCF Sys Name: S076 Transport Class: TCMIM | path assignments for the transport class shown. | Message Traffic Direction: OUTBOUND | | | 31JAN95:17:00:00.00 | XCF Messages migrated due to no path exceeds | Most likely, there are no signaling paths DURATION: 0:30:00 | threshold. | assigned to the selected transport class, | Messages migrated: 1795 | incurring additional XCF, overhead for selecting | Threshold specified: 1500 | alternate transport classes. Review signaling | XCF Sys Name: S076 Transport Class: TCMIM | path assignments for the transport class shown. | Message Traffic Direction: OUTBOUND | | | --------------------------------------------------------------------------------------------------------------------------------
Figure 2-212. Sample Sysplex Performance Exceptions
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |