Main Control-M/Restart capabilities

Control-M/Restart provides the following major capabilities:

• Restart

  Performing job restart is the main function of Control-M/Restart. When job restart is necessary, Control-M/Restart automates restart by identifying at which step to initiate a job restart and by performing necessary tasks (described later) to ensure that job restart is error-free.

  This capability is available both for restarts under Control-M and standalone restarts.

• Data set cleanup and Prevent-NCT2 processing

  Another important function of Control-M/Restart is data set cleanup, which is described in Data set cleanup prior to the original run.

  Before restarts and reruns, Control-M/Restart automatically performs data set cleanup. It does not have to be requested.

  Data set cleanup can also be performed by request prior to the original job run:

  • When the data set cleanup request is connected to the original job run request, it is termed Prevent-NCT2 processing.

    The term is derived from the error message generated following an attempt to catalog a data set that was already cataloged. The error message indicates a reason of NOT CATLGD for reason code 2. As part of data set cleanup, Control-M/Restart prevents these types of errors.

  • When the data set cleanup request is independent of, and not accompanied by, a job run request, no special term is applied and it is called data set cleanup.
• Maintaining Previous Runs in the History Jobs File

  Jobs that have already executed and are ready for removal from the Control-M Active Jobs file can be saved in the Control-M History Jobs file (instead of being deleted). Parameters in the Control-M job scheduling definition determine if and when a job is placed in the History Jobs file and how long the job is maintained there.

  This capability is available only for jobs submitted under Control-M.