4. EXCEPTIONS › 4.1 Introduction

4.1 Introduction

The exception reporting process reads data from the available
monitoring sources (e.g., VMC, SMF, CA TSO/MON PM), compares
this activity against predefined thresholds, and provides an
integrated list of exceptions for potential problem areas.

Figure 4-1 illustrates the operation of the exception
reporting process.  The user-defined values comprise the part
of the system that tailors and modifies the exceptions to
uniquely address a site's requirements.


                        +-----------+
                        |           |
                        | Database  |
                        |           |
                        +-----------+
                              |
                              |
                        +-----------+
                        |   User-   |
                        |  Defined  |
                        | Exception |
                        |  Analyzer |
                        +-----------+
                              |
                        +-----------+
                        | Database  |
                        | Exception |
                        |   File    |
                        +-----------+
                              |
                  +-----------------------+
                  |                       |
            +-----------+           +-----------+
            | Standard  |           | MICF      |
            | Exception |           | Exception |
            | Reports   |           | Inquiry   |
            +-----------+           +-----------+


  Figure 4-1.  Exception Reporting Operational Flow

On a daily basis, the exception files contained in the
database are processed to detect the defined exception
conditions.  The Exception Analyzer performs this task by
using individual test routines to identify the exceptions.
Each test routine requires user-defined values that tailor
the exception test to the site requirements.

An exception analysis completely defines the tests made to
determine the exception condition and the criteria that
define and classify the exception for reporting.  The user
may easily modify, or in some cases even add, values to the
exception criteria to better meet a site's exception
reporting requirements.

These tests are called Exception Test Routines and are stored
in the source library prefix.MICS.USER.SOURCE in the member
DYVMCEXC.  An exception group exists for each file that is to
be processed by the Exception Analyzer and consists of the
exception data that is to be processed for a product.

Figure 4-2 lists the range of Exception Numbers that may be
defined for each data group and file.  The exception code is
organized sequentially by exception numbers within the
DYVMCEXC program and consists of standard identification
definitions (e.g., severity level), exception-dependent
criteria (e.g., amount of CPU time used), or standard
selection facilities (e.g., selection of prime-time hours
only).  Modification of existing exception analysis can be
done easily.  The exception name and number delineate the
start of its definition within DYVMCEXC.  The value to be
modified can then be located and changed directly within the
SAS code.


  +------------------------------------------------------+
  |   Exception    |                                     |
  |  Number Range  |     Database File Name              |
  |----------------+-------------------------------------|
  |  08050-08055   |  Domain 1 VM Monitor records        |
  |  08056-08061   |  DETAIL.VMXSGP01                    |
  |  08062-08063   |  DETAIL.VMXSCF01                    |
  |  08064         |  Domain 1 Record 11 VM monitor      |
  |                |    records                          |
  |  08065-08066   |  DETAIL.VMXLPR01                    |
  |  08067-08068   |  Domain 1 VM Monitor Event records  |
  +------------------------------------------------------+



 Figure 4-2.  Exception Number Table