|
|
|
NOTE: Please review the "Procedures for using the ACS
Test Facility" section before attempting to use
this facility. This section is contained in the
description of the ACS Test Case Creation
facility.
Source: ACS Test Case Library
ACS Testing Output Report File
Function: This facility analyzes the results of the ACS
routine testing process to make sure your ACS
routines are working correctly. Another CA MICS
StorageMate facility, the ACS Test Case Creation
facility, is used to build a library of ACS test
cases from your CA MICS data. That library is
read by the ISMF ACS Test Facility, and each test
case is passed to your production/test ACS
Routine(s). The test results are written by ISMF
to a report output file. This facility reads both
the test case library and the testing output file,
merges them, and provides a number of reports
useful in evaluating the operation of the ACS
routines.
This particular report provides a summary page of
general statistics, useful for obtaining a quick
impression of the overall testing results. Other
reports may then be used to provide more detail or
to explore anomalies.
Further information about the use of the ACS Test
Facility is available in the facility instructions
at the end of this section.
Features: Options allow you to restrict reporting to only
those ACS routines specified. For example, when
executing the ISMF Test Facility you can specify
that all four types of ACS routines be executed
(Storage Class, Management Class, Data Class,
Storage Group), but when running reports you can
only be interested in results of the Data Class
routine.
Up to eight different reports may be generated by
this facility, each showing a different view of
the test results, or showing a different
summarization. The reports can be selected in any
combination.
SMS
Issues: An important phase of any SMS conversion project
is making sure your ACS routines are operating
correctly and achieving their desired results.
This problem is no less critical after SMS
conversion, because regular maintenance to the ACS
routines will still be necessary. Because of
their critical nature, accuracy of ACS routines is
just as important as the accuracy of any system
exit. Using this facility to carefully analyze
your test results will help insure your success in
this critical task.
COLUMN DESCRIPTIONS
TOTAL NUMBER OF TEST CASES:
A numeric value indicating the total number of
test cases that were processed by the ACS Test
Facility.
STORAGE CLASS COUNTS:
The statistics following this heading apply to the
testing of the storage class ACS routine. Refer
to the 'Common Values' section below for a
description of each of these items.
MANAGEMENT CLASS COUNTS:
The statistics following this heading apply to the
testing of the management class ACS routine.
Refer to the 'Common Values' section below for a
description of each of these items.
DATA CLASS COUNTS:
The statistics following this heading apply to the
testing of the data class ACS routine. Refer to
the 'Common Values' section below for a
description of each of these items.
STORAGE GROUP COUNTS:
The statistics following this heading apply to the
testing of the storage group ACS routine. Refer
to the 'Common Values' section below for a
description of each of these items.
(Common Values)
ACS ROUTINE INVOCATION:
A numeric value indicating the total number of
times this ACS routine was invoked in this test.
The data class and storage class ACS routines
should be called for every test case. The
management class ACS routine should be called for
every managed data set, with a few exceptions such
as VIO data sets. The storage group ACS routine
should be called for every managed data set.
RETURN CODE NOT ZERO:
A numeric value indicating the number of times the
ACS routine completed with a non-zero return code.
This condition would cause the allocation to fail
if the routine were running in a production
environment. The number in parentheses indicates
the percentage of the total calls to this ACS
routine that had this result.
VALID CLASS/GROUP VALUE ASSIGNED:
A numeric value indicating the number of calls to
this ACS routine that resulted in a zero return
code, and a valid (non-blank) class/group name
being assigned. The number in parentheses
indicates the percentage of the total calls to
this ACS routine that had this result.
BLANK (NULL) VALUE ASSIGNED:
A numeric value indicating the number of calls to
this ACS routine that resulted in a zero return
code, but a null (blank) class/group name being
assigned. The number in parentheses indicates the
percentage of the total calls to this ACS routine
that had this result.
ACS TESTING RESULTS (STGELG) CA MICS StorageMate - STATISTICS ABC CORPORATION TOTAL NUMBER OF TEST CASES: 416 STORAGE CLASS COUNTS: ACS ROUTINE INVOCATION: 416 RETURN CODE NOT ZERO: 5 ( 1%) VALID CLASS VALUE ASSIGNED: 398 ( 96%) BLANK (NULL) VALUE ASSIGNED: 13 ( 3%) MANAGEMENT CLASS COUNTS: ACS ROUTINE INVOCATION: 396 RETURN CODE NOT ZERO: 0 ( 0%) VALID CLASS VALUE ASSIGNED: 386 ( 97%) BLANK (NULL) VALUE ASSIGNED: 10 ( 3%) DATA CLASS COUNTS: ACS ROUTINE INVOCATION: 416 RETURN CODE NOT ZERO: 0 ( 0%) VALID CLASS VALUE ASSIGNED: 358 ( 86%) BLANK (NULL) VALUE ASSIGNED: 58 ( 14%) STORAGE GROUP COUNTS: ACS ROUTINE INVOCATION: 398 RETURN CODE NOT ZERO: 0 ( 0%) VALID GROUP VALUE ASSIGNED: 398 (100%) BLANK (NULL) VALUE ASSIGNED: 0 ( 0%)
Figure 4-6. ACS Testing Results / Statistics
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |