Previous Topic: 3.3 Define Database ComplexNext Topic: 3.3.2 Generate Complex-Level JCL Jobs, PROCs, CLISTs


3.3.1 SAS Libraries Used by CA MICS


 The following list of the SAS libraries is required for CA
 MICS. The configuration members for SAS version 9.1.3 is
 BATW0, usually located in the your.SAS.CNTL data set.
 Beginning with SAS 9.2, there are four configuration members,
 BATCH, COMMON, ENW0, and SITE that are usually located in the
 your.SAS.CONFIG data set.
 
 The TKMVSENV SAS library was introduced with SAS 9.1.3.  SAS
 9.3 allows symbolic references in the SAS configuration
 files.  Use of symbolic references requires access to the
 TKMVSENV file where these references are defined.  If your
 SAS administrator used symbolic references in the SAS config
 files or elsewhere, the TKMVSENV file is required.  It is
 also required if you intend to use SAS features that require
 JAVA while executing within a CA MICS cataloged procedure.
 
 If you copy this library under a different name for exclusive
 use by CA MICS, you might need to modify the contents to
 ensure any references to the high-level-qualifier of the SAS
 library names are also changed.
 
   your.SAS.LIBRARY
   your.SAS.AUTOLIB
   your.SAS.SASHELP
   your.SAS.CNTL     (SAS 9.1.3)
   your.SAS.CONFIG   (SAS 9.2 and above)
   your.SAS.SASMSG
   your.SAS.TKMVSENV
 
        We recommend that you maintain one set of CA MICS SAS
        libraries with SAS version-independent data set names.
        When a new SAS version has been thoroughly tested at
        your installation, rename your CURRENT CA MICS
        production SAS libraries to a name that can identify
        the release if necessary, and rename the NEW CA MICS
        SAS libraries to the production data set names
        currently in use.
 
        Using version-independent data set names with CA MICS
        avoids changes to CA MICS JCL and PROCs and simplifies
        the upgrade to a CA MICS supported SAS version.
 
        For example:
 
        Current CA MICS production     New SAS installation
        SAS libraries:                 libraries:
 
        SYS2.SAS.LIBRARY               SYS2.SAS94.LIBRARY
        SYS2.SAS.CONFIG                SYS2.SAS94.CONFIG
        SYS2.SAS.TKMVSENV              SYS2.SAS94.TKMVSENV
        SYS2.SAS.W0.AUTOLIB            SYS2.SAS94.W0.AUTOLIB
        SYS2.SAS.ENW0.SASMSG           SYS2.SAS94.ENW0.SASMSG
        SYS2.SAS.ENW0.SASHELP          SYS2.SAS94.ENW0.SASHELP
 
        Now that you are ready to use the new SAS version with
        CA MICS, rename your current CA MICS production SAS
        libraries from:
 
        SYS2.SAS.LIBRARY
        SYS2.SAS.CONFIG
        SYS2.SAS.TKMVSENV
        SYS2.SAS.W0.AUTOLIB
        SYS2.SAS.ENW0.SASMSG
        SYS2.SAS.ENW0.SASHELP
 
        TO:
 
        SYS2.SASvnn.LIBRARY
        SYS2.SASvnn.CONFIG
        SYS2.SASvnn.TKMVSENV
        SYS2.SASvnn.W0.AUTOLIB
        SYS2.SASvnn.ENW0.SASMSG
        SYS2.SASvnn.ENW0.SASHELP
 
        Substituting vnn for the SAS version of these
        libraries if desired.
 
        Rename the new SAS version libraries to be used for CA
        MICS from:
 
        SYS2.SAS94.LIBRARY
        SYS2.SAS94.CONFIG
        SYS2.SAS94.TKMVSENV
        SYS2.SAS94.W0.AUTOLIB
        SYS2.SAS94.ENW0.SASMSG
        SYS2.SAS94.ENW0.SASHELP
 
        to the CA MICS production SAS library names currently
        in use:
 
        SYS2.SAS.LIBRARY
        SYS2.SAS.CONFIG
        SYS2.SAS.TKMVSENV
        SYS2.SAS.W0.AUTOLIB
        SYS2.SAS.ENW0.SASMSG
        SYS2.SAS.ENW0.SASHELP
 
        With this naming convention, your CA MICS JCL should
        only require changes or regeneration when a new SAS
        library is added.