$HASP9169

Explanation

>>-MEMBER CANNOT GET CKPT LOCK (PROBABLY HELD BY ANOTHER MEMBER)-><

 JES2 issues this notice message in response
to a $JDJES or a $JDSTATUS monitor command. The message indicates
that JES2 is not able to access the JES2 checkpoint. This is normally
caused by another member holding the checkpoint and not releasing
it.

System action
 Most JES2 activities, such as running jobs and
printing output, require access to the JES2 checkpoint. If this condition
persists, JES2 functions will eventually stop.

Operator response
 Determine which JES2 member is holding the
checkpoint lock by looking for HASP9207 message on other members of
the MAS. (Issue a ROUTE *ALL, $JDSTATUS if all members use $ as the
JES2 command prefix.) If a member is holding the JES2 checkpoint,
perform problem determination on that member and restart JES2 if needed.

System programmer response
 If this condition occurs too frequently,
consider adjusting the MASDEF LOCKOUT parameter. The condition is
detected when the time specified on LOCKOUT has elapsed and the checkpoint
lock has not been obtained.

Module
 HASJCMDS 
 Routing Code: Routed as a command response 
 Descriptor
Code:5