Skip to content
CA MICS Resource Management - 14.2
Documentation powered by DocOps

HISTM Operational Job

Last update April 15, 2016

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



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 generation data group entry using the most recent MONTHS timespan data (cycle 01) and the history-to-date that is contained in the current (0) generation archive for each file that is 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. For more information about the Archive Database, Database Structure and Administrative Information Area Files.

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

If you specified


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 z/OS internal reader.
  • If you specified NOAUTOSUBMIT (or took the default), then 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 is allowed to execute.

If you specified


in prefix.MICS.CNTL(JCLDEF), without the JOB parameter (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 do not execute the HISTM job.

You will typically 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.

Was this helpful?

Please log in to post comments.