Example reconfiguration dialog for I/O error

The following example illustrates a typical console sequence when JES2 initiates a checkpoint reconfiguration dialog with operator verification enabled. The system configuration is based on the following checkpoint definition:

CKPTDEF CKPT1=(DSN=SYS1.JES2CKPT1,VOL=CHECK1,INUSE=YES),
        CKPT2=(DSN=SYS1.JES2CKPT2,VOL=CHECK2,INUSE=YES),
        NEWCKPT1=(DSN=SYS1.REPLACE1,VOL=CHECK3),
        NEWCKPT2=(DSN=SYS1.REPLACE2,VOL=CHECK3),
        MODE=DUPLEX,OPVERIFY=YES

Assume an I/O error occurs on CKPT2 on member SY1

$HASP275 CKPT2 I/O ERROR - Knn
$HASP233 REASON FOR JES2 CHECKPOINT RECONFIGURATION IS CKPT2 I/O ERROR(S) ON 1 MEMBER(S)
$HASP285 JES2 CHECKPOINT RECONFIGURATION STARTED - DRIVEN BY MEMBER SY1
$HASP273 JES2 CKPT2 DATA SET WILL BE ASSIGNED TO ...
$HASP272 ENTER RESPONSE
Operator response: R nn,CONT
$HASP280 JES2 CKPTn DATA SET...
$HASP255 JES2 CHECKPOINT RECONFIGURATION COMPLETE
$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=(...).

If you alternatively specified OPVERIFY=NO on the CKPTDEF statement, message pair $HASP273 and $HASP272 is not presented to the operator. All messages issued in a JES2-initiated automated checkpoint reconfiguration are informational and none require response.

If an automatic checkpoint reconfiguration takes place while the operator is away from the console, on return, the only message displayed will be $HASP256. Therefore, you can automate a reconfiguration by automating the response to this message only. To do so, establish a pool of replacement checkpoint data sets from which an automated $T CKPTDEF,NEWCKPTn=(...) reply in response to $HASP256 can choose a replacement.