Steps that are not restartable

Cataloging, re-cataloging, and uncataloging operations cannot, by themselves, hinder the capability to restart, because it is possible to use EQQCLEAN. However, there are some cases where a step is not restartable and the logic applied by HCL Workload Automation for Z is the following:

• The step must be re-executable (see the Re-executing steps section)
• The step must not satisfy any of the following conditions:
  • The step follows the abended step.
  • The step includes a DDNAME that is listed in the parameter DDNOREST (in the RCLOPTS initialization statement).
  • The step includes a DDNAME that is listed in the parameter DDNEVER (in the RCLOPTS initialization statement). In this case the preceding steps are also not restartable.
  • The step is a cleanup step.
  • The step is flushed or not run, and the step is not simulated. The only exception is when the step is the first to be flushed in the JCL, all the following steps are flushed, and the job did not abend.
  • The data set is not available, and the disposition is different from NEW.
  • The data set is available, but all the following conditions exist:
    • The disposition type is OLD or SHR.
    • The normal disposition is different from UNCT.
    • The data set has the disposition NEW before this step (the data set is allocated by this JCL).
    • The data set has been cataloged at the end of the previous run and a CAT action is performed in one of the steps that follow.
  • The step refers to a data set with DISP=MOD, unless the step never ran in the previous job runs (flushed or NORUN).
  • Restarting the job from this step entails the running of a step that cannot be rerun.