Explanation
>>-JES2 RESOURCE SHORTAGE OF--resource-type – nnn--------------->
>--% UTILIZATION REACHED--optional text------------------------><
optional text can be one
of the following
A TOTAL OF aaaaa resource-type ARE
CURRENTLY DEFINED, OF WHICH:
xxxxx (xxx%) ARE IN USE
yyyyy (yyy%) ARE BEING WAITED FOR
zzz PROCESSORS REQUESTED resource-type
BUT DID NOT WAIT
THE LARGEST UNFULFILLED REQUEST WAS
FOR bbbbb resource-type
A MINIMUM OF ccccc resource-type ARE
REQUIRED TO SATISFY CURRENT DEMAND
JES2 has a shortage
of the resource type identified in the message text. The threshold
percentage of utilization of the resource is displayed. The percentage
is based on volumes available for allocation (active spool volumes).
The presence of the optional text indicates that the demand for
the resource is greater than the current number of resources that
are defined. Throughput might be increased by increasing the number
of the resources that are defined.
A resource shortage is defined
as one of the following:
- A percent utilization value for the resource was specified either
on the initialization statement or on a $T command, and JES2 is now
using more than that percentage of the resource.
- No percent utilization value was specified on the initialization
statement or on a $T command, and JES2 is now using more than 80%
of the resource. (80 percent is the default for the percent utilization
value.)
- The demand for the resource exceeded 100% within the last 32 seconds.
The message includes optional text indicating that JES2 was unable
to fulfill some request for the resource. Note that the message displays
the current utilization which might be a value lower than your
installation-defined threshold.
In the message text:
- resource-type
- The type of resource for which the shortage exists.
- nnn
- The current utilization percentage of the resource.
- aaaaa
- The total number of resource resource-type that
is currently defined.
- xxxxx
- The number of resource resource-type that is
currently in use.
- xxx
- The percentage of the total resource that is currently in use.
- yyyyy
- The number of resource resource-type for which
JES2 processors are currently waiting, because their requests could
not be satisfied. If this value is non-zero, the utilization percentage
(nnn might be less than the threshold percentage.
- yyy
- The amount of the resource being waited for, expressed as a percentage
of the currently defined total.
- zzz
- The number of processors that attempted to obtain resource resource-type, but had their requests denied because of
a shortage, and did not wait for the resource. If this value is non-zero,
the utilization percentage (nnn) might be less
than the threshold percentage.
- bbbbb
- The size of the largest unfulfilled request for resource-type.
- ccccc
- The estimated total number of resource-type that would be required
to fulfill all current outstanding requests.
The resource types and the corresponding initialization
statements are:
- resource-type
- Initialization
Statement
- BERT (block extension reuse table)
- BERTNUM on CKPTSPACE
- BSCB (bisynchronous buffers)
- BSCBUF on TPDEF
- BUFX (extended logical buffers)
- EXTBUF on BUFDEF
- CKVR (checkpoint versions)
- NUMBER on the CKPTDEF statement
- CMBs (console message buffers)
- BUFNUM on the CONDEF statement
- CMDs
- CMDNUM on the CONDEF statement
- ICES (SNA interface control elements)
- SESSIONS on the TPDEF statement
- LBUF (logical buffers)
- BELOWBUF on the BUFDEF statement
- JNUM (job numbers)
- RANGE on the JOBDEF statement
- JQEs (job queue elements)
- JOBNUM on the JOBDEF statement
- JOEs (job output elements)
- JOENUM on the OUTDEF statement
- NHBs (NJE header/trailer buffers)
- HDRBUF on the NJEDEF statement
- SMFB (system management facilities buffers)
- BUFNUM on the SMFDEF statement
- TGs (spool space/track groups)
- TGSPACE=(MAX=) on the SPOOLDEF statement
- TTAB (trace tables)
- TABLES on the TRACEDEF statement
- VTMB (VTAM®® buffers)
- SNABUF on TPDEF
For example, on the CONDEF initialization statement,
LIMIT=20 tells JES2 to generate 20 console message buffers and WARN=75
tells JES2 to issue this message when 75% of those buffers are being
used.
Note: If a CMB shortage is reached, remote messages may
be discarded to alleviate the shortage.
System action
Processing continues. If the utilization percentage
decreases, JES2 deletes this message from the console 32 seconds after
it is issued. If the utilization percentage still exceeds the threshold
value, JES2 reissues this message with the new utilization percentage
displayed. This process continues until the resource shortage is relieved
(either by less use of the resource or by an increase in the threshold).
If JES2 ends before the shortage is relieved, the message is deleted.
For the resources that are monitored on a MAS-wide basis (JNUM,
JQEs, JOEs and TGs), the message can be displayed to the console by
any member. The operator will not see redundant messages issued to
the console by every member if the MVS™ MSCOPE=(*ALL)
command was specified, but messages from all members are written to
hardcopy. If MSCOPE=(*ALL) was not specified in the MVS CONSOLxx
PARMLIB member, the operator might miss seeing this message.
For CMDS, the CMDNUM value on CONDEF can be changed through the $TCONDEF
command.
Operator response
Notify the system programmer. If
resource-type is either JQEs (job queue elements) or JOEs
(job output elements), any operator in the MAS can relieve the shortage
by doing one or more of the following:
- Entering the $OQ command to release held output.
- Purging unneeded output.
- Making unprocessed output eligible for selection by changing printer
characteristics.
System programmer response
If this message appears frequently
(or continues to be issued):
- Increase the percent utilization value with an operator command.
- Take steps to lower the usage of the resource.
- If the extended form of the message appears, increase the number
of the resource to at least ccccc, if possible.
Module
HASPMISC
Routing Code: 2,10
Descriptor Code: 2,7