$HASP416

day, dd mmm yyyy

Explanation

>>-VERIFY CHECKPOINT DATA SET INFORMATION----------------------->

>--| VALUES FROM CKPTDEF |--| VALUES JES2 WILL USE |------------>

>--LAST WRITTEN--day, dd mmm yyyy -AT--hh:mm:ss--(--+-LOCAL TIME-+--)-><
                                                    '-GMT--------'      

VALUES FROM CKPTDEF

|--+-CKP1=--+-| DSNAME |--+---------+---------------------------|
   |        '-| STRNAME |-'         |   
   '-CKP2=--| DSNAME |--| STRNAME |-'   

VALUES JES2 WILL USE

|--CKP1=--+-| DSNAME |----------------------------+------------->
          '-(--STRNAME=--strname,--INUSE=--xxx--)-'   

>--CKP2=--+-(--DSNAME=--dsname,--VOLSER=--volser,--INUSE=--xxx--)-+--|
          '-| STRNAME |-------------------------------------------'   

DSNAME

|--(--DSNAME=--dsname,--VOLSER=--volser,--INUSE=--xxx--)--------|

STRNAME

|--(--STRNAME=--strname,--INUSE=--xxx--)------------------------|

 JES2 initialization is unsure of the checkpoint
data set specifications. If this message follows message $HASP454,
JES2 wants to confirm that the members have not migrated to a new
checkpoint data set.  This message is also issued if the CKPTDEF values
given during initialization are not consistent with information read
from the checkpoint data set. If this is true, JES2 is assuming the
data sets have been forwarded and wants confirmation of the data set
names.
 The message displays VALUES FROM CKPTDEF only if these
values are different from the values JES2 will use.
 The LAST
WRITTEN TIME in the message is the time associated with the checkpoint
data set JES2 will read the control blocks from. LOCAL TIME or GMT
displays depending on which was stored in the checkpoint.
 In
the message text:  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.
day
The day of the week (Monday, Tuesday, ....) that the checkpoint
data set was last written
dd mmm yyyy
The date of the last write to the checkpoint in day, month, year
format (for example, 28 MAR 2003)
hh:mm:ss
The time of the last write to the checkpoint in hour:minute:second
format (for example, 18:24:45)

System action
 JES2 issues message $HASP417.

Operator response
 Respond to message $HASP417.

System programmer response
 If the data set JES2 will use is
incorrect, update the CKPTDEF initialization statement with the correct
CKPTn values and then restart JES2.

Module
 HASPIRDA
 Routing Code: 1,2,10
 Descriptor Code: 2,7