EXCEPTS

The EXCEPTS control statement requests the Exception Subreport and the Exception Trace Detail Report. The EXCEPTS statement uses data collected by the TRACE76 Extractor control statement.

EXCEPTS
[INTERVAL=hh:mm:ss]
[,MIN=0|n]
[,MAX=0|n]
[,ASSOC=(measname1,measname2,measname3)]
[,CPU={0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|10|11|...|1F|ALL}]
[,MEASURE=measname]
[,TRACE={YES|NO}]
[,TRCETYPE=(T1=trace-type,...,T4=trace-type)]

Parameters

The parameters for the EXCEPTS control statement are as follows:

INTERVAL=	specifies the time divisions on the report The default is the size of the recording interval. Specifying an interval that is less than the recording interval has the same effect as using the INTERVAL default. If TRACE=YES is specified, the default interval is the trace set size. The EXCEPTS interval is used to gather data in multiples of the Extractor record interval. Data cannot be prorated over time. A data collection key is generated for each Extractor record encountered that meets date-time qualification requirements. The equation for this record key is Extractor record start time / EXCEPTS interval If the start of the Extractor record cycle and the size of the EXCEPTS interval parameter are known, you can determine which EXCEPTS record (graph line) contains which Extractor record group. The use of the EXCEPTS interval is illustrated in examples 1 and 2, following.
MIN=	specifies the lower limit that can trigger the exception It must be a one- to eight-digit number greater than or equal to zero. The default is zero, and there is no implied precision.
MAX=	specifies the upper limit that can trigger the exception It can be a one- to eight-digit number. The default is zero, and there is no implied precision.
ASSOC=	specifies up to three additional measures (regardless of type) to be printed if the MEASURE value is less than the MIN value or greater than the MAX value In the EXCEPTS statement, three or fewer ASSOC measures can be requested together, independent of type.
CPU=	specifies the CPU ID (as a hexadecimal value) for which CPU-related measures are to be reported Acceptable IDs are 0 through 1F, and ALL. ALL is the default.
MEASURE=	specifies the measure that can be monitored for each exceptional condition Only one measure can be monitored for each EXCEPTS command. Valid measures are the same as those used in the GRAPH statement; they are listed in the section that discusses “Measure and trace values.” If you want to define more than one measure, use the ASSOC parameter.
TRACE=	produces the Exception Trace Detail report This report is for TRACE76 measures only. Any other graphics measures included on the measure list cause an error. One TRACE76 measure name can be on the MEASURE parameter, and three associative TRACE76 measure names can be included on the ASSOC parameter. TRACE76 measures are shown in the section that discusses measure and trace values. Important Look at member CMFANLTR in the UBBPARM data set for examples of using the TRACE, MEASURE, and TRCETYPE parameters. TRACE uses the ASSOC, MEASURE, and TRCETYPE parameters to format the trace report.
TRCETYPE=	specifies atrace-type value to be associated with the entries on the MEASURE and ASSOC parameters There are four values for the TRCETYPE parameter: T1 specifies thetrace-type value for the measure name on the MEASURE parameter T2 specifies the trace-type value for the first measure name on the ASSOC parameter T3 specifies the trace-type value for the second measure name on the ASSOC parameter T4 specifies the trace-type value for the third measure name on the ASSOC parameter The trace-type values can have any of the following values: MIN—minimum value captured during the specified time interval calculation: SMF76MIN MAX—maximum value captured during the specified time interval calculation: SMF76MAX AVG—average value captured during the specified time interval calculation: SMF76AVG / SMF76SSS; the default END—last value captured during the specified time interval calculation: SMF76ENV STD—standard deviation value captured during the specified time interval calculation: (SMF76SSS * Ʃ(SMF76STD) – (Ʃ(SMF76AVE) 2)) .5 / SMF76SSS DIF—difference between the starting end value and the ending end value calculation: SMF76ENV(last) - SMF76ENV(first) Important The trace-types collected must be selected in the RMF data collector. The BMC AMI Ops Monitor for CMF Extractor always collects all trace-types. If a trace-type is selected for data that was not collected by RMF, it is marked N/A in the report output and a warning message is produced.

Examples

Determine which EXCEPTS interval contains Extractor record data for CPU busy, as of 10:15 A.M., on March 28, 2010, if

Extractor start time is 00:15 A.M. on March 28, 2010
Extractor REPORT control statement interval parameter value is QTR
EXCEPTS parameter interval value is 02:00:00

From this information you know the following information:

