$HASP9207

hh:mm:ss.xx

Explanation

>>-JES CHECKPOINT LOCK HELD--DURATION---hh:mm:ss.xx------------><

 JES2 issues this alert message in response
to a $JDJES or a $JDSTATUS monitor command or as a highlighted message.
Based on context, this message can indicate an alert or an incident
JES2 is tracking. This message is issued when the checkpoint data
set has been held for significantly longer than was specified on the
MASDEF HOLD= statement. The alert is issued in conjunction with other
alerts to inform the operator of the multi-system aspect of this problem.
If this member is holding the checkpoint lock, other members of the
JES2 MAS cannot process JES2 requests. If this message appears without
any other alerts, it might indicate a checkpoint problem. Issue the
$DPCE(CKPT),DETAILS command to display what the checkpoint PCE is
doing.
 In the message text: hh:mm:ss.xx
The length of time this member has held the checkpoint data set
lock.

System action
 If the condition persists, JES2 reissues this
message every 30 seconds.

Operator response
 Monitor alerts indicate potential reasons
why JES2 is not functioning properly. This message indicates that
a problem exists that might impact all member of your MAS. Unless
this message appears without any other monitor alerts, this message
addresses the impact of a problem rather than the problem itself.
If this condition persists, notify the system programmer.

System programmer response
 This message indicates the multi-member
nature of another problem that exists. However, if this message appears
without any other monitor alerts, it might indicate one of the following
problems: A potential problem with the JES2 checkpoint PCE. Issue a $DPCE(CKPT),DETAILS
command to determine where the checkpoint PCE is waiting. If the PCE
is not being dispatched, for example, wait time not advancing, this
is the cause of the problem. If the wait is in exit code, review your
exit code. If the wait is in IBM® –distributed
code, request a dump of the JES2 member issuing the message and contact
the IBM support center.
A problem with the checkpoint data set. Consider issuing a $TCKPTDEF,
RECONFIG=YES command to re-configure the checkpoint and use a different
checkpoint data set. For more information about this command, see z/OS JES2 Initialization and Tuning Guide and z/OS JES2 Commands.

Module
 HASJSPLR
 Routing Code: 1,2,10,42 or as a command response
 Descriptor Code: 2,7 or 5 when a command response