IST535I ROUTE DISPLAY requestid FROM SA subarea1 TO SA subarea2
IST808I ORIGIN PU = originpu DEST PU = destpu NETID = netid
IST536I VR TP STATUS ER ADJSUB TGN STATUS CUR MIN MAX
IST537I [vr][tp] [vrstatus] [er] [adjsa] [tgn] [erstatus] [cur] [min] [max]
⋮
IST314I ENDThese messages contain virtual route and explicit route status for routes to the destination subarea subarea2. If the explicit route test option (TEST=YES) was requested, the results of actual tests of the applicable explicit routes will appear in subsequent messages.
If the destination subarea (DESTSA) has not been defined in the PATH definition statement, destpu will appear as ***NA*** (not available).
If the ORIGIN operand was specified on the DISPLAY ROUTE command with a name other than ISTPUS or the name specified on the HOSTPU start option in this host, the cur, min, and max window sizes reflecting the origin subarea VR information are not available and will not be displayed.
If the COSNAME operand was specified in the DISPLAY ROUTE command, message IST537I will appear in the same order as in the COS table entry. If a virtual route display or an explicit route display was requested, these messages will appear in numeric order by virtual route number (vr).
If an explicit route display was requested in the DISPLAY ROUTE command and there are no virtual routes defined to use a given explicit route, all the virtual route information (vr, tp, and vrstatus) for that explicit route will be blank. If a virtual route display or a COS display was requested in the DISPLAY ROUTE command and a given virtual route has not been defined to VTAM, all the explicit route information (er, adjsa, and erstatus) for that virtual route will be blank. adjsa will be blank for any explicit route with a status of UNDEF.
The virtual route has been defined to VTAM in a path definition set. It has been successfully activated. It is in use by one or more sessions.
The virtual route has been defined to VTAM in a path definition set and it has been successfully activated. It is in use by one or more sessions, but congestion has been detected along the route.
The virtual route has been defined to VTAM in a path definition set and is in the process of being activated by this node.
The virtual route has been defined to VTAM in a path definition set and has recently been active, but is now in the process of being deactivated by this node. Unless VTAM is halting, the VR will be automatically reactivated when it is again needed for a session.
The virtual route has been defined to VTAM in a path definition set, but is not currently active or is pending active. It will be automatically activated when it is needed for a session.
The virtual route has not been defined to VTAM in a path definition set.
The explicit route has been defined to VTAM in a path definition set, is physically available to the network, and has been activated by the node at the other end of the route. A route test (TEST=YES option) should succeed, because physical connectivity exists along the entire route in this state.
The explicit route has been defined to VTAM in a path definition deck, is physically available to the network, has been activated by the node at the other end of the route, and is in the process of being activated by this node. A route test (TEST=YES option) should succeed, because physical connectivity exists along the entire route in this state.
The explicit route has been defined to VTAM in a path definition set, is physically available to the network, and has been activated by this node or by both this node and the node at the other end of the route. A route test (TEST=YES option) should succeed, because physical connectivity exists along the entire route in this state.
The explicit route has been defined to VTAM in a path definition set and is believed to be physically available to the network. During activation processing, it was determined that one or more nodes along the route do not support the explicit route protocols. A route test (TEST=YES option) will probably fail, because one or more of its nodes does not support explicit route protocols. This does not mean that the physical connectivity of the route has failed. It only means that the route could not be completely tested because of the migration nodes.
The explicit route has been defined to VTAM in a path definition set, is physically available to the network, has not been activated by the node at the other end of the route, and is in the process of being activated by this node. A route test (TEST=YES option) should succeed, because physical connectivity exists along the entire route in this state.
The explicit route has been defined to VTAM in a path definition set and is physically available to the network, but has never been successfully activated. Activation will be attempted automatically when the ER is needed for a session. A route test (TEST=YES option) should succeed, because physical connectivity exists along the entire route in this state.
The explicit route has been defined to VTAM in a path definition set, but is not physically available to the network. That is, connectivity does not exist along the entire route. A route test (TEST=YES option) will fail, because the explicit route does not have physical connectivity.
The explicit route is physically available to the network, and activation has been attempted by the node at the other end of the route, but the route has not yet been defined to VTAM in a path definition set. The route is automatically activated by this node when an appropriate path definition set is processed. A route test (TEST=YES option) can succeed, even though the explicit route is not defined in this host. The purpose of the test is to provide information on the physical connectivity of the explicit route so that the operator can decide whether or not to define the route. In order for VTAM to carry session message traffic, the explicit route must be defined to VTAM.
The explicit route is physically available to the network, but it has not yet been defined to VTAM in a path definition set. A route test (TEST=YES option) can succeed, even though the explicit route is not defined in this host. The purpose of the test is to provide information on the physical connectivity of the explicit route so that the operator can decide whether or not to define the route. In order to be used by VTAM to carry session message traffic, the explicit route must be defined to VTAM.
The explicit route has not been defined to VTAM in a path definition set and is not physically available to the network. A route test (TEST=YES option) will always fail, because the explicit route is neither defined to VTAM nor operative.
Processing continues. If the DISPLAY ROUTE command specified TEST=YES, subsequent messages (with route display number rtn being the same as the one appearing in message IST535I) will indicate whether VTAM started any route tests and, if so, their results (as the results are received from the network).
The status might be used for information only, or might indicate that operator action is necessary if any status does not meet expectations. In particular, a virtual route or an explicit route with a status of UNDEF might indicate that a path definition set should be activated. An explicit route with a status of INOP might indicate that a subarea node, a cross-subarea link, or a cross-subarea link station should be activated, or that there is some network problem with a node, link, or link station.
None.
8
5