7. PARAMETERS › 7.3 Unit-Level Parameters › 7.3.4 IMS Processing Options (IMSOPS) › 7.3.4.11 DETAIL Tape Overview › 7.3.4.11.7 Activating DETAIL Tape Checklist

7.3.4.11.7 Activating DETAIL Tape Checklist

___ 1.  Add or modify the desired TAPEfff and TAPEfffSMS
        statements in prefix.MICS.PARMS(cccOPS), where fff is
        the three-character file identifier for the file to
        be written to tape.

___ 2.  Submit prefix.MICS.CNTL(cccPGEN).

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

        cccGDGGN DAILY

        If Incremental Update is active, add this:

        INCRccc

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

        Note:  If you want to use specific JCL and SMS
        parameter values for your DETAIL tape data sets, make
        sure you have coded the appropriate DETAILTAPEPARM
        and/or DETAILTAPESMSPARM statements in
        prefix.MICS.PARMS(JCLDEF) for unit level, or
        prefix.MICS.PARMS(cccOPS) for component level DETAIL
        tape JCL parameters.  Refer to the previous sections
        for a detailed discussion on JCL parameters available
        for DETAIL tape data sets.

___ 5.  Submit prefix.MICS.CNTL(cccGDGGN) to define the tape
        GDG.

        Note:  If you want to override the number of entries
        kept in a GDG with cataloged data sets for a TAPEfff
        file, you must delete and redefine the index with the
        new limit for GDG entries.  Follow the checklist in
        section 3.5.6.3 of the PIOM.

___ 6.  You have just activated DETAIL tape for one or more
        database files.  As mentioned in the DETAIL Tape
        Processing Overview section, the choice to create
        DETAIL tape files is independent of, and does not
        affect the creation of DETAIL files in the unit
        database.

        If you are currently creating one or more cycles of
        the files you just activated for DETAIL tape in your
        unit prefix.MICS.DETAIL timespan, your DAILY update
        job will continue to do so.

        Now that you are creating DETAIL tape cycles for the
        files, you may want to deactivate, or limit the
        number of DETAIL cycles written to the unit DETAIL
        timespan database.

        The CA MICS System Modification Guide contains
        instructions for changing the number of cycles of a
        file as well as instructions for deactivation of the
        DETAIL timespan of a file.

        If you deactivate the files in the DETAIL timespan,
        make sure you delete the existing cycles to free up
        space in the prefix.MICS.DETAIL database.  If you
        reduce the number of cycles, make sure you delete any
        existing cycles in prefix.MICS.DETAIL beyond the new
        cycle limit.

        The following JCL can be used to delete specific
        cycles of a file from the DETAIL timespan.  Make sure
        to replace 'x' with the unit identifier:

        a) Delete all cycles for file fff (01-nn)

        //DELETE  EXEC MICSDBx
        //SYSIN   DD *
         PROC DATASETS DDNAME=%DDNx(TS=DETAIL);
           DELETE cccfff01 cccfff02 ... cccfffnn ;
           RUN;

        b) Delete cycles 02, 03, and 04 for file fff:

        //DELETE  EXEC MICSDBx
        //SYSIN   DD *
         PROC DATASETS DDNAME=%DDNx(TS=DETAIL);
           DELETE cccfff02 cccfff03 cccfff04 ;
           RUN;