Data collection begins at 00:15:00 (from Extractor start time).
Twelve EXCEPTS intervals cover the 24-hour period encompassing the data of March 28, 2010. (This value is calculated by dividing 24 hours by the EXCEPTS interval value of 2; the result is 12.)
A maximum of eight Extractor intervals can be summed into each EXCEPTS data collection interval. (This value is calculated by dividing the EXCEPTS collection interval of 2 by the Extractor QTR hour (¼) hour interval; the result is 8.)

The following table shows the EXCEPTS intervals and EXCEPTS interval time ranges for this situation. EXCEPTS interval 06 contains the Extractor record data for CPU busy at 10:15 A.M.

EXCEPTS interval time range for 12 intervals

EXCEPTS interval number	EXCEPTS interval time range	Comments
01	00:00:00 - 02:00:00
02	02:00:00 - 04:00:00
03	04:00:00 - 06:00:00
04	06:00:00 - 08:00:00
05	08:00:00 - 10:00:00
06	10:00:00 - 12:00:00	10:15:00 EXTR RECORD
07	12:00:00 - 14:00:00
08	14:00:00 - 16:00:00
09	16:00:00 - 18:00:00
10	18:00:00 - 20:00:00
11	20:00:00 - 22:00:00
12	22:00:00 - 24:00:00

When using the SHIFT control statement with an EXCEPTS control statement that contains the interval parameter, use this equation to generate the record key:

Record Key = ((Extractor record start date)
             - (January 1, 2010)
             + (Extractor record start time))
             / EXCEPTS interval

Example 1

SHIFT (010000,090000),(090000,170000)
EXCEPTS MEASURE=CPU,INTERVAL=02:00:00

Determine which EXCEPTS intervals have a CPU busy less than 8% or greater than 20% if the following scenario is true:

Extractor start time is 00:15 on March 28, 2010.
Extractor REPORT control statement INTERVAL parameter value is QTR.
EXCEPTS INTERVAL value is 02:00:00 (2 hours).
SHIFT request time ranges are 010000 to 090000 (1:00 A.M. to 9:00 A.M.) and 090000 to 170000.

From this information, you know that the following statements are true:

Data collection begins at 01:00:00 (from the SHIFT control statement request).
There are four EXCEPTS intervals within each SHIFT time range definition defined on the SHIFT control statement. (This number is calculated by dividing the 8 hour time range by the EXCEPTS interval value of 2; the result is 4.)
A maximum of eight Extractor intervals can be summed into each EXCEPTS data collection interval. (This number is calculated by dividing the EXCEPTS collection interval of 2 by the Extractor QTR (¼) hour interval; the result is 8.)

The following table shows the EXCEPTS intervals and EXCEPTS interval time range for this situation. The EXCEPTS interval 05 contains the Extractor record data for CPU busy at 10:15 A.M.

EXCEPTS interval time range for eight intervals

EXCEPTS interval number	EXCEPTS interval time range	Comments
01	01:00:00 - 03:00:00
02	03:00:00 - 05:00:00
03	05:00:00 - 07:00:00
04	07:00:00 - 09:00:00
05	09:00:00 - 11:00:00	10:15:00 EXTR RECORD
06	11:00:00 - 13:00:00
07	13:00:00 - 15:00:00
08	15:00:00 - 17:00:00

Example 2

EXCEPTS INTERVAL=00:30:00,MIN=8,MAX=20,
MEASURE=PAGESEC,ASSOC=(PAGEINS,PAGEOUTS)

In this example, the INTERVAL parameter value causes the time division on the Exception Report generated to be 30 minutes; minimum/maximum trigger range is less than 8 or greater than 20; the average paging rate per second is measured, as well as the number of pages brought into and out of central storage.

Example 3

EXCEPTS MEASURE=RCEAFC,
         TRACE=YES,
         ASSOC=(RCEPOOL,
                RCECOMPI,
                RCECOMPO),
         TRCETYPE=(T1=AVG,T2=DIF,T3=MAX,T4=MIN)

where

T1=AVG specifies the trace value for exception-measure
T2=DIF specifies the trace value for associate-measure-1
T3=MAX specifies the trace value for associate-measure-2
T4=MIN specifies the trace value for associate-measure-3

Important

VSDB and VSDA labels used in the calculations (referred to in the table from the topic that discusses 'Profile Bar Graph field descriptions') are DSECT fields in VSDATA, which define areas within major SMF78RCD triplet areas associated with CSA and SQA data.