No path exists to the destination node: Route selection
services in the CP has determined from the topology database that
no path exists to the destination node.
Bytes 2 and 3 following the sense code contain sense code
specific information.
- 0000
- No specific code applies.
- 0001
- No route to the destination node exists for the specified class
of service.
VTAM® hint: Possible
causes of this error include, but are not limited to, the following
ones:
- If the IST1097I message group is displayed with the X'80020000'
sense code, followed by a display of the IST1110I message group with
this sense code, then the CP-CP session failed due to the loss of
the last CP-capable connection with the adjacent control point.
- If there are multiple entry points to the subarea network, there
must be a COS-acceptable route from the origin node to each interchange
node that represents a possible subarea entry point to be used to
reach the destination LU. A COS-acceptable route is a route that is
acceptable for the class of service specified on the session request.
Examine your network configuration to determine if a valid path
does exist. Use the DISPLAY TOPO command to verify that the topology
database currently shows the links in the path as operational. If
a valid APPN path exists, the characteristics of the nodes and links
in the operational paths might not meet the requirements of the specified
class of service. Do the following checks:
- Verify that the mode name specified on the request maps to the
intended class of service.
- Examine the LINEROWs and NODEROWs in the class of service definition
to determine what the allowable ranges are for the link and node characteristics.
- Use the DISPLAY TOPO command to view the characteristics of the
nodes and TGs in the likely paths. Look for the following problems:
- Nodes in the path are congested or have route resistance values
outside the limits set by the class of service.
- The COS definition required secure links, but no path exists consisting
exclusively of secure TGs.
- High capacity (speed) was required by the COS definition, but
no path exists in which all of the links are fast enough to meet the
specified minimum capacity.
- When one of the session partners resides on an end node (EN) that
has many links (TGs) to other nodes, this sense code might be set
by the network node (NN) responsible for computing the session path
if that NN did not receive a complete list of the EN's active links
(TG vectors). This can happen when some of the EN TG Vectors are
removed from the APPN Locate search because including all of them
would result in an APPN Locate search that exceeds the maximum APPN
Locate size supported by every node along the APPN Locate search path.
See Maximum APPN Locate Size Considerations in z/OS Communications Server: SNA Network Implementation
Guide for more information.
- 0002
- COS name received is not valid.
VTAM hint: The most common reasons for this
error are:
- The requested APPN class-of-service (COS) definition is not found
in the COS database at the node issuing this sense code.
- The requested mode name for the session does not map to an APPN
class of service known by this node.
Examine the mode definition to determine the APPN COS
name. Verify that this definition exists in a VTAMLST member at the
nodes which resolve the mode to an APPN class of service. Activate
the member to ensure that the definition is active. If APPN COS substitution
has been enabled by specifying the APPNCOS start option, verify that
the COS it specifies has been activated.
- 0003
- The topology database indicates that the destination node is not
available at this time; the node either has inconsistent data or is
quiescing.
VTAM hint: This
sense code might be issued when an attempt is made to change the node
role of the destination node of a TG that is being activated and the
node role change fails.
- 0004
- The topology database indicates that the endpoint resources are
depleted; the node is out of either half-session control blocks or
message buffers.
- 0005
- The length of the generated RSCV exceeds the maximum allowed.
VTAM hint: This
sense code indicates that the attempt to build the route selection
control vector failed because the number of hops between the origin
and destination nodes was too large.
Examine your network configuration
to determine how many hops would be expected in the best route for
the requested APPN class of service. If the number of hops within
a single APPN subnetwork is greater than six, you might need to provide
a more direct origin-to-destination path.
If you are using
connection network routing, reducing the length of the connection
network name reduces the length of the generated RSCV. The reduced
RSCV might be shorter than the maximum length allowed.
If you
are using hostname resolution for Enterprise Extender connection network
processing, reducing the length of the hostnames passed to name-to-address
resolution reduces the length of the generated RSCV. The reduced RSCV
might be shorter than the maximum length allowed.
- 0006
- No path using only HPR (high-performance routing) links exists
to the destination node.
- 0007
- BIND RSCV consists of only an interchange TG.
VTAM hint: An RSCV was calculated that consisted
of only interchange TGs. APPN Locates will not be used to set up the
session.
- 0008
- This node calculated an RSCV in which it does not own the boundary
function.
VTAM hint: This
node calculated an RSCV in which it doesn't own the boundary function.