3. Installation › 3.8 Installation Checklists › 3.8.1 Installing a CA MICS Complex › 3.8.1.1 Unload the Distribution Medium

3.8.1.1 Unload the Distribution Medium

 __ 1. Define Catalog Index Sharedprefixes

       Define the catalog index for the sharedprefix.

       No action is required if the high-level node-name
       already has been defined as an alias in the master
       catalog.

       +---------------------------------------------------+
       | Reference(s): Section 3.2.1                       |
       +---------------------------------------------------+

 __ 2. Install CA Common Services and LMP Keys

       Ensure that CA Common Services is operational.

       CA License Management Program (LMP), one of the CA
       Common Services, is required before you can install
       or run CA MICS.

       To run CA MICS r11 or higher, you must define the
       keys needed for CA LMP.

       +---------------------------------------------------+
       | Reference(s): Section 3.2.2                       |
       +---------------------------------------------------+

 __ 3. Review Cover Letter and PMLs

       Review the cover letter and associated product
       maintenance letters (PML) for the latest important
       technical information.

 __ 4. Copy Load Files

       Copy the files which load the CA MICS system.

       To start the installation, two "tapeload" data sets
       must be created. They contain JCL and load modules
       that are required to complete the installation.

       To create the data sets:

         - See Section 3.2.3.1 if installing from ESD PAX.
         - See Section 3.2.3.2 if installing from tape.

       +---------------------------------------------------+
       | References: Sections 3.2.3, 3.2.3.1, 3.2.3.2      |
       +---------------------------------------------------+

 __ 5. Load Production Libraries

       Load the CA MICS production libraries using ESD PAX or
       tape.  They both contain all code and documentation
       for the entire CA MICS product line in a compressed
       format.  The installation job uses the CA LMP keys to
       identify and decode the modules that belong to your
       licensed CA MICS products.

       Modules are written to disk by executing the program
       named LPEBLDD.  It runs as a "nonauthorized" program.
       Some mainframe security systems, such as CA Top
       Secret, have a feature that restricts nonauthorized
       programs from writing authorized load modules.  (An
       authorized load module is link-edited with an
       attribute of AC(1).) If your site has this security
       feature activated and is licensed for the CA MICS DASD
       Space Collector (VCC), then the load job will fail
       with an S913 abend while trying to write an authorized
       VCC load module.  To prevent this abend, request your
       security administrator to permit LPEBLDD to write
       authorized load modules.

       To load the production libraries:

       - See Section 3.2.4.1 if installing from ESD PAX.
       - See Section 3.2.4.2 If installing from tape.

       +---------------------------------------------------+
       | References: Sections 3.2.4, 3.2.4.1, 3.2.4.2      |
       +---------------------------------------------------+

 __ 6. Retain Distribution Tape and Load Libraries


       Retain the "tapeload" libraries for future optional
       product installation. They are:

       o  sharedprefix.MICS.TAPELOAD.CNTL
       o  sharedprefix.MICS.TAPELOAD.LOAD

       In addition, if you installed CA MICS from a tape,
       retain the tape for future optional product
       installation.

       If you installed from ESD PAX, there is no need to
       retain the interim libraries since they can be
       downloaded from Support Online when they are needed.

 __ 7. (CONDITIONAL) Conversion to SAS 9.1.3 ONLY

       If you are converting to SAS 9.1.3, the SAS Autocall
       library (sasprefix.W0.AUTOLIB) must be converted to a
       fixed block data set to address issues documented in
       SAS Usage Note SN-013990.  Review this SAS Usage Note
       before proceeding with the rest of this conversion
       checklist.

       This data set should be used only for CA MICS, and is
       only necessary for SAS 9.1.3.  The fixed-block version
       of the SAS Autocall library must be created with an
       LRECL of 80 and a BLKSIZE that is a multiple of 80.

       Note that standard IBM utilities, such as IEBCOPY,
       will not copy variable blocked data sets to fixed
       block.

       The following is a sample job using the SAS provided
       VBGT72 macro, referenced in SN-013990 to copy the SAS
       Autocall library. VBGT72 must be downloaded from the
       SAS institute support site before it can be used. In
       this example, VBGT72 was downloaded and then saved
       as member VBGT72 in sasprefix.VBGT72.LIBRARY:


       //    ....JOB....
       //VBGT72   EXEC SAS
       //VBGT72   DD DISP=SHR,DSN=sasprefix.VBGT72.LIBRARY
       //ISASAUTO DD DISP=SHR,DSN=sasprefix.W0.AUTOLIB
       //AUTOOUT  DD DISP=(NEW,CATLG,DELETE),
       //    DSN=micssasprefix.FB.W0.AUTOLIB,
       //    UNIT=unit,VOL=SER=volume,
       //    DCB=(LRECL=80,RECFM=FB,BLKSIZE=6160),
       //    SPACE=(CYL,(1,1,45))
       //SYSIN    DD *
        %INCLUDE VBGT72(VBGT72);
        %VBGT72(indd=ISASAUTO);
       //

       The JCL will need to be modified before submission to
       suit your site requirements.

       Alternatively, the copy utility provided with ISPF
       (Option 3.3) can be used.