6. Database Tailoring and Retrofitting Techniques › 6.2 Tailoring the Database › 6.2.3 Tailoring Archive Files › 6.2.3.6 Delete File From Monthly History Archive Tape

6.2.3.6 Delete File From Monthly History Archive Tape

There are two ways to delete a file from the monthly history
archive tape, which is generated by the CA MICS MONTHLY or
standalone HISTM operational job.   The first only affects
one database unit, the second affects all database units in
which the component owning the file is installed.
 
To delete a file from the monthly history archive tape of a
particular unit, without affecting other units, do the
following:
 
  1.  Edit prefix.MICS.PARMS(DBMODEL).
 
      On the FILE statement for the file you want to delete,
      specify a cutoff limit of zero in the monthly history
      archive position.
 
      Refer to Section 2.3.4.1.2 in the PIOM for more
      information on the FILE statement in DBMODEL.
 
  2.  Submit the prefix.MICS.CNTL(CYCLEGEN) job.
 
      This job changes the component's executable code in the
      prefix.MICS.USER.SOURCE library and affects only the
      database unit in which the component is installed.
 
  3.  Edit prefix.MICS.PARMS(JCLGENU). Specify:
 
          MONTHLY HISTM
 
  4.  Submit the prefix.MICS.CNTL(JCLGENU) job.
 
      This generates the MONTHLY and/or HISTM job JCL that
      contains DD statements for the new monthly history
      configuration.
 
To delete a file from the monthly history archive tape,
affecting all database units in which the component is
installed, do the following:
 
  1.  Edit the FILE statement in
      sharedprefix.MICS.GENLIB(cccGENIN).  Change the "Y" in
      the file's monthly history archive position to "N".
 
      Refer to Section 6.2.3 for more information on the
      GENIN FILES statement.
 
  2.  Submit the sharedprefix.MICS.CNTL(cccCGEN) job to
      regenerate the component.
 
  3.  Submit the prefix.MICS.CNTL(CYCLEGEN) job for all
      database units in which the component is installed.
 
      This job changes the component's executable code in the
      prefix.MICS.USER.SOURCE libraries and affects only the
      database units in which the component is installed.
 
  4.  Edit prefix.MICS.PARMS(JCLGENU) for all database units
      in which the component is installed.  Specify:
 
          MONTHLY HISTM
 
  5.  Submit the prefix.MICS.CNTL(JCLGENU) job(s).
 
      This generates the MONTHLY and/or HISTM job JCL that
      contains DD statements for the new monthly history
      configuration.

For example, assume the NPANCP file example showed the file
appearing in the following archives:
 
 WEEKLY   WEEKLY    MONTHLY
 AUDIT    HISTORY   HISTORY
--------  --------  --------
  NO        YES       YES
 
Assume the desired configuration is:
 
 WEEKLY   WEEKLY    MONTHLY
 AUDIT    HISTORY   HISTORY
--------  --------  --------
  NO        YES       NO
 
The  initial definition of the NPANCP file statement in
sharedprefix.MICS.GENLIB(NPAGENIN) would have been:
 
    FILE NCP 00 1 Y Y Y Y N N Y Y NCP Activity File
                            | | |
      no WEEKLY audit  -----+ | |
      WEEKLY history   -------+ |
      MONTHLY history  ---------+
 
Change this statement to:
 
    FILE NCP 00 1 Y Y Y Y N N N Y NCP Activity File
                              |
  no MONTHLY history produced-+