10. MODIFICATION › 10.1 Modification Checklists › 10.1.3 Alter the Active Timespans for a File

10.1.3 Alter the Active Timespans for a File

For each DB2 Information Area file, there is a corresponding
FILE statement in sharedprefix.MICS.GENLIB(DB2GENIN).  The
FILE statement defines the file name, the file type, the file
status (active or inactive) in each timespan, and the file
status for archive (audit and history collection).

Note:  If incremental update is active, be sure to review
Section 10.1.2 of this guide before using the TAPEfff option
or USRXfff exits.

The USRXfff exits are coded in the #DB2EXIT member of the
sharedprefix.MICS.SOURCE library. They use the %FXIT
technique, which is described in section 10.2.3 of this
guide, as well as in Section 4.3.1.2 of the SMG.

Because the DB2DSP, DB2DSU, DB2DPP, DB2DDU, DB2DDP, DBPDBU,
and DBPDBP files contain large amounts of data at the DETAIL
timespan, the CA MICS Analyzer Option for DB2 provides the
TAPEDSP, TAPEDSU, TAPEDPP, TAPEDDU, TAPEDDP, TAPEDBU, and
TAPEDBP options, which allow you to write the DETAIL timespan
data to tape rather than DASD.  You do not need to code the
USRXfff exit to use the TAPEfff options.  For more
information about the TAPEfff options, refer to Section
7.3.1.4.3 in this guide.

   ****************** IMPORTANT ***************************
   *                                                      *
   *    If incremental update is active, be sure to       *
   *    review the important considerations in Section    *
   *    10.1.2 of this guide before using the TAPEfff     *
   *    option or USRXfff exits.                          *
   *                                                      *
   ****************** IMPORTANT ***************************

   +-----------------------------------------------+
   |To ...                   | use checklist...    |
   |-------------------------+---------------------|
   |activate the TAPEfff     |                     |
   | options...              | 3.1, which follows. |
   +-----------------------------------------------+

   *****************************************************
   *                                                   *
   *    Checklist 3.1 - Activate the TAPEfff Options   *
   *                                                   *
   *    If incremental update is active, be sure to    *
   *    review the considerations in Section 10.1.2.   *
   *                                                   *
   *****************************************************

___ 1.  Make a backup copy of all complex and unit level
        libraries in the complex.

___ 2.  Review the descriptions of the FILE statement
        provided in Section 4.2.4.2.1 of the SMG.

   ****************************************************
   *     Repeat the following steps for each database *
   *     unit containing the CA MICS Analyzer Option  *
   *     for DB2.                                     *
   ****************************************************

___ 3.  Edit prefix.MICS.PARMS(DB2OPS) and add the following
        statements anywhere in the member:

        TAPEDSP--to write the DETAIL.DB2DSP01 file to tape
        TAPEDSU--to write the DETAIL.DB2DSU01 file to tape
        TAPEDPP--to write the DETAIL.DB2DPP01 file to tape
        TAPEDDU--to write the DETAIL.DB2DDU01 file to tape
        TAPEDDP--to write the DETAIL.DB2DDP01 file to tape
        TAPEDBU--to write the DETAIL.DBPDBU01 file to tape
        TAPEDBP--to write the DETAIL.DBPDBP01 file to tape
        WORK--to set the number of work data set pairs to use
              when processing DETAIL transactions for each
              intermediate work file

___ 4.  Submit prefix.MICS.CNTL(DB2PGEN).

___ 5.  Edit prefix.MICS.PARMS(JCLGENU) so that it reads:

        DB2GDGGN DAILY

___ 6.  Submit prefix.MICS.CNTL(JCLGENU) to regenerate the
        JCL for DAILY and DB2GDGGN.

___ 7.  Submit prefix.MICS.CNTL(DB2GDGGN) to define the tape
        GDG.

        Note:  If your site already uses the TAPEfff options
        for other files, DB2GDGGN will complete with
        condition code 12.  Examine the output from the
        IDCAMS step to verify that a GDG entry has been
        successfully created for the selected file.