7. PARAMETERS › 7.3 Unit Level Parameters › 7.3.1 DB2 Processing Options (DB2OPS) › 7.3.1.4 DETAIL Tape Processing Overview

7.3.1.4 DETAIL Tape Processing Overview

For certain high volume files, the CA MICS architecture
provides the ability to create optional DETAIL timespan data
sets.  These optional data sets are separate from the normal
CA MICS database and have the following characteristics:

o  They are created during the component step execution:
   during either an incremental update or the DAILY update
   run.  Each DETAIL tape file has a separate DD statement in
   the DAILY or incremental update job that specifies the
   data set name and other data set characteristics.

o  The data set name (DSN) for each DETAIL tape in a
   component step is:

   tapeprefix.tmics.DETAIL.iiifff(+1)

   where:

   - tapeprefix is the tape prefix value specified with the
     TAPEPREFIX statement in prefix.MICS.PARMS(JCLDEF)

   - tmics is either null when NOMICSLEVEL is specified, or
     MICS if MICSLEVEL is specified with the TAPEPREFIX
     statement in prefix.MICS.PARMS(JCLDEF)

   - iii is the three character CA MICS information
     area associated with the file

   - fff is the three character CA MICS file identifier

   Example: For the CA MICS DB2 Analyzer, if DETAIL tape
            processing were activated for the DB2DSU file,
            the following prefix.MICS.PARMS(JCLDEF)
            statement:

            TAPEPREFIX CPLXA.U1T NOMICSLEVEL

            yields the following DETAIL tape DSN:

            CPLXA.U1T.DETAIL.DB2DSU(+1)

o  There is no cycle aging associated with these data sets.
   Instead, each DETAIL tape data set created is an 01 cycle
   (for example, DB2DSU01), and multiple instances are
   managed using Generation Data Groups (GDGs).

o  The creation of DETAIL tape data sets is independent of
   any sharedprefix.MICS.GENLIB customization choices.  You
   can have one or more cycles of a file written to and
   managed in the unit DETAIL timespan database, and also
   use the DETAIL tape feature to create independent data
   sets for that same file.

o  The decision to create DETAIL tape data sets is made at
   the unit level.  You can choose to create DETAIL tape data
   sets for a component file in unit A, but not in unit B.

o  While the expectation is that these files will be written
   to tape, you can make JCL choices to target other media
   such as DASD.  Note that the SAS sequential tape engine
   will be used to write these files for both DASD and tape
   data sets.

o  Unique output exits are provided to permit manipulation
   and subsetting of the records written to the DETAIL tape
   data sets.  This manipulation and subsetting, however, has
   no impact on files written to the standard CA MICS
   database.

The activation of DETAIL tape data sets is accomplished by
specifying a TAPEfff statement in prefix.MICS.PARMS(cccOPS).

Customization of the JCL used to create each data set is
accomplished using a cascading hierarchy of parameters
beginning with choices made with the TAPEPARM statement in
prefix.PARMS(JCLDEF).

The following sections provide the information required to
activate DETAIL tape processing:

1 - Component Files Supporting DETAIL Tape Activation
2 - DETAIL Tape JCL Customization Overview
3 - The TAPEfff Statement
4 - The DETAILTAPEPARM Statement
5 - DETAILTAPESMSPARM and TAPEfffSMS Statements
6 - DETAIL Tape User Exits
7 - Activating DETAIL Tape Checklist
8 - Deactivating DETAIL Tape Checklist