2. PERFORMANCE REPORTING ANALYSIS › 2.8 Sysplex Analysis › 2.8.5 Component Operation › 2.8.5.3 Sysplex Performance Exceptions
2.8.5.3 Sysplex Performance Exceptions
The Sysplex Performance Exceptions report allows you to
detect and track various unusual or out-of-the-ordinary
conditions that might arise in XCF service processing and the
underlying coupling facility hardware configuration. It can
be generated for the DETAIL, DAYS, WEEKS, or MONTHS timespans
if they are present in your CA MICS database. Note that the
Sysplex Performance Exceptions report obtains its data from
the SCPXCY, SCPXCA, HARCFP, and HARCFR Files. If you are
unsure of the timespans supported at your installation,
consult your CA MICS System Administrator.
The Sysplex Performance Exceptions report is produced using a
series of six screens. Only the first screen is required.
The others are used to specify additional options that are
often defaulted.
/---------------------- XCF Performance Exception Analysis ---------------------\
| Command ===> |
| |
| Composing CA MICS Inquiry: SPA001 - Sysplex Analysis - Sample Inquiry |
| |
| Time-span ===> DAYS (DETAIL/DAYS/WEEKS/MONTHS) Cycle(s) ===> 01 - 02 |
| Data base ===> A (PRIMARY) _ _ _ _ |
| Allow Run-Time Override of Data Base ===> N (Y/N) and/or Cycle(s) ===> N (Y/N) |
| |
| Data Selection: Allow run-time override |
| Date ===> _______ - _______ _______ - _______ ===> N (Y/N) |
| Hour ===> __ - __ __ - __ __ - __ ===> N (Y/N) |
| Zone ===> _ _ _ _ _ _ _ _ _ ===> N (Y/N) |
| Sysid ===> ____ ____ ____ ____ ____ ____ ===> N (Y/N) |
| Systems ===> ________ ________ ________ ________ |
| |
| |
| Specify extended options ===> N (Y/N) |
| |
| |
| |
| |
| |
| |
\---------------------------------------------------------------------------------/
Figure 2-218. Sysplex Performance Exceptions Inquiry Screen
Figure 2-218 shows a Sysplex Performance Exceptions inquiry
screen. The fields common to all Sysplex Analysis routines
are described in Section 2.8.5.
There are five other screens in this series that you can use
to specify additional options that are often defaulted. They
are:
o Extended Options Menu
o Global Data Selection
o Exception Thresholds
o Alternate Input File
o Save Selected Input Observations
The Exception Thresholds Extended Option is unique to this
query. A description of how to set the Exception Thresholds
follows. For additional information on the common Extended
Options refer to Section 1.4.3.6, Specifying Common Extended
Options.
If you enter Y (Yes) in the Specify extended options field,
the Extended Options Menu screen, shown in Figure 2-219, is
displayed.
/---------------------------- Extended Options Menu ----------------------------\
| Command ===> |
| |
| Inquiry Step: XCF Performance Exceptions |
| |
| |
| Specify global data selection exit ===> N (Y/N/R) |
| Specify Exception Thresholds ===> N (Y/N/R) |
| |
| Specify alternate input file ===> N (Y/N/R) |
| Save selected input observations ===> N (Y/N/R) |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\---------------------------------------------------------------------------------/
Figure 2-219. Sysplex Performance Exceptions Extended Options Menu Screen
If you enter Y (Yes) to the Specify Exceptions Thresholds
in the Extended Options Menu, the Exception Thresholds
screen, shown in Figure 2-220 is displayed. This
screen allows you to enter trigger values for generating
exception incidents when the analysis is run.
/----------------------------- Exception Thresholds ----------------------------\
| Command ===> |
| |
| Inquiry step: XCF Performance Exceptions |
| ------------Threshold Values----------- |
| Exceptions: DETAIL DAYS WEEKS MONTHS |
| Intervals w/ XCF Deactivation 0 1 3 5 |
| XCF Count Resets 0 1 3 5 |
| Pct XCF Messages Larger than Buffer 5 5 5 5 |
| XCF Messages Rejected 0 0 0 0 |
| XCF Messages Migrated - No Path 0 1 3 5 |
| |
| Pct XCF Path Busy 50 50 50 50 |
| Intervals w/ XCF Path Deactivation 0 1 3 5 |
| Inbound Signals Refused 0 0 0 0 |
| |
| CF Pct Processor Busy 5 5 5 5 |
| Unsuccessful CF Requests 0 1 3 5 |
| CF Requests failed - Path Busy 0 1 3 5 |
| |
| CF Requests delayed due to dump ser 0 1 3 5 |
| CF Requests hitting lock contention 0 1 3 5 |
| |
| |
| |
\---------------------------------------------------------------------------------/
Figure 2-220. Sysplex Performance Exceptions Threshold Setting Screen
When using the XCF Performance Exception Analysis, it is
recommended that you start out with the default exceptions
shown above, and then adjust them to reflect the
characteristics of your particular environment. The four
columns correspond to the four CA MICS timespans that can
provide input to the analysis. Only the column that
corresponds to the timespan selected on the primary screen
will be used in the analysis. For example, if the timespan
selected on the primary screen was WEEKS, the threshold
values in the WEEKS column will be the ones used in the
analysis.
The length of RMF intervals, and the definition of CA MICS
ZONES play an important role in setting appropriate exception
threshold values. At the DETAIL level, a 5 or 10 minute RMF
interval might dictate a set of exception values considerably
different than a 20 or 30 minute interval. Similarly, at the
WEEKS and MONTHS levels, each CA MICS observation contains
ZONE in the file key, and this determines the overall
duration. For example, at the MONTHS timespan, ZONE 1 might
cover prime shift (9 to 5 Monday through Friday) for an
entire month. If ZONE 2 covered the remaining 16 hours of
each day Monday through Friday, the observations describing
ZONE 2 would cover a period of time that is twice as long as
those for ZONE 1. Because of this, you should probably use
ZONE selection criteria and separate analyses for each ZONE
when dealing with WEEKS or MONTHS level data.
Keep in mind, that if you set up an analysis using one
timespan as input along with corresponding threshold values
established via this screen, and then later change the
analysis to utilize a different timespan, the corresponding
column of threshold values specified here will go into
effect. Changing timespans on the primary screen does NOT
reset the exception threshold values to the defaults.
The grouping of exceptions shown in this screen is indicative
of the CA MICS file from which the exception is generated.
Thus, the first five exceptions are from the SCPXCY file, the
next three are from the SCPXCA file, the next three from the
HARCFP file, and the last two from the HARCFR file.
To turn off any give exception, simply set the threshold
value to an artificially high value.
