Modifying standard exceptions to reflect the concerns of your
installation is a two-step process: selecting the exceptions
that are significant in your environment and establishing and
coding norms for the chosen exceptions.
SELECTING CA MICS EXCEPTIONS
CA MICS provides a variety of exception tests in order to
meet the needs of its user base.
The exception tests are organized in the following ways:
o By exception number for unique identification. The
range of exception numbers is listed by file name in
Figure 4-1.
o By severity level to signify degree of importance.
There are three levels: warning, impacting, and
critical.
o By management area to identify responsibility. These
include availability, performance, productivity,
security, service, standards, and workload.
+----------------+-------------------------------------+
| DYIDMEXC | Standard IDMS Exceptions |
+----------------+-------------------------------------+
| Exception | Database File Name |
| Number Range | |
+----------------+-------------------------------------+
| 13001-13013 | DAYS.IDMSUA01 |
| 13020 | DETAIL.IDMSIN01 |
+----------------+-------------------------------------+
Figure 4-1 IDMS Analyzer Exception Members
MODIFYING THE CODE
The exception tests are organized by exception number within
sharedprefix.MICS.SOURCE(DYIDMEXC). This code sets the
severity level, management area, and selection criteria for
each exception test. Each exception test condition lists its
name and number so that it can be located easily within the
DYIDMEXC member. If you need to modify the code, copy it to
prefix.MICS.SOURCE(DYIDMEXC) and change it there. Code
modifications should only be made by the System
Administrator.
Figure 4-2 lists the standard exceptions provided with the
IDMS Analyzer, including the exception number, severity
level, management area, and descriptive title.
+--------+------------+-----------------+--------------------------------------------------------+ | Number | Severity | Management Area | Exception Description | +--------+------------+-----------------+--------------------------------------------------------+ | 13001 | Impacting | Performance | Terminal Errors | | 13002 | Impacting | Performance | Storage Kept Exceeds Limit | | 13003 | Impacting | Performance | Database Calls Exceed Limit | | 13004 | Impacting | Performance | Active Storage Exceeds Limit | | 13005 | Impacting | Performance | ADS/O Levels Exceed Limit | | 13006 | Impacting | Performance | Average System CPU Time Exceeds Limit | | 13007 | Impacting | Performance | Average User CPU Time Exceeds Limit | | 13008 | Impacting | Performance | Maximum Total Response Time Exceeds Limit | | 13009 | Impacting | Performance | Maximum Short Response Time Exceeds Limit | | 13010 | Impacting | Performance | Maximum Medium Response Time Exceeds Limit | | 13011 | Impacting | Performance | Maximum Long Response Time Exceeds Limit | | 13012 | Impacting | Performance | Maximum Conversational Response Time Exceeds Limit | | 13013 | Impacting | Performance | Maximum User Response Time Exceeds Limit | | 13020 | Impacting | Performance | Task ABENDs | +--------+------------+-----------------+--------------------------------------------------------+
Figure 4-2. IDMS Analyzer Exception List
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |