$HASP276

reason text

Explanation

>>-JES2 CANNOT USE THE REQUESTED CHECKPOINT DATA---------------->

>--SET(S) DURING A {COLD START}--{WARM START WITH -RECONFIG SPECIFIED}-->

>--BECAUSE--reason text----------------------------------------><

  CURRENT CHECKPOINT VALUES: 

{CKPT1=(DSNAME=dsname,VOLSER=volser,

INUSE=xxx),}

{CKPT1=(STRNAME=strname,

INUSE=xxx),}

{CKPT2=(DSNAME=dsname,VOLSER=volser,

INUSE=xxx)}

{CKPT2=(STRNAME=strname,INUSE=xxx)}

VALID RESPONSES ARE:

CKPT1=... - UPDATE CURRENT

            CHECKPOINT

CKPT2=... - SPECIFICATION WITH THE

            VALUES JES2 SHOULD USE

‘CONT’    - ATTEMPT INITIALIZATION

           WITH THE VALUES LISTED

‘TERM’    - TERMINATE JES2

            INITIALIZATION ON THIS

           MEMBER

 JES2 initialization processing is
unable to access the displayed checkpoint data set(s).  The reason
for the failure is detailed in a preceding message and summarized
in the reason text in this message.  JES2 cannot
continue until either the problem displayed has been resolved or you
supply a usable checkpoint data set specification.
 In the message
text:  reason text
The reason initialization cannot continue
dsname
The name of the data set.
volser
The volume identifier.
strname
The name of the coupling facility structure.
xxx
Either YES or NO, indicating whether the data set is currently
in use.

 reason text is one of the
following. See the previous message for more information on the reason
for entering the dialog. BOTH CKPT1 AND CKPT2 ARE INUSE=NO  $HASP472 is issued
before entering dialog

CONNECT FOR CKPTn FAILED RC=xxxxxxxx RSN=xxxxxxxx  $HASP536 is issued before
entering dialog

OBTAIN FOR CKPTn FAILED RC=xxxxxxxx  $HASP414 is issued before entering dialog

VOLUME FOR CKPTn NOT MOUNTED  $HASP424
is issued before entering dialog

ALLOCATE FOR CKPTn FAILED RC=xxxxxxxx S99ERROR=xxxx S99INFO=xxxx  $HASP581 is issued before entering dialog

CKPTn FAILED ALLOCATION  There is
no related error message

DATA SET FOR CKPTn HAS NO EXTENTS  $HASP453 is issued before entering dialog

TRACK SIZE TOO SMALL FOR CKPTn DATA SET  $HASP295 is issued before entering dialog

CKPTn DATA SET TOO SMALL  $HASP296
is issued before entering dialog

CKPTn VOLUME NOT SHARED  $HASP449
is issued before entering dialog

OF ABEND PROCESSING CKPTn DATA SET  $HASP095 is issued before entering dialog

OF I/O ERROR READING CKPTn  $HASP290
or $HASP291 is issued before entering dialog

OF I/O ERROR LOCKING CKPTn  $HASP290
is issued before entering dialog

OF I/O ERROR RESERVING CKPTn  $HASP291
is issued before entering dialog

CKPTn FAILED VALIDATION PROCESSING  $HASP434 is issued before entering dialog

CKPTn STRUCTURE CONTAINS NO DATA  $HASP555 is issued before entering dialog

OPERATOR DID NOT ALLOW FORWARDING  A reply of ‘N’ was
given to $HASP457 before entering the dialog

OPERATOR REPLIED ‘N’ TO $HASP417 MESSAGE  $HASP416 and
HASP417 are issued before entering dialog

CKPT1 STRUCTURE IS  NOT LARGE ENOUGH  $HASP295 is issued
before entering dialog

System action
 JES2 issues message $HASP272 and waits for an
operator response.  If you reply ‘CKPT1’, ‘CKPT2’, or CKPTDEF to $HASP272,
JES2 reissues message $HASP276 with the updated checkpoint specification.

Operator response
 To determine why the reconfiguration was
entered, examine the previous message listed above. Either correct
the cause of the error or reply 'CONT' to the subsequent $HASP272
message. If the checkpoint information displayed is not correct, determine
where the checkpoint data set is to be placed (if this is a cold start)
or where the current checkpoint data resides (if processing a RECONFIG
request).  Respond to the $HASP272 message with the correct CKPTn
specification (for example, ‘CKPT1=(DSNAME=TEST.CKPT1, VOLSER=TSTCK1,
INUSE=YES)’). When message $HASP276 displays the correct checkpoint
specification, reply ‘CONT’ to the HASP272 message.
 If the
data set specification displayed is correct, then resolve the error
described in the message and reply ‘CONT’.  JES2 initialization attempts
to access the data sets again.
 If needed, in response to the
immediately following $HASP272 message, you can respond CKPTDEF with
operands to change the checkpoint data set names, the mode (DUPLEX
or DUAL), and the size of the change log.
 If you do not want
to continue JES2 initialization, reply ‘TERM’.

System programmer response
 If you are not familiar with the
initialization dialog process, see z/OS JES2 Initialization and Tuning Reference   for a detailed discussion.

Module
 HASPCKDS
 Routing Code: 1,2,10,42
 Descriptor Code: 2,7