Restarting Checkpointed Tasks Automatically

If a WFL job was executing a checkpointed task when a halt/load occurred, the job does not immediately restart after the halt/load. Instead, an independent runner called JOBRESTART appears in the W (Waiting Entries) system command display. The following is an example of the entry:

---Mix-Pri---Elapsed------------ 2 WAITING ENTRIES -----------------
  7082  50       :55  JOB  JOBRESTART
       RESTART PENDING 7119 DAILY/RUNNIT

In the preceding example, DAILY/RUNNIT is the job that is pending restart, and its mix number is 7119. The checkpointed task does not appear in the display. JOBRESTART is a job that was initiated by the system software to do the restarting, and its mix number is 7082. The following are the possible operator responses to this example and the effects of the responses:

  • 7082 OK

    This command restarts the job and restarts the task at the last checkpoint.

  • 7082 DS

    This command discontinues the job and the task. Any checkpoint files are saved, regardless of whether the disposition was LOCK or PURGE. The checkpoint number of PURGE files is left as 0 (zero).

  • 7082 QT

    In this context, QT has the same effect as DS.

Prev  Up  Next
Restarting a Checkpointed Task  Home  Initiating a Restart Explicitly