$HASP263

VOLUME volser

Explanation

>>-WAITING FOR ACCESS TO--JES2 CHECKPOINT--VOLUME volser-------->

>--+-LOCK HELD BY MEMBER member_name-+-------------------------><
   +-LOCK HELD BY SYSTEM-------------+   
   '-SYSTEM MANAGED PROCESS ACTIVE---'   

 When the primary checkpoint data set resides
on DASD, JES2 has issued a RESERVE operation to the CKPT1 or CKPT2
data set on volume volser. The number of seconds
specified as the time interval on the LOCKOUT parameter on the MASDEF
initialization statement or on the $T MASDEF operator command has
elapsed, but the RESERVE operation has not completed. Another member
in the multi-access spool configuration may have ended while holding
the hardware RESERVE on the checkpoint data set.
 This message
is informational and displays why the lock can not be obtained. Either: The lock is held by another member of the MAS.
The lock is in transition and is currently held by MVS™. If
this state persists, there may be a XCF signalling problem or a system
may have failed.
The lock cannot be obtained because a system managed process is
active for the structure.

 In the message text:  volser
The volume identifier.
member_name
The JES2 member that holds the checkpoint lock.
SYSTEM
The MVS system temporarily holds the lock after it
has been relinquished by the last JES2 member to update the checkpoint.

System action
 JES2 issues this message every time the warning
interval specified on the LOCKOUT parameter expires until the read
operation completes.

Operator response
 Ensure that other systems in the MAS configuration
are operational. If the primary checkpoint is on DASD and the other
system is down, it is probably holding a RESERVE on the JES2 checkpoint
data set. If the failed system cannot be restarted, the RESERVE must
be cleared by pressing SYSTEM RESET on the failed system. After pressing
SYSTEM RESET, message $HASP264 might be issued. Use of the JES2 $E
CKPTLOCK command will not clear the reserve when this message is issued
with a VOLSER.
 If the primary checkpoint data set resides on
a coupling facility structure, wait until the software lock is freed.
If the list member is not operational, then the JES2 $E CKPTLOCK command
can be used to steal the lock. If LOCK HELD BY SYSTEM is displayed,
there may be a problem with XCF signalling or a system has failed
and not been partitioned out of the SYSPLEX. Check for outstanding
WTORs that have additional information. If a SYSTEM MANAGED PROCESS
ACTIVE indication has not cleared, you should determine the state
of the active process and possibly cancel it using the SETXCF command.
 Examine other members of the MAS for a $HASP9207 message. A member
that has issued the $HASP9207 message is the cause of this message.
Perform diagnostics on the member issuing the $HASP9207 message to
resolve the problem.

Module
 HASPCKDS
 Routing Code: 1,2,10
 Descriptor Code: 4