Previous Topic: 3.3.2 How to Modify Standard MICF InquiriesNext Topic: 4.1 Philosophy and Requirements


4. EXCEPTION REPORTING


To pinpoint problem areas that may undermine an
installation's effectiveness, CA MICS provides exception
reporting.  Exception reporting can report an occurrence that
is a distinct problem (e.g., TCAM/VTAM outage at 2:00 PM),
one that may be a problem and requires further research
(e.g., TSO user overloaded the system from 1:00 to 1:30 PM),
or one that represents a standard, security, or audit
violation (e.g., user XYZ is not authorized to use SUPERZAP
and was detected using it seven times last week).

This problem reporting is linked to the areas of installation
management responsibility -- availability, service, workload,
standards, security, and performance.

The exception reporting process uses threshold values, which
are defined by the installation, to test for instances that
do not conform to the values.  These instances are called
exceptions.

The process produces several standard reports.  Some reports
are produced from an option within the CA MICS daily update.
These include the following:

o   Exception Management Overview

    This is a count of the number of critical, impacting,
    and warning conditions.

o   Severity Level Exception Summary

    This report lists the exceptions that were encountered
    by time of day and level of severity.

o   Management Area Exception Summary

    This summary lists the exceptions for the day for each
    management area, listed by hour.

Exception DETAIL reports are produced via the CA MICS
Information Center Facility (MICF).  These reports are the
following:

o  Full Exception DETAIL Report

o  Short Exception DETAIL Report

These reports detail the exceptions encountered, listing the
threshold  value that was set and the value that was
encountered.   They are used to diagnose the individual
exceptions that occur.

This chapter describes the philosophy and requirements of
exception reporting,  the operational flow, the exceptions
provided with this Analyzer,  and a detailed explanation of
the exception definition process.

This section contains the following topics:

4.1 Philosophy and Requirements

4.2 Exception Processing

4.3 Using the Exception Reports for Problem Analysis

4.4 Identification and Qualification

4.5 CA MICS Network Standard Exceptions List

4.6 Detail Exception Descriptions