$HASP9162

Explanation

>>-PCES WAITING FOR SPOOL SPACE--------------------------------><

 JES2 issues this notice message in response
to a $JDJES or a $JDSTATUS monitor command. This message indicates
that there is at least one PCE waiting for SPOOL space. This might
be a normal condition that occurs as part of the SPOOL allocation
cycle on your system. However, if the condition persists in combination
with other symptoms, it might indicate a potential problem.

System action
 Display continues.

Operator response
 At least one PCE is waiting for SPOOL space.
If the command response indicates other problems (such as checkpoint
reconfiguration in progress) then a PCE waiting for SPOOL space is
a result of that situation. However, if no other problems are indicated
in the response and this condition persists in combination with other
symptoms, this message might indicate a problem situation.
 First, determine if the SPOOL volumes are full by issuing a $DSPOOL
command. The $HASP646 message indicates the percent of SPOOL in use.
If this is high, then freeing SPOOL space will address this condition.
If there is sufficient free space, determine what PCEs are waiting
for SPOOL space by issuing the $DPCE,DETAILS=WAIT command and looking
for PCEs with WAIT=TRACK. If the PCEs differ each time the command
is issued, then this is a performance problem caused by this member
not accessing the checkpoint data set frequently enough. If the same
PCE is appearing in the message and that PCE is not functioning properly,
there might be a problem allocating SPOOL space. Contact your system
programmer as appropriate.

System programmer response
 JES2 issues this message if at least
one PCE is waiting for SPOOL space at the time the operator issued
the $JDJES or $JDSTATUS command. Depending on the timing of the command
and the allocation of SPOOL space, this may be a normal condition.
This could also be a normal side effect of other problems that might
be indicated in the command response.
 If you suspect a performance
problem, then examine the settings HOLD= and DORMANCY= on the MASDEF
statement. Adjusting these settings can reduce the time PCEs wait
for SPOOL space but might cause delays elsewhere.
 Another source
of potential problems is the SPOOLDEF FENCE= settings and the AFFINITY=
setting on your SPOOL volumes. Use of these parameters can limit the
SPOOL space available to a PCE. This is especially true if FENCE=(ACTIVE=YES,VOLUMES=1)
and you have a large number of SPOOL volumes (greater than 64). If
this is the case, consider increasing the number of volumes within
the "fence".
 If you suspect a problem, obtain a dump of
the JES2 address space. If you determine symptoms other than this
message and are unable to determine the cause, contact the IBM® Support Center.

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