Explanation
IST533I ER er {SUCCEEDED|FAILED} IN ROUTE TEST routetest
IST797I FROM VIA ADJACENT DEST ER LENGTH
IST644I originpu TG [adjnode] destpu
IST534I originsa [tg1] [adjsa] destsa erlength
[IST798I netid ]
[IST572I REJECTING TG ADJACENT ER MASK]
[IST816I rejsa tg2 rejadjsa ermask]
IST523I REASON = reasonVTAM® performed a route test on an explicit route, er. VTAM receives the results of the route test and displays the information in this message group. A route test and its results were unsolicited if the route test number routetest (in message IST533I) is zero. Otherwise, they were solicited as a result of a DISPLAY ROUTE command in which the TEST=YES option was specified. For the solicited route test, routetest is the route test number that corresponds to the route status display number in the message IST535I group (which should have already been displayed as a result of the DISPLAY ROUTE command).
- Originated in node originpu, subarea number originsa,
in network netid. If name of the origin physical
unit is not available, originpu will appear as ***NA*** (not
available).
- originpu is the node specified by the ORIGIN operand of the DISPLAY ROUTE command or used by default.
- netid is displayed. It is the network ID specified either by the NETID parameter of the DISPLAY ROUTE command or in the NETID start option (during initialization of VTAM).
- Flowed through adjacent node adjnode, subarea
number adjsa. tg1 is the transmission
group number defined to the link to the adjacent subarea, adjsa.
- If the route test was unsolicited, the adjacent node does not pertain to the flow and, therefore, adjnode, adjsa, and tg1 will not be displayed. If the node name is not known, adjnode will be displayed as ***NA*** (not available).
- Was destined for node destpu, subarea number destsa.
- destsa is the destination subarea number specified by the DESTSUB operand of the DISPLAY ROUTE command. If the node name has not been defined for it, destpu will be displayed as ***NA*** (not available).
An explicit route completes a route test successfully if the route test request is successfully forwarded to and returned from the other end of the route. In order for this to occur, a physical connection must exist along the entire length of the route, with proper route definitions in each intermediate node and in the end node.
- It was rejected by the node with subarea number rejsa, adjacent to subarea number rejadjsa through transmission group number tg2. rejadjsa or tg2 or both might be zero if they are not known to the rejecting node.
- ermask is a hexadecimal 4-digit mask representing operative routes in the direction opposite the direction of the explicit route er. The first 8 bits represent ERs 0–7. If mask is 0, the ER is not reversible.
- It was rejected for one of the following values of reason:
- A REQUIRED TG IS INACTIVE
- The explicit route requires a transmission group that is not currently active somewhere along the path of the route.
- ER EXCEEDS MAXIMUM LENGTH
- The explicit route had a length in excess of the maximum possible length (that is, a routing loop might exist).
- ER NOT DEFINED
- The explicit route was not defined in the forward direction.
- ER NOT REVERSIBLE
- The explicit route was not reversible because of an incompatible definition or no definition in the reverse direction.
- MIGRATION ER NOT SUPPORTED
- A migration node was encountered. Migration nodes do not support ER or VR protocols. ER0 cannot be used.
- MIGRATION NODE DOES NOT SUPPORT THIS ER
- The adjacent subarea NCP or VTAM does not support extended subarea addressing and the explicit route being activated has an origin or destination subarea greater than 255, or an explicit route number greater than seven.
- MIGRATION NODE ENCOUNTERED
- A migration node was encountered. Migration nodes do not support ER or VR protocols. ER0 can be used.
- UNEXPECTED TYPE BYTE X'nn'
- a reason code, nn (expressed in hexadecimal), was received from the rejecting node, and VTAM does not recognize that reason code.
The following is an illustration of a typical route failure:
System action
Processing continues, regardless of the route-test results, with no effect on this host.
Operator response
If the explicit route completed the route test successfully, VTAM can use the route for routing session message traffic (provided the explicit route and an associated virtual route are defined to VTAM). No operator response is necessary unless route definitions are required, in which case the appropriate path definition sets can be activated.
If the explicit route failed the route test, an operator response might not always be necessary, but in order for VTAM to carry session message traffic on this explicit route, it must be properly defined to VTAM and all nodes on the route must support the explicit and virtual route protocols. The route-status display (message group IST535I corresponding to routetest) lists the defined or undefined status of the explicit route in this host.
- You can activate the links connecting the rejecting subarea rejsa to its adjacent node of subarea rejadjsa.
- If the problem node is not in your host, you might need to call the operator of the other domain or host to activate the nodes.
- If the test had been unsolicited and the originating node is from another host, this might indicate a request that you activate the nodes so that this other host can attempt some session traffic activities on that route.
System programmer response
The information in this group of messages is basically that which appears in the NS_ER_TESTED request unit. See the description of the explicit route test process and its associated RUs in the z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures. For more information on the DISPLAY ROUTE command, see z/OS Communications Server: SNA Operation. Most problems will be the result of inconsistent route definitions among the affected network nodes.
Routing code
8
Descriptor code
5