Route Setup procedure failure: An intermediate or destination
node was unable to successfully complete the processing of a high-performance
routing (HPR) Route Setup request or reply.
Bytes 2 and 3 following the sense code contain sense code
specific information. Settings allowed are:
- 0000
- No specific code applies.
- 0001
- The destination LU is not ready to accept sessions.
- 0002
- An unknown destination LU was specified in the request.
- 0003
- A TG specified in the RSCV could not be activated.
- 0004
- An unknown TG was specified in the RSCV.
- 0005
- A TG specified in the RSCV has failed.
- 0006
- A TG specified in the RSCV was not activated as an HPR TG.
- 0007
- An intermediate node had insufficient storage to activate a TG
specified in the RSCV.
- 0008
- The receiving node had insufficient storage to process the route
setup request.
- 0009
- The route setup request was received over a TG that was not activated
as an HPR TG.
- 000A
- A VR within a composite network node is inoperative.
- 000B
- The receiving node does not support HPR protocols.
- 000C
- The receiving node does not support the HPR transport option.
- 000D
- The route setup request or reply could not be forwarded over the
TG in the FID2 format because its size was greater than the TG maximum
BTU size.
- 000E
- The value of the current hop count field of the RSCV received
in a route setup request exceeded the value of the destination hop
index field in the request (for example, the route setup request appeared
to have passed the destination node).
- 000F
- The route setup request completed unsuccessfully. The route setup
reply was not received in the allotted time (as determined by the
IOPURGE start option).
- 0020
- The intended destination was not able to perform the RTP function
(for example, it does not support the RTP transport tower). When a
negative route setup reply with this sense code passes through an
RTP-capable intermediate node, the intermediate node attempts to become
the new destination and perform the RTP function.
VTAM® hint: This might be encountered due
to an error in the definition of an activate-on-demand switched link,
which was dialed as the result of the route setup request. If the
link was predefined as HPR capable, but the partner node does not
support HPR (or does not wish to support HPR protocols on the designated
link), the route setup will fail when the link fails to activate as
an HPR-capable link.
This should not lead to a failure to set
up the session, but might lead to the use of normal APPN intermediate
session routing instead of HPR.
- 0021
- An extended border node rejected a path switch attempt due to
locally defined restrictions that do not allow RTPs to pass through
that node. This sense code could be set during APPN Locate search
processing or route setup processing for an RTP connection that is
undergoing path switch. For APPN Locate search processing, this sense
code might not cause a search failure. Rather, this sense code causes
APPN Locate search processing to continue, thereby allowing discovery
of alternate paths to the target node, which support the path switching
RTP.