Explanation
VTAM® displays
this message group to indicate that the TCP/IP stack could not find
a route to the specified destination address when activating an Enterprise
Extender connection. For an Enterprise Extender connection to activate
successfully:
- The local IP address must be a static VIPA owned by a TCP/IP
stack on this node
- The remote IP address must be either a static VIPA (if it is on
a z/OS® host) owned by the intended
destination node or a network address translation (NAT) address used
to ultimately access the remote node
- A route must be available between the two endpoints of the connection.
A complete description of the message group follows the example.
IST1892I NO ROUTE AVAILABLE TO DESTINATION
IST1680I type IP ADDRESS ip_address
[IST1909I REMOTE HOSTNAME value]
[IST1911I value]
IST1680I type IP ADDRESS ip_address
[IST1910I LOCAL HOSTNAME value]
[IST1911I value]
IST314I END
IST1680I - type is either LOCAL or REMOTE to identify
the IP address displayed.
- ip_address is either the remote IP address
or the local IP address. The first instance of IST1680I will display
the remote IP address, and the second instance of IST1680I will display
the local IP address.
IST1909I - value is the host name, owned by a target
remote node, that was used to acquire the remote IP address as part
of name-to-address resolution. If the host name is longer than 44
characters, then the first 44 characters are displayed as value and
the remaining characters are displayed in one or more IST1911I messages.
IST1910I - value is the host name used to acquire the
local static VIPA address used as part of the attempted route determination.
If the host name is longer than 45 characters, then the first 45
characters are displayed as value and the remaining
characters are displayed in one or more IST1911I messages.
IST1911I - value is the continuation of value on
IST1909I or IST1910I. IST1911I is repeated as many times as necessary
to display the entire character string.
System action
The Enterprise Extender dial out attempt failed.
Operator response
System programmer response
There is no route between these IP
addresses. The IP addresses used in the connection activation attempt
can be obtained in the following ways:
- For both predefined and connection network Enterprise Extender
connection, the local IP address (ip_address on
the IST1680I instance with type LOCAL) is
obtained from one of the following:
- The TCP/IP stack identified on the TCPNAME start option.
- The IPADDR start option, or the IPADDR operand on the XCA major
node GROUP definition statement associated with the Enterprise Extender
connection network or predefined Enterprise Extender connection used
for the failed route attempt, when IST1910I is not displayed.
- The name-to-address resolution of value on
IST1910I, which represents either the value supplied as the HOSTNAME
start option, or the value specified as the HOSTNAME operand on the
XCA major node GROUP definition statement associated with the Enterprise
Extender connection network or predefined Enterprise Extender connection
used for the failed route attempt.
- For predefined Enterprise Extender connections, the remote IP
address (ip_address on the IST1680I instance with type REMOTE)
is obtained from one of the following:
- The IPADDR operand on the PATH statement, when IST1909I is not
displayed.
- The name-to-address resolution of value on
IST1909I, which represents the value specified as the HOSTNAME operand
on the PATH definition statement.
- For connection network Enterprise Extender connections, the remote
IP address (ip_address on the IST1680I instance
with type REMOTE) is obtained from one of
the following:
- The IPv4 address provided by the remote Enterprise Extender node
in the APPN Route Selection Control Vector (RSCV) describing the
session route to use, when IST1909I is not displayed.
- The name-to-address resolution of value on
IST1909I, which represents the host name provided by the remote Enterprise
Extender node in the APPN Route Selection Control Vector (RSCV) describing
the session route to use.
Ensure that all of the following are true:
- The local or remote address has been specified correctly.
- The correct local or remote host name, or both, have been used
for name-to-address resolution.
- The routes exist in both directions between the attempted endpoints
of the Enterprise Extender connection.
- The NAT translation tables are accurate for translating the NAT
address to the ultimate target destination VIPA address (if on a z/OS host).
- The firewall along the route between the attempted endpoints of
the Enterprise Extender connection is configured to allow traffic
to flow from one endpoint to the other.
Routing code
Descriptor code