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

Previous Topic: 4.3.3.2.20 HISTW Operational Job

Next Topic: 4.3.3.3 Job Steps
4.3.3.2.21 HISTM Operational Job

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

     ARCHIVE HISTM YES JOB

in prefix.MICS.PARMS(JCLDEF).

The HISTM job performs the Archive Monthly History tape
processing.  This processing alternatively occurs within the
MONTHLY job's MONTH300 step.

The archive monthly history data is updated by creating a new
generation data group entry using the most recent MONTHS
timespan data (cycle 01) and the history-to-date contained in
the current (0) generation archive for each file maintained
in the MONTHS 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 MONTHS timespan files included in monthly 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 HISTM 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 HISTM YES JOB

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

   -  If you specified the AUTOSUBMIT parameter on the
      ARCHIVE statement, then the MONTHLY job MONTH300 step
      automatically submits the HISTM job through the OS/390
      internal reader.

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

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

o  If you specified

        ARCHIVE HISTM YES

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

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