10. MODIFICATION › 10.1 Checklists › 10.1.5 Activate Archive for a File

10.1.5 Activate Archive for a File

For each CIC information area file, there is a corresponding
FILE statement in sharedprefix.MICS.GENLIB(CICGENIN).  The
FILE statement defines the name, the type, the status of a
file in each timespan, and the file status for each of the
three possible archive files: the weekly audit, the weekly
history, and the monthly history.

The weekly audit archive is written each week during the
execution of the WEEKLY job or of the standalone Weekly
Processing - Database Archive Audit (AUDIT) job. By default,
up to 10 cycles of the DETAIL timespan for a given file are
copied from the CA MICS database to tape.  Since many files
are inactive in the DETAIL timespan or have far fewer than 10
active cycles in the DETAIL timespan, one can archive cycles
from the DAYS timespan instead of cycles from the DETAIL
timespan.

Weekly history archive files are written each week by the
WEEK300 step of the WEEKLY job or by the standalone Weekly
Processing - Database Archive (HISTW) job. When weekly
history archive is active for a particular CA MICS file, the
just completed WEEKS cycle of the CA MICS file is copied to
the output history tape for that file. At the same time, the
last generation of the weekly history archive for the file is
read so that its previous weekly cycles can be written to new
tape generation along with its just-completed WEEKS cycle.
The number of cycles of data that are written to the new tape
generation is limited by a predefined retention period.

Monthly history archive files are written each month by the
MONTH300 step of the MONTHLY job or by the standalone Monthly
Processing - Database Archive (HISTM) job. When monthly
history archive is active for a particular CA MICS file, the
just-completed MONTHS cycle of the CA MICS file is copied to
the output history tape for that file. At the same time, the
last generation of the monthly history archive for the file
is read so that its previous monthly cycles can be written to
new tape generation along with its just completed MONTHS
cycle. The number of cycles of data that are written to the
new tape generation is limited by a predefined retention
period.
The checklist below provides directions on how to activate
archiving for a file.

    ****************************************************
    *                                                  *
    *    CHECKLIST 5 - ACTIVATE ARCHIVE FOR A FILE     *
    *                                                  *
    ****************************************************


___ 1.  Save a copy of sharedprefix.MICS.GENLIB(CICGENIN) in
        sharedprefix.MICS.LOCALMOD.CNTL for recovery
        purposes.

___ 2   Decide which files are to be archived and for each of
        these files, decide which will have a weekly audit, a
        weekly history, or a monthly history archive. At the
        same time, decide whether the archiving will be
        performed during the WEEKLY and MONTHLY jobs or
        during the standalone AUDIT, HISTW, and HISTM jobs.
        For more information, see the PIOM.

___ 3.  Review the description of the FILE statement in the
        CA MICS System Modification Guide.

___ 4. In sharedprefix.MICS.GENLIB(CICGENIN), update the FILE
        statement for each file to be modified. For weekly
        archive audit, the file should be active in either
        the DETAIL or DAYS timespan. For weekly archive
        history, the file should be active in the WEEKS
        timespan.  For monthly archive history, the file
        should be active in the MONTHS timespan.

        At the same time, activate the archive files by
        specifying "Y" in the appropriate positions on the
        FILE statement for each file as described in the
        documentation reference in step 3 above.

___ 5.  Regenerate the CICS Analyzer by submitting the job in
        sharedprefix.MICS.CNTL(CICCGEN).
   ******************************************************
   *     Repeat the following steps for each database   *
   *     unit containing the CICS Analyzer.             *
   ******************************************************

___ 6.  Review the definitions in prefix.MICS.PARMS(DBMODEL).
        Modify the cycle retention number to match the file
        status in each timespan and the archive cutoff values
        indicating the number of cycles of data to be kept in
        the weekly and monthly archive history files. For
        details, see section 7.3.10 of this guide for details
        on DBMODEL definitions.

___ 7.  Submit the job in prefix.MICS.CNTL(CYCLEGEN).

___ 8.  Modify prefix.MICS.PARMS(JCLGENU) so that it contains
        a single line that reads:

        WEEKLY MONTHLY AUDIT HISTW HISTM

___ 9.  Submit the job in prefix.MICS.CNTL(JCLGENU).

___ 10. Submit the job in prefix.MICS.CNTL(GDGSGEN).