Appendix A. Special CA MICS Processing › A.2 File Tailoring for the SPECIAL Database › A.2.1 SPECIAL Database File Tailoring Options (SELFILES)

A.2.1 SPECIAL Database File Tailoring Options (SELFILES)

The SPECIAL database is tailored by user specifications in
prefix.MICS.PARMS(SELFILES).  The purpose of this member is
to tell the SPECIAL database tailoring job (also called
SELFILES) which files are to be active, and in which
timespans, in the online SPECIAL database.

Each line in the SELFILES member resembles the FILE
statement in prefix.MICS.PARMS(DBMODEL) for the associated
file.  For example, the FILE statement for the ADMEXC file
looks like:

    FILE BAS  ADMEXC 00 08 00 06 00 00 000 000 aud
    ---- ---  ------ -- -- -- -- -- -- ------- ---
      |   |      |    |  |  |  |  |  |    |     |
      | +-+      |    |  |  |  |  |  |    |     |
      | | +------+    |  |  |  |  |  |    |     |
      | | | +---------+  |  |  |  |  |    |     |
      | | | | +----------+  |  |  |  |    |     |
      | | | | | +-----------+  |  |  |    |     |
      | | | | | | +------------+  |  |    |     |
      | | | | | | | +-------------+  |    |     |
      | | | | | | | | +--------------+    |     |
      | | | | | | | | | +-----------------+     |
      | | | | | | | | | | +---------------------+
      | | | | | | | | | | |
      | | | | | | | | | | +-audit archive specification
      | | | | | | | | | |   (See 2.3.4.1.2)
      | | | | | | | | | +---history archive retention limits
      | | | | | | | | |     (not used in SPECIAL database)
      | | | | | | | | +-----cycles retained in TABLES
      | | | | | | | +-------cycles retained in YEARS
      | | | | | | +---------cycles retained in MONTHS
      | | | | | +-----------cycles retained in WEEKS
      | | | | +-------------cycles retained in DAYS
      | | | +---------------cycles retained in DETAIL
      | | +-----------------complete file name
      | +-------------------component ID
      +---------------------FILE statement keyword

Normal (complex-wide) activation of a file in a timespan is
accomplished by the specification of the timespan indicator
in the FILE statement of the component's CA MICS Component
Generator (MCG) definition statements.  See the CA MICS
System Modification Guide section on the CA MICS Component
Generator (MCG) for more information on this process.

Normal definition of the number of cycles of a file to be
retained in a timespan in which the file is active is
accomplished by the specification of the timespan retention
indicators in the FILE statement of the database unit's
DBMODEL definition statements.  See the section in this
document on database space modeling for more information on
this process.

The file activation and aging limits specified in the MCG
statements and in the DBMODEL will be overwritten by using
the SELFILES process.  Changing the cycle retention limits of
a file in a timespan from zero to a non-zero number will
activate the file in that timespan.  Changing it from
non-zero to zero will deactivate the file in the timespan.
Changing all retention limits to zero will deactivate the
entire file.  Changing the retention limit from one non-zero
value to another will alter the aging macros for the file.

Components are specified to the SPECIAL database in
prefix.MICS.PARMS(JCLDEF).  The components generated here are
eligible for SPECIAL database processing.  However, those
components may or may not be active (see the SPECIAL database
EXECDEF specification in the next section).

If the component is active, it will be processed.  If it is
not active, it will not be processed.  All components that
are eligible will have certain parts of their executable code
changed to reflect the new specification, but only for the
SPECIAL database being generated.