2. Planning for Installation and Use of CA MICS › 2.3 Installation Planning and Parameter Specification

2.3 Installation Planning and Parameter Specification

The CA MICS installation process is designed to meet the
needs of a very diverse set of installations.  As such, it
has evolved to contain a great many options, but no one piece
of it is difficult.  The degree of complexity will mainly be
determined by the presence or absence of special standards or
processing requirements for systems run in your shop.

The CA MICS installation process is similar in some respects
to an OS/390 system generation and is performed in a series
of separate stages:

     Database Complex Definition

     Component Installation

     Database Allocation

     Component Activation

The information which the CA MICS installation process needs
to tailor the system must be specified by you in the various
members of the partitioned data sets named "MICS.PARMS."  The
sections that follow explain each specification which you
must make so that the CA MICS installation/generation process
can customize the system to meet your site's requirements.

*************************************************************
*                                                           *
*  CAUTION:  CA MICS does NOT support "dynamic" parameter   *
*            libraries.  Nothing is accomplished by merely  *
*            changing a member of MICS.PARMS.  You MUST     *
*            run the appropriate CA MICS generation         *
*            process for the change to become effective.    *
*                                                           *
*************************************************************

One exception to this rule is the parameters specified in
prefix.MICS.PARMS(EXECDEF).  Changes to this member take
effect the next time CA MICS is run.  This member is
discussed in Section 2.3.5.

Another exception to this rule is the account code derivation
exit routines in sharedprefix.MICS.PARMS.  Changes to these
members take effect the next time CA MICS is run.  These
routines are discussed in section 2.3.1.7 and in the various
product guides.

The parameters you must supply to guide the CA MICS
installation and generation process may be broken down into
four categories:

     Database Complex parameters--those which provide
     information that applies to the entire database complex
     rather than to a particular component or database unit.

     Operational parameters--those which guide the processing
     of the CA MICS system.  For example, the parameters
     which tell CA MICS how many account fields you want in
     the Batch Job file and how to give them values are of
     this type.

     JCL generation parameters--those which tell CA MICS how
     to tailor its batch jobs, macros, and TSO CLISTs to run
     properly at your shop.  The jobs involved in the
     installation process itself must be tailored along with
     those used to actually run and use CA MICS.  For
     example, the parameters that tell CA MICS how to build a
     job card that will be valid in your shop are of this
     type.

     Database configuration and space parameters--those
     which tell CA MICS the number of CYCLEs of each type of
     file that should be kept in the online database, and
     also how much of what data should be kept on tape.  For
     example, the parameters that tell CA MICS how many
     cycles to keep of the TSOTSO file in the YEARS timespan
     are of this type.

The parameters in the above categories feed the JCLGEN,
CYCLEGEN, and parameter generator processes.

Note that not all the parameters which guide CA MICS
execution are documented in this manual.  The CA MICS
Management Objective Reports and Exception Reports are
tailored to your needs by direct modification of their
modules in prefix.MICS.USER.SOURCE.  For more information
about tailoring CA MICS reports, consult the CA MICS Standard
Reports Guide and the individual product guides.

The remainder of this section presents the following topics:

    1 - Database Complex Planning and Parameters
    2 - CA MICS Operational Planning and Parameters
    3 - CA MICS JCL Planning and Parameters
    4 - Database Space Modeling Facility
    5 - Dynamic Execution Options (EXECDEF)
    6 - Dynamic Allocation Parameter Overrides (//PARMOVRD)