Requested resources not available: Resources named in
the request, and required to honor it, are not currently available.
It is not known when the resources will be made available.
Bytes 2 and 3 following the sense code contain sense-code-specific
information.
- 0000
- No specific code applies.
VTAM® hint: This
error can be caused by a DR ADD for a duplicate address. Check your
DR statements to see if an address was duplicated.
- 0001
- BIND queuing not supported, retry: The SLU is not available and
the sender of the UNBIND does not support BIND queuing as requested
by the PLU.
- 0002
- Requested resource not available: For dynamic reconfiguration
MOVE, ADD, or ADDLINK operation, the requested local address is already
assigned to an active resource. For MOVE PU, this is the DLC address;
for MOVE LU, the LU local address.
- 0003
- The application transaction program specified in the request is
not available.
- 0004
- Session resources unavailable: The receiver of the RNAA cannot
satisfy the request for reserved session resources specified on the
assign LU characteristics (X'30') control vector.
VTAM hint: A possible cause of this error
is a mismatch between the values specified on the EAS and MAXSESS
operands on the BUILD definition statement.
- 0005
- Controller resource is not available.
- 0009
- The intersubnetwork Locate failed because the maximum number of
intersubnetwork hops was exceeded. The value of the maximum intersubnetwork
hop count field in the locate was reduced by a number greater than
one while being processed by a border node along the route.
- 6002
- The resource identified by the destination program name (DPN)
is not supported.
- 6003
- The resource identified by the primary resource name (PRN) is
not supported.
- 6031
- Transaction program not available, retry allowed: The FMH-5 attach
command specifies a transaction program that the receiver is
unable to start. Either the program is not authorized to run
or the resources to run it are not available at this time. The condition
is temporary. The sender is responsible for subsequent retry.
This sense data is sent only in FMH-7.