|
|
|
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.
The storage class ACS routine has a dual function,
because it must decide whether a data set should be
managed as well as determining the class to be
assigned to it. The analysis reports are useful in
making sure the first function is working
correctly. One analysis report will show all data
sets that would be managed, while the other shows
those that would not be managed. These reports can
only be requested if you specified that the storage
class ACS routine be invoked as part of the testing
process.
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 may
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, as 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 ensure your success in this
critical task.
COLUMN DESCRIPTIONS
TITLE 4
The fourth title line of the report indicates which
analysis report is being produced. This title will
be either 'MANAGED DATA SETS' or 'UNMANAGED DATA
SETS'. If a test case is assigned a blank storage
class, it will not be managed. A non-blank value,
as well as a return code of zero, indicates SMS
will manage the data set.
SYSID
This value appears at the top of each page and
identifies the system to which this data applies.
The System Identifier (SYSID) is copied from the
CA MICS data used in creating the test cases.
Maximum Return Code
A numeric value indicating the maximum return code
received from any of the ACS routines called on
behalf of this test case. This column will be
blank if the return code was zero. Examination of
the next four columns (class and group names)
should reveal the error codes presented by
individual routines.
Storage Class Name
The name of the storage class assigned to this data
set by the storage class ACS routine. A BLANK
value indicates that the ACS routine was not
invoked for this data set. A value of '(NONE)'
indicates that the ACS routine was called, but no
value was assigned. This null value should never
be present for a managed data set, but should
always be present for an unmanaged one. A value of
'*RC=nnnn' indicates a non-zero return code from
the routine, where 'nnnn' is the numeric
representation of the return code.
Manage. Class Name
The name of the management class assigned to this
data set by the management class ACS routine. A
BLANK value indicates that the ACS routine was not
invoked for this data set. A value of '(NONE)'
indicates that the ACS routine was called, but no
value was assigned. A value of '*RC=nnnn'
indicates a non-zero return code from the routine,
where 'nnnn' is the numeric representation of the
return code.
Storage Group Name
The name of the storage group assigned to this data
set by the storage group ACS routine. A BLANK
value indicates that the ACS routine was not
invoked for this data set. A value of '(NONE)'
indicates that the ACS routine was called, but no
value was assigned. A value of '*RC=nnnn'
indicates a non- zero return code from the
routine where 'nnnn' is the numeric representation
of the return code.
Data Class Name
The name of the data class assigned to this data
set by the data class ACS routine. A BLANK value
indicates that the ACS routine was not invoked for
this data set. A value of '(NONE)' indicates that
the ACS routine was called, but no value was
assigned. A value of '*RC=nnnn' indicates a non-
zero return code from the routine, where 'nnnn' is
the numeric representation of the return code.
Data Set Name
The name of the data set passed to the testing
routine for this test case.
Test Case Member
Identifies the test case library member (PDS
member) that was passed to the ACS test routine.
You may want to browse this member in the test case
library to identify the actual values passed to the
ACS routine. This is especially valuable when
investigating errors or improper results in the ACS
routines.
Size (KB)
The calculated size of the identified data set as
passed to the ACS routine. The value is
represented in kilobytes (thousands of bytes).
This value is important as the ACS routine often
makes decisions based on it.
Input Type
The location of the original data set upon which
this test case was based. This value is supplied
by the ACS Test Case Creation function, based on
the original source of the data. Valid values are
DASD (VCADAA file), VSAM (VCA_VS file), TAPE
(External), MIGRATE (HSMMIG file), or BACKUP
(HSBBAC file).
ACS TESTING RESULTS (STGELG) CA MICS StorageMate - ANALYSIS ABC CORPORATION UNMANAGED DATA SETS ------------------------------------------------------------ SYSID=SYSA ------------------------------------------------------------ Maximum Storage Manage. Storage Data | Data Set Name Test Size Input Return Class Class Group Class | Case (KB) Type Code Name Name Name Name | Member (NONE) DCPS | CSA.RCP.COMPLOAD.PREPROC @CSAA002 94.9 DASD (NONE) DCPS | CSUT.AXXXX250.XXX.CLOSED.ADJUST.CNTL @CSUA001 712.1 DASD (NONE) DCPO | CSUT.PSTEST0C.INCLLIB @CSUA004 1139.4 DASD (NONE) DCPO | DA1TES1.TSOTST.PROCLIB @DA1A001 56.7 DASD (NONE) DCPS | DA1TES2.MAST.USER.PSTS.LIST @DA1A002 2.0 MIGRATE (NONE) DCPS | DA2TEST.NDXX.D01214.T161007 @DA2A002 2.0 MIGRATE (NONE) DCPS | DBRT.DALYTRAN.BACKUP.G1594V00 @DBRA001 7858.4 TAPE (NONE) DCPS | DBRT.PACK.DBXX01.G1688V00 @DBRA002 206257.0 TAPE (NONE) DCPS | DDAT.DDATEST4.TRNORT.BKOKD.G3188V00 @DDAA001 21533.2 TAPE (NONE) DCPO | DSITEST.ASM.CLASS @DSIA006 192.5 MIGRATE (NONE) (NONE) | DXBXXX.BXXX302.MODLDSCB @DXBA040 0.0 DASD (NONE) DCPS | WDDA.PROD.TEST1.XXXBEXT.BKUP @WDDA004 9113.3 TAPE (NONE) DCPS | WDDA.TESTDBTC.STEP21.PRTEST.G0002V00 @WDDA005 32.8 TAPE ----- ------------ SYSID 246994.4 ============ 246994.4 N= 13
Figure 4-9. ACS Testing Results / Analysis
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |