The exception process provides management and technical personnel with a means to specifically identify problems or problem areas, organize and report the problems in terms of their severity, integrate the problem reporting for all system components, and associate the problems to their respective management areas. This process is called Exception Reporting and operates daily to process the updated database and report each day's exceptions. Figure 2-1 depicts the inputs, operational flow, and outputs related to this daily process.
+-----------+
| |
| Database |
| |
+-----------+
|
|
+-----------+
| User- |
| Defined |
| Exception |
| Analyzer |
+-----------+
|
+-----------+
| Database |
| Exception |
| File |
+-----------+
|
+-----------------------+
| |
+-----------+ +-----------+
| Standard | | MICF |
| Exception | | Exception |
| Reports | | Inquiry |
+-----------+ +-----------+
Figure 2-1. Exception Reporting Operational Flow
On a daily basis the appropriate 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 the necessary user-defined values
which tailor the exception test to the installation
requirements.
The test routines are provided with each distributed
component (e.g., TSO test routines, RMF test routines, etc.).
These tests are called Exception Test Routines (ETRs) and are
stored in their respective unit source library (e.g.,
sharedprefix.MICS.SOURCE) in the member DYcccEXC, where ccc
represents the applicable component identifier, such as SNT
for the SNA Network Analyzer.
Each exception test may be identified within the source
module named above by its assigned exception number. The
text condition and definition is written in SAS and
consequently may be easily modified by the user. The
exception test condition also sets the exception number,
defines the severity, assigns the exception to a management
area, defines the appropriate text message to explain the
exception, and establishes the necessary tests to identify
the exception condition.
Standard reports and online inquiries are available in
reporting the exception information. The standard reports
include an Exception Management Overview, the Severity Level
Exception Summary, and optionally, the Management Area
Exception Summary. Online inquiry provides the user with the
ability to produce the Exception Full Detail Report which
itemizes the detected exceptions on an individual basis. The
online inquiry facility enables the user to quickly retrieve
the Exception Full Detail report online by specific
selections on exception number, severity level, management
area, user, and standard date and time.
This reporting structure is used with the emphasis being
on first providing management a concise summary of the
frequency of problems in the Exception Management Overview.
An integrated, time-of-day oriented report provides the
performance analyst and systems team with a summary of which
exceptions, ordered by their severity, have been detected
over the hours of the day. Based on the exceptions reported
and the known problems, the performance analyst can then
employ the online inquiry to analyze quickly, and in-depth,
the detail exceptions and the database information from
which they were taken, to complete the research and
resolution of the reported items.
The Exception Reports provide a concise, integrated, and
itemized list of the problems impacting an installation's
effectiveness in terms of availability, service, workload,
standards, security, and performance for the different areas
of responsibility (e.g., TSO, Batch, MVS).
This chapter contains sections to describe the philosophy
and requirement of exception reporting, a general description
of the process, the methodology for qualifying exceptions, an
explanation of the operational flow, a list of the exceptions
provided, a description of the reports, a plan for the use of
the reports, and the more detailed descriptions required to
explain the exception definition process.
This section contains the following topics:
2.1 The Exception Reporting Process
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |