4. EXCEPTIONS › 4.2 Setting Exception Values

4.2 Setting Exception Values

Exception test routines contain tests that determine the
exception conditions and definitions that define and classify
the exception for reporting and analysis.  The following is a
sample exception test:

*
** 06008
** MESSAGE QUEUE REQUESTS SATISFIED IN POOL BELOW STANDARD;
*;
  IF ISYPCMQP < percent-satisfied-in-pool
   THEN DO;
    EXCCODE ='06008';
    SEVERITY='W';
    MGMTAREA='PERFORMANCE';
    EXCDESC1=
    'MSG QUEUE REQUESTS SATISFIED IN POOL BELOW STANDARD';
    EXCDESC2='MESSAGES QUEUE REQ SATIS IN POOL = ' ||
             PUT(ISYPCMQP,7.2);
    LINK HIT;
  END;

This exception test is processed for each observation in the
latest cycle of the DETAIL IMS System Activity File (IMSISY).
The test is positive when the percent of message queue
manager requests falls below the installation-defined limit.
When the test is positive, the exception is categorized by
providing the appropriate values for EXCCODE, SEVERITY, and
MGMTAREA.  EXCDESC1 provides a constant title for the
exception.  EXCDESC2 provides variable information for the
conditions that caused the test to be positive.  The LINK HIT
statement invokes a routine that causes the exception
condition to eventually be written to the Exception Activity
File (ADMEXC) for later processing by the standard reports or
MICF inquiries.

The values for most exception conditions should be determined
uniquely for different environments within a single
organization.  For example, a system paging rate that would
be excessive during the nightly batch processing may be
normal during the daytime hours that have heavy interactive
usage.  Also, different processors can support different
paging rates.  Numbers used as exception values should not be
defined without some analysis of installation history,
performance, and user requirements.

Remember to use the information in the CKPTMASK data element
(Checkpoint Record Component Mask) when assigning values to
exception conditions.  CKPTMASK tracks the checkpoints
encountered in the IMS log, which enables you to determine
the applicability of data element values used in your
exception tests.

The exception value analysis routine uses the CA MICS Data
Base to produce a report that provides a statistical analysis
of the values of the variables used in the standard exception
tests distributed with the products.  Using the results of
this analysis, along with your installation's internal
political, security, or standards policies, industry
publications, and possibly your own analysis of data element
behavior, you can determine the modifications that you should
make to each exception test to provide meaningful exceptions
in your environments.

You can also modify the exception test routine to add your
own tests for additional exception conditions not detected by
the standard tests delivered with the product.