Restarting a Job

A job can be restarted in two ways:

  • After a halt/load

    The system automatically attempts to restart any job that was active at the time of a halt/load. If a checkpoint has been invoked during the execution of the interrupted task, then the operator is given a message requiring a response to determine whether the job should be restarted. The operator can respond with the system command OK (to restart at the last checkpoint), DS (to prevent a restart), or QT (to prevent a restart but save the files for later restart if the job was a checkpoint with PURGE).

  • By a Work Flow Language (WFL) RERUN statement

    A WFL job can be restarted programmatically by use of the WFL RERUN statement.

The following conditions can inhibit a successful restart:

  • An invalid usercode

  • Recompilation of the program since the checkpoint

  • Change of the operating system, since the checkpoint

    The restart fails if the creation time stamp of the operating system that created the checkpoint file does not match the creation time stamp of the current operating system.

  • Intrinsics after the checkpoint that are different from the intrinsics before the checkpoint

The messages in the following list can appear as the result of an attempt to restart:

  • RESTART PENDING (RSVP)

  • MISSING CHECKPOINT FILE

  • IO ERROR DURING RESTART

  • USERCODE NO LONGER VALID

  • OPERATOR DSED RESTART

  • OPERATOR QTED RESTART

  • MISSING CODE FILE

  • NOT ABLE TO RESTART

  • INVALID JOB FILE

  • RESTART AS CP/nnnn

  • MISSING JOB FILE

  • FILE POSITIONING ERROR

  • WRONG JOB FILE

  • WRONG CODE FILE

  • BAD CHECKPOINT FILE

  • BAD STACK NUMBER

  • WRONG MCP

The following can inhibit a successful checkpoint/restart:

  • Direct I/O (direct arrays or files)

  • Datacomm I/O (open datacomm files)

  • Open Enterprise Database Server sets

  • ODT files

  • Output directly to a printer (backup files are acceptable)

  • Checkpoints taken inside sort input or output procedures. The sort intrinsic provides its own restart capability; for more information, see SORT Statement.

  • Checkpoints taken in a compile-and-go program

If a job that produces printer backup files is restarted, the backup files can already have been printed and removed, and on restart, the job requests the missing backup files. In this situation, when the backup files are requested, the operator must respond with the system command OF (Optional File). A new backup file is created. Output preceding the checkpoint is not re-created.

The messages in the following table can appear as the result of a checkpoint/restart. Error conditions can be handled in a program by checking for them by completion code number and instructing the program to handle the result.

Checkpoint Message

Completion Code

CHECKPOINT#nn/yy TAKEN

0

INVALID AREA IN STACK

1

SYSTEM ERROR

2

BAD IPC ENVIRONMENT

3

NO USER DISK FOR CP FILE

4

IO ERROR DURING CHECKPOINT

5

# ROWS IN CP FILE > 1024

6

DIRECT FILE NOT ALLOWED

7

TOO MANY TEMPORARY DISK FILES

8

ILLEGAL FILEKIND

9

ILLEGAL FILE ORGANIZATION

11

INSUFFICIENT MEMORY TO CHECKPOINT

12

OPEN REVERSED TAPE FILE NOT ALLOWED

13

ICM AREA IN STACK

14

DMS AREA IN STACK

15

DIRECT ARRAY IN STACK

16

SECURITY ERROR SAVING TEMPORARY DISK FILE

17

SUBSPACE IN STACK

18

STACKMARK

19

SORT AREA IN STACK

20

IN USE ROUTINE NOT ALLOWED

21

ILLEGAL CONSTRUCT

22

BDBASE ILLEGAL

23

ILLEGAL FILE STRUCTURE

24

MULTI-REEL UNLABELED TAPE NOT ALLOWED

25

SURROGATE TASK NOT ALLOWED

26

NON-EVENT PO IN STACK

27

PROGRAM USES LIBRARIES

28

JOB STACK NOT VISIBLE

29

ROW SIZE TOO SMALL FOR CP FILE

30

VISIBILITY ATTRIBUTE SHOULD BE USED

31

OPERATOR CHECKPOINT REQUEST CANCELLED

32

CHECKPOINT REQUEST DENIED

33

BR REQUEST REJECTED

34

OPEN BACKUP FILE WITH PRINTDISPOSITION = EOT NOT ALLOWED

36

OPEN BACKUP FILE WITH PRINTDISPOSITION = CLOSE NOT ALLOWED

37

OPEN BACKUP FILE WITH PRINTDISPOSITION = DIRECT NOT ALLOWED

38

ERROR OCCURRED DURING CHECKPOINT IN FILE

39

ATTEMPT TO EXCEED TEMPORARY FILE LIMIT ON CP FILE

40

ATTEMPT TO EXCEED FAMILY LIMIT ON CP FILE

41

FAMILY INTEGRAL LIMIT EXCEEDED ON CP FILE

42

INVALID ENVIRONMENT IN STACK

43

DISK TYPE MUST BE DISK OR PACK

44

CHECKPOINT TYPE MUST BE ZERO OR ONE

45

SHARED BUFFERS NOT ALLOWED

46

STACK CONTAINS STRUCTURE TYPE VARIABLES

47

LIBRARY IS LINKED TO A CONNECTION LIBRARY ENVIRONMENT

48

PROGRAM USES CONNECTION LIBRARIES

49

PROGRAM USES SIGNALS

50

PROGRAM USES FILE DESCRIPTORS

51

FIFO NOT ALLOWED

52

POSIX SPECIAL FILES NOT ALLOWED

53

CHECKPOINT ABORTED: PRINTDISPOSITION OF OPEN BACKUP FILE MUST BE EOJ OR DONTPRINT

54

CHECKPOINT ABORTED: PRINTER FILES MUST BE BACKUP

55
Prev  Up  Next
Disposition Option  Home  Locking