Insufficient resources: Receiver cannot act on the request
because of a temporary lack of resources.
Bytes 2 and 3 following the sense code contain sense-code-specific
information.
- 0000
- No specific code applies.
VTAM® Information: When VTAM receives this sense code for
a session initiation, it continues searching through the adjacent
SSCP table until the destination LU is found or routing is exhausted.
VTAM hint: A possible cause
of this error is that VTAM cannot
find a predefined application program definition or model application
program definition when processing an OPEN macro for an application
program requesting to open its ACB.
- 0001
- More PUs or LUs requested by RNAA than are present in the pool.
VTAM hint: If you
are activating a PU connected to an NCP, check the NCP LUDRPOOL definition
statement.
See NCP, SSP, and EP Resource Definition Reference for
more information.
- 0002
- More PUs or LUs are requested by RNAA than the attachment resource
will hold.
- 0003
- Resources are not currently available to support an XRF session.
- 0004
- The RNAA request indicates that the requested address must be
pre-ENA compatible, but no pre-ENA compatible address is available.
See z/OS Communications Server: SNA Resource Definition
Reference for information about MAXSUBA.
VTAM Information: When VTAM receives this sense code for
a session initiation, it continues searching through the adjacent
SSCP table until the destination LU is found or routing is exhausted.
- 0005
- The requested reserved resources for sessions are not available:
In RNAA, a reservation of session resources exceeded those available;
no address was assigned and no change was made to the current reservation
of the LU.
- 0006
- Insufficient resources are available for a boundary LU-LU session.
- 0007
- Insufficient resources are available for LU address allocation.
- 0008
- No buffer space: The session was deactivated because of a buffer
shortage when extending a nonextended positive RSP(BIND). Insufficient
resources exist to extend a BIND response.
- 0009
- No unreserved session connectors are available to add an LU.
- 000A
- A network node does not have adequate resources to honor a Register
request (the available directory capacity has already been reached).
- 000B
- A BFSESSINFO was received for an LU that is unknown to VTAM. VTAM attempted to create a representation for
the LU, but was unable to do so because of insufficient resources.
VTAM Information: When VTAM receives this sense code for
a session initiation, it continues searching through the adjacent
SSCP table until the destination LU is found or routing is exhausted.
- 000C
- Not enough buffer space exists to support a deadlock-free transmission
group. The receiver does not have enough buffers to allocate a BIND
receive buffer.
- 000D
- Insufficient buffers exist to activate a session.
- 000E
- The network names table is full.
VTAM hint: The NCP network names table is
full. Increase the NNT in the NAMTAB on the BUILD definition statement.
This sense code is set by the NCP.
See NCP, SSP, and EP Resource Definition Reference for
more information.
- 000F
- Insufficient buffer space exists to build a BFINIT.
- 0010
- The CP does not have adequate resources to process a GDS variable
request; it will deactivate its CP-CP sessions with the partner CP.
- 0011
- There is insufficient storage available to the SNA component to
satisfy the request at this time.
VTAM hint: A possible cause of this error
is that VTAM is trying to build
a dynamic application program from a model application program definition
and there is not enough storage to allow VTAM to build the dynamic application program.
- 0012
- No network address available to assign to a parallel session.
- 0014
- This session has failed because of storage depletion at an intermediate
node.
- 0015
- Insufficient resources are available to initiate a short hold
mode logical connection.
- 0016
- Unknown network identifier.
- 0017
- Insufficient buffer space exists to process a nonimmediate UNBIND.
- 0018
- All LFSIDs this node is allowed to assign on the TG are in use
at this time; the request is rejected.
- 0019
- Insufficient storage is available to conduct an XID exchange.
- 001A
- Insufficient storage is available to activate a TG.
- 001B
- Insufficient resources to activate a token-ring connection.
VTAM hint: A possible correction
for this error is to code the NCP parameter NEWDEFN, and the output
deck must be supplied to the VTAM configuration
found in SYS1.VTAMLST.
See Defining SNA
data sets in the z/OS Communications Server: New Function Summary for information about key data sets.
- 001C
- Insufficient storage exists to respond precisely to an error condition.
- 001D
- The PU Type 4 node does not have sufficient disk space to perform
the requested dump.
- 001E
- A session has failed because depletion of pooled buffer storage
has exceeded a critical threshold resulting from that session monopolizing
the usage.
- 0021
- A received XID3 cannot be fully processed because the receiver
has insufficient storage to keep the network-qualified name of the
control point of the sender.
- 0022
- No specific code applies.
VTAM hint: This
sense code can be displayed in a VTAM message
but is set by NCP. See NCP V7R8, SSP V4R8, EP R14 Messages and Codes for
a description of sense codes set by NCP.
- 0023
- No specific code applies.
VTAM hint: This
sense code can be displayed in a VTAM message
but is set by NCP. See NCP V7R8, SSP V4R8, EP R14 Messages and Codes for
a description of sense codes set by NCP.
- 0024
- No specific code applies.
VTAM hint: This
sense code can be displayed in a VTAM message
but is set by NCP. See NCP V7R8, SSP V4R8, EP R14 Messages and Codes for
a description of sense codes set by NCP.
- 0025
- Insufficient storage to keep the network-qualified name of the
connection network virtual node control point.