4. Operation › 4.3 Operations Reference › 4.3.3 Operational Processes, Jobs, and Steps › 4.3.3.2 Operational Jobs › 4.3.3.2.20 HISTW Operational Job

4.3.3.2.20 HISTW Operational Job

The HISTW job applies only where you have activated
stand-alone Archive Weekly History tape processing by
specifying,

     ARCHIVE HISTW YES JOB

in prefix.MICS.PARMS(JCLDEF).

The HISTW job performs the Archive Weekly History tape
processing.  This processing alternatively occurs within the
WEEKLY job's WEEK300 step.

The archive weekly history data is updated by creating a new
generation data group entry using the most recent WEEKS
timespan data (cycle 01) and the history-to-date contained in
the current (0) generation archive for each file maintained
in the WEEKS timespan archives.  Historical data and new
data are read in and any data that is older than the user-
specified archive retention age is deleted.

The WEEKS timespan files included in weekly archive history
processing and the archive retention are specified in
prefix.MICS.PARMS(DBMODEL) and sharedprefix.MICS.GENLIB
member cccGENIN, where ccc is the three-character component
identifier.  See the CA MICS Structure and Content Guide for
more information on the Archive Database.

The HISTW job may be scheduled automatically, or you may need
to schedule the job using your installation's production
batch job scheduling facilities.

o  If you specified

        ARCHIVE HISTW YES JOB

   in prefix.MICS.CNTL(JCLDEF), then Archive Weekly History
   processing is performed in the stand-alone HISTW job.

   -  If you specified the AUTOSUBMIT parameter on the
      ARCHIVE statement, then the WEEKLY job WEEK300 step
      automatically submits the HISTW job through the OS/390
      internal reader.

   -  If you specified NOAUTOSUBMIT (or took the default)
      then you must schedule the HISTW job externally, either
      manually or through your installation's production
      batch job scheduling facilities.

   NOTE:  The HISTW job must complete before the next
          scheduled WEEKLY job will be allowed to execute.

o  If you specified

        ARCHIVE HISTW YES

   in prefix.MICS.CNTL(JCLDEF), without the JOB parameter
   (i.e., you took the default or specified STEP), then
   Archive Weekly History processing is performed in the
   WEEK300 step of the WEEKLY job.  In this situation, you
   will NOT execute the HISTW job.

You will normally execute the HISTW job once each week, after
the WEEKLY job completes successfully.  To preserve archive
database integrity and avoid duplicate data, the HISTW job
will abort if you attempt to run it again before the next
WEEKLY job completes.  Likewise, the next WEEKLY job will not
be allowed to execute until the HISTW job completes
successfully.