Figure 2-8 illustrates the operation of the Exception Reports process. The Database, Database Exception File, Standard Exception Reports, and MICF Exception Inquiry are standard parts of this process. The User-Defined Exception Analyzer comprises the part of this system which tailors and modifies the exceptions to uniquely address an installation's requirements.
+-----------+
| |
| Database |
| |
+-----------+
|
|
+-----------+
| User- |
| Defined |
| Exception |
| Analyzer |
+-----------+
|
+-----------+
| Database |
| Exception |
| File |
+-----------+
|
+-----------------------+
| |
+-----------+ +-----------+
| Standard | | MICF |
| Exception | | Exception |
| Reports | | Inquiry |
+-----------+ +-----------+
The exceptions are defined with each product and a
starter set of default values is provided. It is the
responsibility of each installation to review this starter
set and modify the values used for exception identification
to adjust them for applicability to your environment and
requirements.
The exception values are defined in a single source
member for each CA MICS product (e.g., TSO, RMF, SMF) in the
CA MICS source library (e.g., prefix.MICS.USER.SOURCE). An
exception group exists for each unique file that is to be
processed by the Exception Analyzer and consists of the
exceptions which are to be processed using a specific file.
ABOUT EXCEPTION TESTS
An exception test defines the tests performed to determine whether or not an exception condition exists and needs to be reported. The test also states the exception's identifying number and its severity and management levels. You can modify, and in some cases add, values to adjust the exception test to meet your installation's requirements. Exception tests reside in sharedprefix.MICS.SOURCE, in modules named DYcccEXC, where ccc is the three-character product identifier. The exception code is organized sequentially by exception number within the member. Each exception condition consists of the standard identification definition (e.g., severity level), exception-dependent criteria (e.g., amount of CPU time used), and standard selection facilities (e.g., selection of prime-time hours only). To modify an exception, locate it by name or number, then change the value directly in the code. Refer to the Exceptions chapter of the individual product guides for detailed exception information for the products licensed by your site.
EXCEPTION VALUE ANALYSIS
The Exception Value Analysis Process is a procedure by which
the CA MICS Database is used to determine the values to be
used for exceptions. Figure 2-9 illustrates the operation of
the Exception Value Analysis Process. The Exception Value
Analyzer extracts values from the database for those
exception values which are to be analyzed. Descriptive
statistics for the selected variables are printed in the
Exception Value Analysis Report.
+------------+
| |
| Database |
| |
+------------+
|
+------------+
| Exception |
| Value |
| Analyzer |
+------------+
|
+------------+
| Exception |
| Value |
| Report |
+------------+
Figure 2-9. Exception Value Analysis Operational Flow
EXCEPTION VALUE ANALYSIS REPORTS
Exception Value Analysis Reports help you determine the values to use in the exception tests coded in DYcccEXC. There is one report available for each CA MICS product. The code to produce the report is located in sharedprefix.MICS.SOURCE(cccEVA), where ccc is the three-character product identifier. For each data element used in an exception test, this report shows twelve statistical measures, described below. It also shows a recommended value. Figure 2-10 illustrates the format of this report. The heading shows the report title, system being reported on, the date on which the report was run, and company and product identification. The body of the report is grouped by exception number. After the exception number and name, the report shows the data elements used in the exception test. For each element, the report gives its name and descriptive title. Some exception data elements are repeated for sub-groups of exception tests. (e.g., disk or tape). For these exceptions a qualifier is shown. The number of observations used to calculate the measures are printed. The statistical measures are divided into three types: basic, standard deviations, and percentiles. Basic statistical values are the minimum, mean, median, and maximum values. Standard deviation values are the mean plus and minus one and two standard deviations. Percentile values include the 1st, 5th, 95th, and 99th percentile values. The CA MICS SUGGESTED VALUE is the system's choice of the statistical function (e.g., 99th percentile) that most closely meets the requirement. This value provides you with a representative initial exception value. The INDUSTRY RECOMMENDED VALUE is not supported at this time.
CA MICS Y O U R C O M P A N Y N A M E PAGE 1 EXCEPTION VALUE ANALYSIS SYSTEM: SYSP - PRODUCTION TSO RUN DATE: WEDNESDAY, OCT 4, 2000 INFORMATION AREA: TSO ----------------------------------------------------------------------------------------------------------------------------------| EXCEPTION | QUALIFIER / | EXCEPTION DESCRIPTION / | NUMBER | DATA ELEMENT | DATA ELEMENT DESCRIPTION AND STATISTICAL VALUES | -----------------------------+----------------------------------------------------------------------------------------------------| 00001 | INTERACTIVE TSO RUN EXCEEDED ELAPSED TIME STANDARD | TSIELPTM | EXECUTION ELAPSED TIME OBSERVATIONS: 632 | |----------------------------------------------------------------------------------------------------| BASIC STATISTICAL VALUES: | MIN: 0.020 | MEAN: 690.425 | MEDIAN: 110.660 | MAX: 5079.387 | STANDARD DEVIATION VALUES: | -2: . | -1: . | +1: 1862.770 | +2: 3035.115 | PERCENTILE VALUES: | 1ST: 0.289 | 5TH: 1.180 | 95TH: 3650.541 | > 99TH: 4448.140< | *----------------------------------------------------------------------------------------------------| INDUSTRY RECOMMENDED VALUE: N/A CA MICS SUGGESTED VALUE: 1:14:08 HH:MM:SS ( 4448 SECONDS) | ----------------------------------------------------------------------------------------------------------------------------------| 00002 | INTERACTIVE TSO RUN EXCEEDED RESOURCE USAGE LIMIT | TSICPUTM | CPU TIME CONSUMED OBSERVATIONS: 632 | |----------------------------------------------------------------------------------------------------| BASIC STATISTICAL VALUES: | MIN: 0.010 | MEAN: 1.752 | MEDIAN: 0.300 | MAX: 87.789 | STANDARD DEVIATION VALUES: | -2: . | -1: . | +1: 8.189 | +2: 14.626 | PERCENTILE VALUES: | 1ST: 0.020 | 5TH: 0.060 | 95TH: 5.162 | > 99TH: 30.047< | *----------------------------------------------------------------------------------------------------| INDUSTRY RECOMMENDED VALUE: N/A CA MICS SUGGESTED VALUE: 0:00:30 HH:MM:SS ( 30 SECONDS) | ----------------------------------------------------------------------------------------------------------------------------------| 00002 | INTERACTIVE TSO RUN EXCEEDED RESOURCE USAGE LIMIT | TSIEXCPS | I/O (EXCP S) GENERATED OBSERVATIONS: 632 | |----------------------------------------------------------------------------------------------------| BASIC STATISTICAL VALUES: | MIN: 0.000 | MEAN: 293.239 | MEDIAN: 12.000 | MAX: 38261.000 | STANDARD DEVIATION VALUES: | -2: . | -1: . | +1: 2028.385 | +2: 3763.532 | PERCENTILE VALUES: | 1ST: 0.000 | 5TH: 0.000 | 95TH: 1084.599 | > 99TH: 3662.348< | *----------------------------------------------------------------------------------------------------| INDUSTRY RECOMMENDED VALUE: N/A CA MICS SUGGESTED VALUE: 3662 | ----------------------------------------------------------------------------------------------------------------------------------| 00002 | INTERACTIVE TSO RUN EXCEEDED RESOURCE USAGE LIMIT | TSISERVU | SERVICE UNITS OBSERVATIONS: 632 | |----------------------------------------------------------------------------------------------------| BASIC STATISTICAL VALUES: | MIN: 0.000 | MEAN: 13749.310 | MEDIAN: 2005.000 | MAX: 903687.000 | STANDARD DEVIATION VALUES: | -2: . | -1: . | +1: 68567.899 | +2: 123386.489 | PERCENTILE VALUES: | 1ST: 0.000 | 5TH: 150.600 | 95TH: 42008.693 | > 99TH: 228175 497< | *----------------------------------------------------------------------------------------------------| INDUSTRY RECOMMENDED VALUE: N/A CA MICS SUGGESTED VALUE: 228175 | ----------------------------------------------------------------------------------------------------------------------------------| 00103 | INTERVAL TSO SYSTEM RESOURCE OVERLOAD | TSOEXCPS | I/O (EXCP S) GENERATED OBSERVATIONS: 197 | |----------------------------------------------------------------------------------------------------| BASIC STATISTICAL VALUES: | MIN: 884.000 | MEAN: 4808.061 | MEDIAN: 3985.000 | MAX: 23258.000 | STANDARD DEVIATION VALUES: | -2: . | -1: 1490.541 | +1: 8125.581 | +2: 11443.101 | PERCENTILE VALUES: | 1ST: 1027.560 | 5TH: 1639.700 | 95TH: 10394.994 | > 99TH: 20619.471< | *----------------------------------------------------------------------------------------------------| INDUSTRY RECOMMENDED VALUE: N/A CA MICS SUGGESTED VALUE: 20619 | ----------------------------------------------------------------------------------------------------------------------------------|
EXCEPTION VALUE ANALYSIS ROUTINES
The Exception Value Analysis routines are defined in sharedprefix.MICS.SOURCE(cccEVA) as described in the prior section. An exception group exists for each file that is to be processed by the Exception Value Analyzer. The job control to execute the EVA process is contained in the prefix.MICS.CNTL library. Each product has a separate member in the library; member names are cccEVA, where ccc is the product's three-letter identifier. To perform an analysis of exception values for a product, submit the applicable job from the prefix.MICS.CNTL library: SUB 'prefix.MICS.CNTL(cccEVA)'
ASSIGNING EXCEPTION VALUES
The procedure below describes adjusting the values used
by the CA MICS Exception Analyzers.
1. Identify the exceptions you want to change.
2. List the Exception Analyzer member in
sharedprefix.MICS.SOURCE(DYcccEXC), where ccc is the product
identifier.
3. Execute the applicable Exception Value Analysis job
according to the instructions provided in the previous
section.
4. Using the source listing of the Exception Analyzer
and the corresponding Exception Value Analysis Report, mark
up the source listing with the new exception values. The
exceptions are ordered by number.
5. Copy the routine to be changed to a test library and
make the changes.
6. Test the routine by executing it to ensure that there
are no syntax errors.
7. Copy the modified source member back to the
production user source library, prefix.MICS.USER.SOURCE,
maintaining the original copy in the sharedprefix.MICS.SOURCE
library.
8. Monitor the next day's production execution of the
exception reports to ensure that the adjustments have been
correctly implemented.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |