Previous Topic: 12. INSTALLATIONNext Topic: 12.2 Backups, Restores, and Compression


12.1 Installation Procedure


Instructions for loading the CA MICS Capacity Planner were
included with the CA MICS product distribution tape. In the
second step of these instructions you ran the product load
job to copy all required product modules and members into
your CA MICS libraries. Use the following checklist to
complete the installation of the CA MICS Capacity Planner.
All references to the PIOM are to sections of the CA MICS
Planning, Installation, Operation, and Maintenance Guide.

___ 1. Using the JCL shown in Figure 12-1, allocate a shared
       capacity planning database for your installation. The
       MICSNDBx cataloged procedure is used to execute the
       program, where x is the database identifier of the
       primary CA MICS unit database. If you are unfamiliar
       with your CA MICS database identifiers, consult your
       CA MICS System Administrator.


  //ALLOCATE   EXEC MICSNDBx
  //*
  //* SHARED CAPACITY PLANNING DATABASE ALLOCATION
  //* SPECIFY VOLSER AND UNIT TYPE
  //*
  //CAPACITY   DD DSN=sharedprefix.MICS.CAPACITY,
  //           DISP=(NEW,CATLG,DELETE),
  //           DCB=(DSORG=PS,RECFM=FS),
  //           SPACE=(TRK,(300,50)),UNIT=____,VOL=SER=______
  //SYSIN      DD *
  DATA CAPACITY.DUMMY; DUMMY=1; RUN;
  //


 Figure 12-1.  Capacity Planning Database Allocation JCL

       Note that the 300 tracks specified is an estimate of
       initial requirements.  You should carefully monitor
       the space utilization of the capacity planning
       database to optimize DASD utilization.

___ 2. Update the product statement in JCLDEF in the primary
       unit to include the character string 'CAP' to indicate
       the product is installed.

        +---------------------------------------------------+
        | Reference(s):  PIOM,  Section 2.3.3.2.1.1         |
        +---------------------------------------------------+

___ 3. Generate jobs GDGSGEN, BACKUP, BACKUPM, and MONTHLY
       using the JCLGENU job.

        +---------------------------------------------------+
        | Reference(s):  PIOM,  Section 3.5.3.4             |
        +---------------------------------------------------+

___ 4. Run the GDGSGEN job.

        +---------------------------------------------------+
        | Reference(s):  PIOM,  Section 3.5.6.3             |
        +---------------------------------------------------+

___ 5. Run a CGEN for all the products you have installed in
       your complex.  The CGEN jobs exist in your
       sharedprefix.MICS.CNTL library.

        +---------------------------------------------------+
        | Reference(s):  PIOM,  Section 3.4.3               |
        +---------------------------------------------------+

       Note that if you do not run a CGEN for all of your
       installed products, you will experience errors when
       using the Capacity Planner Online Facilities.

You have now completed the product installation.