>>-REASON FOR JES2 CHECKPOINT--RECONFIGURATION IS--------------->

>--+-CKPTn I/O ERROR(S) ON m MEMBER(S)-----+-------------------><
   +-COUPLING FACILITY HAS BECOME VOLATILE-+   
   '-OPERATOR REQUEST----------------------'   

CKPTn I/O ERROR(S) ON m MEMBERS

JES2 initiated a checkpoint reconfiguration because of I/O error(s) on a coupling facility structure or data set on m members. $HASP275 (issued by one or more members) accompanies this message and provides the specific member and reason code. ($HASP275 might be displayed on a different console based on your installation's MSCOPE specification on the CONSOLxx parmlib member. See z/OS MVS Initialization and Tuning Guide for a description of the MSCOPE parameter. See z/OS JES2 Initialization and Tuning Guide for a complete explanation of checkpoint reconfiguration processing and examples of various checkpoint reconfiguration dialogs.

In the message text:

n

Either 1 or 2 indicating CKPT1 or CKPT2, respectively.

m

The number of members encountering I/O errors on CKPTn when JES2 first determined the reason for this checkpoint reconfiguration.

COUPLING FACILITY HAS BECOME VOLATILE

The coupling facility on which a checkpoint resides became volatile and JES2 entered a checkpoint reconfiguration as a result of processing based on your CKPTDEF VOLATILE= specification.

Note: A coupling facility is always considered volatile unless you have taken measures to protect against the loss of power to that coupling facility. See ES/9000 and ES/3090 PR/SM Planning Guide for a description of how to monitor the volatility of coupling facilities.

OPERATOR REQUEST

JES2 entered this reconfiguration following your request to begin a checkpoint reconfiguration with a $T CKPTDEF,RECONFIG=Yes command. (The blank between $T and CKPTDEF is optional.)