Procedure not valid for resource: The named RU is not
supported in the receiver for this type of resource. For example,
(1) SETCV specifies boundary function support for a Type 1 node, but
the capability is not supported by the receiving node or (2) the NCP
PU receiving an EXECTEST or TESTMODE is not the primary NCP PU for
the target link.
Bytes 2 and 3 following the sense code contain sense-code-specific
information.
- 0000
- No specific code applies.
- 0001
- Surrogate session setup failed.
- 0002
- Link cannot be used because it supports only HPR routing and the
session requires non-HPR routing.
VTAM® hint: A possible cause of this error
is that a session request was received from an adjacent VTAM subarea node by a VTAM APPN node that supports only HPR routing,
such as a VTAM node that communicates
in native mode across an asynchronous transfer mode (ATM) network.
- 0003
- Link not valid: The link to which the PU is to be added is not
an SNA link. Only SNA links are supported.
- 0004
- Link not valid: A request that is allowed only for a nonswitched
link was received for a link that is defined to the receiver as switched.
- 0005
- Resource was not dynamically added: This request works only with
resources that were added through dynamic reconfiguration.
- 0007
- Resource not found: A DELETE or FIND could not be satisfied
because the specified entry does not exist in the receiving directory.
VTAM hint:
- VTAM cannot find a model
definition to build a dynamic application program when the dynamic
application program requests to open its ACB.
- VTAM cannot find a dynamic
application program when the dynamic application program requests
to close its ACB.
- 0008
- The directory entry cannot be deleted. The network node received
a DELETE with a delete entry condition indicating that the entry can
be deleted only if it is a leaf. The entry is not a leaf; therefore,
the DELETE is rejected.
- 0009
- RNAA(Move) received a resource that was added through dynamic
reconfiguration. Such a resource may not be moved through RNAA(Move).
- 000A
- Procedure invalid for resource: A PN supporting independent LUs
has dialed into a boundary function that does not support sessions
with independent LUs. The SSCP cannot activate the independent LUs.
- 000B
- The REGISTER request specifies that a unique directory entry is
required (for example, the REGISTER is for an LU), but there is a
duplicate in the directory data base.
- 0010
- A SETCV with control vector X'43' has been received for
a nonswitched resource.
- 0011
- A dynamically added or switched resource has not yet been activated.
- 0012
- A request was received that is allowed only for a primary link
station. The request must utilize the service link and that link
is defined as secondary.
- 0013
- A CONNOUT request was received that contained an invalid X.21
call type.
- 0014
- A CONNOUT or CONTACT was received specifying that the receiver
is to designate itself as an APPN end node in XID3s that it sends
to an attached APPN or LEN.
- 0015
- This sense data value is generated whenever an APPN session route
must be calculated in two pieces (using two separate RSCVs) and it
is determined that the two RSCVs identify a common node; that is,
the session route passes through a given node twice.
- 0016
- This sense data value is generated whenever an RSCV is precalculated
because the OLU or DLU was thought to be in a subarea network and
it is determined (based on the RSCV) that the location of the DLU
is incorrect; that is, the RSCV indicates that the DLU is in the
APPN network, but the DLU is really in a subarea network, or vice
versa.
- 0017
- A session initiation request was received for a multinode persistent
enabled application program with a precalculated RSCV, but no HPR
connection can be set up using the precalculated route.
VTAM Information: The Locate
is resubmitted and the RSCV recalculated using a set of tail vectors
that VTAM supplies on the Locate
reply.
VTAM hint: The
error occurred because a VTAM V4R2
or VTAM V4R1 node calculated
the RSCV.