ACS Test Case Creation (STGELF)


Source:   VCADAA file at the DETAIL timespan
          VCA_VS file at the DETAIL timespan
          HSMMIG file at the DETAIL timespan
          HSBBAC file at the DETAIL timespan
          Tape library information (external)

Function: This facility obtains data about your existing data
          sets from up to five different input sources, and
          uses these data to build test cases for your ACS
          routines.  These test cases can then be used as
          input to the ISMF ACS Testing facility to make sure
          your current or proposed ACS routines work
          correctly under a wide variety of conditions.

          The output of this facility includes a summary
          report and a jobstream in your Work Data Set that
          can then be used to allocate a test case data set,
          and populate it with test cases constructed from
          your own data.

          The ISMF ACS Testing facility can then process the
          test case library you have built, passing each test
          case to your ACS routines (either the active ones
          or test versions).  The results of these tests will
          produce a report file that can then be analyzed by
          another CA MICS StorageMate facility--ACS Testing
          Results.

          Further information about the use of the ACS Test
          Facility is available in the facility instructions
          at the end of this section.

Features: The ISMF ACS Testing facility allows you to build
          your own test cases, but the information has to be
          entered manually through ISPF, with each completed
          panel resulting in only one test case.  This
          facility provides a mechanism that is faster and
          less prone to error.

          Much of the information needed to describe each
          data set can be extracted directly from the CA MICS
          database.  If your ACS routines are dependent upon
          information not in the database (such as the
          creating jobname of the data set), a secondary
          screen can be used to supply these values to all
          created test cases.  Your own SAS code can also be
          inserted at a special exit point that receives
          control after each test case has been constructed.

          Because the number of data sets represented by even
          one cycle of CA MICS data may be prohibitive, two
          options have been included that reduce the number
          of test cases created.  The Random option will
          select final test cases at a user-specified
          interval, such as every 5th case or every 20th
          case.  The Subset option will include all data sets
          having unique characteristics, while excluding
          those similar to cases already selected.  This
          option considers such factors as the data set name,
          data set size, accounting fields, and data set
          organization.

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.
          Testing your routines with a large number of test
          cases will help insure your success in this
          critical task.

COLUMN DESCRIPTIONS

   SUMMARY OF TEST CASES CREATED IN MEMBER name OF
   DATA SET dsname
         This informational line identifies the Work Data Set
         (dsname) and member (name) containing the jobstream
         that will create and populate the test case library.
         This jobstream should be edited, if necessary, and
         then submitted to create the test case library.

   CASES FROM DASD DATA (NON-VSAM)
         A numeric value that represents the total number of
         test cases created from the CA MICS VCADAA file.
         VCADAA contains information about non-VSAM data sets
         that reside on primary (Level 0) DASD.

   CASES FROM DASD DATA (VSAM)
         A numeric value that represents the total number of
         test cases created from the CA MICS VCA_VS file.
         VCA_VS contains information about VSAM data sets
         that reside on primary (Level 0) DASD.

   CASES FROM TAPE DATA
         A numeric value that represents the total number of
         test cases created from data representing your tape
         library.  This information is obtained from an
         external data set you provided.  The MICSLOG report
         should identify the name of the data set that was
         used.

   CASES FROM HSM MIGRATION DATA
         A numeric value that represents the total number of
         test cases created from the CA MICS HSMMIG file.
         This file contains information about data sets that
         previously resided on DASD, but have migrated to
         either Level 1 or Level 2 HSM storage.

   CASES FROM HSM BACKUP DATA
         A numeric value that represents the total number of
         test cases created from the CA MICS HSBBAC file.
         This file contains information about data sets that
         have one or more versions available on HSM backup
         storage.

   *TOTAL TEST CASES GENERATED*
         A numeric value that represents the total number of
         test cases created in the test case library.  This
         number should be the sum of all the values described
         above.

ACS TEST CASE CREATION (STGELF) CA MICS StorageMate ABC CORPORATION SUMMARY OF TEST CASES CREATED IN MEMBER ACS0412 OF DATA SET STORADMN.MICSSTOR.CNTL CASES FROM DASD DATA (NON-VSAM) 742 CASES FROM DASD DATA (VSAM) 104 CASES FROM TAPE DATA 503 CASES FROM HSM MIGRATION DATA 379 CASES FROM HSM BACKUP DATA 5 -------- *TOTAL TEST CASES GENERATED* 1733


 Figure 4-5.  ACS Test Case Creation