7. PARAMETERS › 7.3 Unit Level Parameters

7.3 Unit Level Parameters

Unit level parameters control the processing of the Space
Analyzer within each database unit.  These parameters are
stored in the prefix.MICS.PARMS library associated with each
database unit you define.  The parameters are incorporated
into the CA MICS system by the parameter generation process.
Note that you must run the generation processes for these
options to take effect.

Recommendation: Separate Units for VCA and HSM

While HSM could be added to the same unit as VCA, we suggest
you strongly consider a separate unit for HSM.  This is
especially true if you manage a relatively large enterprise
with many data sets under the ownership of DFHSM.

A separate unit for HSM will allow for the following:

  - better testing and validation of this newer data source
    while leaving the VCA unit in production status
    uncluttered by the update activity of HSM.

  - concurrent or overlapping execution of the DAILY job for
    HSM (step DAY095) with the DAILY job for other CA MICS
    units including VCA (step DAY090).

  - a database split between the HSM (Migrate data) and the
    HSB (Backup data) information areas.

If you choose to add HSM to an existing database unit,
follow Section 3.8.2.2 in the PIOM.

   - When you arrive at Step 8 (PARMS definition) in the
     checklist for 3.8.2.2, it will point you back to
     this section for detailed instructions.

   - When you arrive at Step 10 (DBMODEL definition) in
     the checklist for 3.8.2.2, it will point you back
     to this section for details.

If you choose to add HSM to a new database unit, follow
Section 3.8.3.2 in the PIOM.

   - When you arrive at Step 11 (PARMS content) in the
     checklist for this section of the PIOM, follow
     guidelines discussed in the next few sections of
     this document.


Figure 7-5 identifies each of the system code generation
processes for the Space Analyzer, their PARMS member inputs,
and the output MACROs (a member may contain the definition of
more than one SAS MACRO) and FORMATs that they generate.  The
output libraries are at the database unit level (prefix)
unless noted otherwise.

+-----------+------------+--------------------+-------------+
|  System   | MICS.PARMS | USER.SOURCE        |  USER.LOAD  |
|   Code    |   Input    | Output Members and |   Output    |
| Generator |   Member   |  SAS MACRO Names   | SAS FORMATs |
+-----------+------------+--------------------+-------------+
|           |            |                    |             |
| VCAPGEN   |  VCAOPS    | $VCAMSTR   VCADUR  | (see VCAFMT)|
|           |            |                    |             |
| HSMPGEN   |  HSMOPS    | $HSMMSTR   HSMDUR  |     n/a     |
|           |            |                    |             |
|           |            |                    |             |
+-----------+------------+--------------------+-------------+

Figure 7-5. cccPGEN Code Generator Cross-Reference List

The sections that follow show you how to specify the
operational parameters that control how input data is
processed by the Space Analyzer. The names in parentheses are
the member names within the prefix.MICS.PARMS data set that
contain the parameters described in the section.

      1 - VCA Processing Options (VCAOPS)
      2 - HSM Processing Options (HSMOPS)
      3 - INPUTRDR, INPUTVCA, and INPUTHSM PARMS Members
      4 - Database Space Modeling (DBMODEL)