Restarting JES2 from an emergency checkpoint

If your checkpoint reconfiguration did not complete successfully, and you are unable to restart JES2 from your checkpoint, perform an all-member warm start using an emergency checkpoint data set. If in response to $HASP279 issued by several members, you have created several emergency checkpoints, attempt to restart JES2 with an available emergency checkpoint that you select in the following order:

Original driving member
Subsequent driving member (if a previous driving member failed)
Other available emergency checkpoint.

Follow this example reconfiguration dialog when warm starting JES2 at initialization. This example assumes you are capable of returning to the original checkpoint DASD specifications that follow:

CKPTDEF CKPT1=(DSN=SYS1.JES2CKPT1,VOL=CHECK1,INUSE=YES),
        CKPT2=(DSN=SYS1.JES2CKPT2,VOL=CHECK2,INUSE=YES),
        NEWCKPT1=(DSN=SYS1.JES2REP1,VOL=CHECK3),
        NEWCKPT2=(DSN=SYS1.JES2REP2,VOL=CHECK4),
        MODE=DUAL,OPVERIFY=YES

Perform an all-member warm start and enter a reconfiguration dialog as follows:

enter
```
S JES2,PARM='WARM,RECONFIG'
```
JES2 initialization processing continues:

JES2 initialization processing continues:
$HASP285 JES2 CHECKPOINT RECONFIGURATION STARTED - JES2 INITIALIZATION
$HASP289 CKPT1 AND/OR CKPT2 SPECIFICATIONS ARE REQUIRED... VALID RESPONSES ARE...
$HASP272 ENTER RESPONSE

Operator response:

R nn,CKPTDEF CKPT1=(DSN=SYS1.EMERGNCY.HASPCKPT,VOL=SPOOL1,INUSE=YES),
CKPT2=INUSE=NO

JES2 displays the original CKPTDEF statement with changes made in the previous step:

$HASP829 CKPTDEF CKPT1=(DSN=SYS1.EMERGNCY.HASPCKPT,VOL=SPOOL1,INUSE=YES),
$HASP829         CKPT2=(DSN=SYS1.JES2CKPT2,VOL=CHECK2,INUSE=NO),
$HASP829         NEWCKPT1=(DSN=SYS1.JES2REP1,VOL=CHECK3),
$HASP829         NEWCKPT2=(DSN=SYS1.JES2REP2,VOL=CHECK4),
$HASP829         MODE=DUAL,OPVERIFY=YES

$HASP289 CKPT1 AND/OR CKPT2 SPECIFICATIONS ARE REQUIRED... VALID RESPONSES ARE...
$HASP272 ENTER RESPONSE
Operator response: R nn,END

At this point, you are using the emergency checkpoint only. Continue reconfiguration processing as in the following examples to achieve the required permanent checkpoint configuration.

Enter

$T CKPTDEF,NEWCKPT1=(DSN=SYS1.JES2CKPT1,VOL=CHECK1),RECONFIG=YES

$HASP285 JES2 CHECKPOINT RECONFIGURATION STARTING
$HASP233 REASON FOR JES2 CHECKPOINT RECONFIGURATION IS OPERATOR REQUEST
$HASP285 JES2 CHECKPOINT RECONFIGURATION STARTED - DRIVEN BY MEMBER SY5
$HASP271 CHECKPOINT RECONFIGURATION OPTIONS...VALID RESPONSES ARE...
$HASP272 ENTER RESPONSE
Operator response: R nn,1
$HASP273 JES2 CKPT1 DATA SET WILL BE ASSIGNED TO NEWCKPT1 ...
$HASP272 ENTER RESPONSE
Operator response: R nn,CONT
$HASP256 FUTURE AUTOMATIC FORWARDING OF CKPT2 IS SUSPENDED UNTIL NEWCKPT2 IS RESPECIFIED. ISSUE $T CKPTDEF,NEWCKPT2=(...) TO RESPECIFY
In this example, $HASP256 is a highlighted message and remains on the screen until you issue $T CKPTDEF,NEWCKPT2=(...) in step 13.
$HASP255 JES2 CHECKPOINT RECONFIGURATION COMPLETE

Enter

$T CKPTDEF,NEWCKPT1=(DSN=SYS1.JES2REP1,VOL=CHECK3)

At this point, you have returned CKPT1 and NEWCKPT1 to their original definitions. The last task is to return CKPT2 and NEWCKPT2 to their original definitions as well.

Enter
```
$T CKPTDEF,RECONFIG=YES
```
$HASP285 JES2 CHECKPOINT RECONFIGURATION STARTING
$HASP233 REASON FOR JES2 CHECKPOINT RECONFIGURATION IS OPERATOR REQUEST
$HASP285 JES2 CHECKPOINT RECONFIGURATION STARTED - DRIVEN BY MEMBER SY3
$HASP271 CHECKPOINT RECONFIGURATION OPTIONS...VALID RESPONSES ARE...
$HASP272 ENTER RESPONSE
Operator response: R nn,8
$HASP273 JES2 CKPT2 DATA SET WILL BE ASSIGNED ...
$HASP272 ENTER RESPONSE
Operator response: R nn,CONT
$HASP255 JES2 CHECKPOINT RECONFIGURATION COMPLETE

At this point, you have resumed using CKPT2. NEWCKPT2 is left unchanged as originally specified. We have now returned all checkpoint specifications to their original definitions.