3. Installation › 3.7 Production System Implementation › 3.7.2 Exception Process Review and Adjustment

3.7.2 Exception Process Review and Adjustment

The running of CA MICS Exception Analyzer routines is
controlled by the CREATE EXCEPTIONFILES parameter you specify
in prefix.MICS.PARMS(EXECDEF) (refer to Section 2.3.5,
Dynamic Execution Options, for a description of this
parameter).  As the CA MICS system is shipped, this parameter
is specified as NONE, causing CA MICS to not run the
Exception Analyzer routines as part of the CA MICS DAILY
job.  If you are going to run some or all of the Exception
Analyzers, you must review these programs and change the
values used for identifying exceptions to be appropriate for
your installation's operating environment.

Follow the steps below to analyze and adjust the exception
values:

    1.  Review Section 2.4, Exception Values, in the
Standard Reports Guide.  This section describes the Exception
Value Analyzer, which enables you to adjust exception values
to address your installation's requirements.

    2.  List the source code used for setting the exceptions
from the source library (sharedprefix.MICS.SOURCE).  You need
only examine the modules for those components you listed on
your CREATE EXCEPTIONFILES parameter statement.  The
Exception Analyzers shipped with the standard set of CA MICS
products are:

    DYSMFEXC - Batch Exceptions
    DYRMFEXC - Hardware Utilization and System Control
               Program Exceptions
    DYTSOEXC - TSO Exceptions

while the Exception Analyzers shipped with optional CA MICS
products are:

    DYcccEXC - ccc Exceptions

where ccc is the three character product identifier.  These
will only be in sharedprefix.MICS.SOURCE if your site
licenses these products.

Review the listings to gain a basic understanding of how an
exception is identified by the code.

    3.  Execute the Exception Value Analyzers referenced in
Step 1.  The output of these reports provides an initial set
of values to be used for exception testing that are based on
data from your installation.  Review the recommendations,
which are listed by data element within exception number for
quick reference, and decide whether to use the recommended
value or your own judgment (which enables you to consider
organizational and political factors).

    4.  Modify the exception analyzer routines to reflect the
adjustments that should be made in tailoring each of the
exception values to address the installation's requirements.

    5.  Activate the modified programs by changing the
CREATE EXCEPTIONFILES statement which is contained in member
EXECDEF of prefix.MICS.PARMS.  Note that if you want the
CA MICS Exception Reports to be printed for some or all of
the exceptions found by the Analyzers, you will have to
name them on the REPORT EXCEPTIONS parameter statement in the
EXECDEF member (or use the MICF inquiry production reporting
facilities, documented under MICF Administration in the MICF
Reference Guide, to generate daily CA MICS exception
reports).  Both of these changes will take effect for your
next day's processing cycle with no further action.  Check
the output of the next daily run to ensure that no
operational problems were introduced.  Carefully verify that
all functions are still operative after the modifications
were implemented.

    6.  You will find that the exceptions thresholds will
require periodic adjustment using the above process.