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 MICS MONTHLY or standalone HISTM operational job.
micsrm140
Required roles: systems programmer, security administrator, database administrator
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, follow these steps:
  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.
    For more information about the FILE statement in DBMODEL, see Preparing the Modeling Input.
  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 or HISTM job JCL, or both. This JCL 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".
    For more information about the GENIN FILES statement, see Tailoring Archive Files.
  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) jobs.
    This generates the MONTHLY or HISTM job JCL, or both. This JCL contains DD statements for the new monthly history configuration.
    For example, assume that 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-+