You restart a running WFL job with the RESTART (Restart Jobs) system command. This command first discontinues the current job and its tasks, and then restarts the new job as though a halt/load had occurred. For example, the job resumes execution from the last point at which no offspring were in use. For further information about the restart point, as well as about job and task side effects that you should plan for, refer to Designing WFL Jobs for Automatic Restarts earlier in this section.

If the DSED program dump option is set for any task of the job, the RESTART command causes the task to generate a program dump.

You can use the RESTART command to achieve some of the effects of a halt/load without interrupting the system. For example, if you need to perform maintenance on a disk unit, you must terminate any jobs that have files open on that disk unit. You can set the mix limit for the relevant job queue to zero, and then apply the RESTART command to such a job (rather than using the DS command). You can then hold the restarted job in the job queue until pack maintenance is completed. When you increase the mix limit, the job restarts from the last point where it had no tasks active.

You can also use the RESTART command to test ON RESTART statements in WFL jobs without having to halt/load the machine.

If the WFL job had no checkpointed task in progress at the time of the RESTART command, then the system automatically submits the job to a job queue. The job resumes execution whenever it is selected from that job queue.

If the WFL job was executing a checkpointed task at the time the RESTART command was entered, the job does not restart immediately after the command. Instead, the independent runner JOBRESTART appears in the W (Waiting Mix Entries) system command display. For information on how to respond to this waiting entry, refer to Restarting Checkpointed Tasks Automatically later in this section.