Previous Topic: 3.2 Load Distribution Libraries

Next Topic: 3.2.2 Ensure that CA Common Services is Operational

3.2.1 Define Catalog Indexes


Two data set name prefixes, a DASD prefix (sharedprefix) and
a tape prefix (tsharedpref), are defined in
sharedprefix.MICS.PARMS(JCLDEFC).  The sharedprefix is
required.  The tsharedpref is optional and only used if you
have licensed CA MICS Accounting and Chargeback, and if you
are going to maintain a complex level audit file.

The data set name prefixes serve several purposes:  to give
unique names to the CA MICS data sets shared by all database
units in the complex, and to provide unique and meaningful
qualification for identification and control of the CA MICS
shared data sets.

The sharedprefix and tsharedpref must be different from all
of the other prefixes and tapeprefixes in the database
complex.  However, the sharedprefix and the other prefixes
may have a common high-level index.

Unless standards at your site prevent it, this step should be
used to ensure that the index established for the
sharedprefix and tsharedpref point to a catalog other than
the master catalog.

In selecting a high-level index for CA MICS data sets, be
aware of the following:

1.  Most sites have data set naming standards for production
    data sets.  CA MICS should be considered as a production
    system, and the high-level index chosen accordingly.

2.  If a high-level index of a TSO userid is selected, ensure
    that your site does not delete data sets that remain
    unreferenced over long periods of time.  For example, the
    YEARS timespan database will not be referenced for output
    until the MONTHLY job is run.

If the highest level index of the sharedprefix is a TSO
userid or an index that already exists, then the required
catalog indexes and master catalog pointers are already built
and no further action is required in this step.

Special Considerations:

1. No action is required if the high-level index has been
   defined already in the master catalog.

2. In a multi-CPU environment, it is essential that the high
   level index be defined in a VSAM user catalog and not
   allowed to default to the master catalog.  Data sets that
   are cataloged in the master catalog of one system will not
   be available from any other system's master catalog unless
   the data sets are explicitly cataloged on that system.