10. MODIFICATION › 10.1 Modification Checklists › 10.1.1 Activate DB2 Plan Activity Files (DB2DSP, DB2DDP)

10.1.1 Activate DB2 Plan Activity Files (DB2DSP, DB2DDP)

The DB2 Plan Activity Files, DB2DSP and DB2DDP, are optional
files created from a rename of the DB2DSU and DB2DDU files.
These files are distributed as active files.  The procedure
to activate the DB2DSP and DB2DDP files is, therefore, needed
only if the files have been set to inactive.

To activate these files, use the following checklist:

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

___ 2.  Modify sharedprefix.MICS.GENLIB(DB2GENIN).  If DDF
        reporting is required, modify the OPTION statement as
        follows:

        OPTION DDF

        Code the following FILE statement for the DB2DSP file
        if the file will be turned on in the DETAIL, DAYS,
        and MONTHS timespans:

        FILE DSP 00 2 Y E N Y N N N N DB2 PLAN Activity File

        Ensure the DDP FILE statement matches the DSP FILE
        statement if DDF is selected on the OPTION statement.

        Ensure all elements turned on in the DB2DSP and
        DB2DDP files are also available at the DETAIL
        timespan for DB2DSU and DB2DDP respectively.   The
        DB2DSU and DB2DDP timespan need NOT be active to
        comply with this requirement.

___ 3.  Submit the job in sharedprefix.MICS.CNTL(DB2CGEN).

___ 4.  Move CA MICS parameter library members that are
        dependent on the components installed in this
        database unit.

        Submit prefix.MICS.CNTL(COPYLIBU)

___ 5.  Review the definitions in prefix.MICS.PARMS(DBMODEL).
        Modify the cycle retention number to match the file
        status in each timespan.  For example, at least one
        cycle is retained for the DETAIL timespan for the
        files you activated.  See Section 7.3.3 of this guide
        for details on DBMODEL definitions.

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