IST522I

For an explicit route activation

Explanation
 This message is the first in a group of messages
that VTAM® issues for one of
these conditions:  A virtual or explicit route activation initiated by this VTAM node failed in the network.
An activation request received from the network by this VTAM node was rejected.

 A complete description of the message group follows.   IST522I {ER|VR} n ACT {FAILED|REJECTED} SA subarea1 TO SA subarea2 [FOR TPi]
 IST523I  REASON = reason
[IST524I  REVERSE ER MASK = ermask]
[IST525I  REJECTING SA subarea3 USING TG tg ADJACENT SA subarea4]

 Note: FOR
TPi appears only when VR n appears.
 For
an explicit route activation:
 IST522I  This message indicates that the activation was rejected if the
reason for the failure is in this node, or indicates that the activation
failed if some node along the route could not permit the activation.
n indicates the one or two-digit ER number.
subarea1 and subarea2 are
decimal subarea numbers specifying, respectively, the node that began
the route activation and the node at the other end of the route.

 IST523I  This message indicates the problem in the rejecting node.
reason might be one of the following:  A REQUIRED TG IS INACTIVE
A required transmission group (TG) is not active somewhere along
the path of the route.
EXPLICIT ROUTE NOT DEFINED
The explicit route is not defined (in the forward direction).
EXPLICIT ROUTE NOT REVERSIBLE
A useable explicit route in the reverse direction cannot be found
(because of an incompatible definition or no definition in the reverse
direction).
EXPLICIT ROUTE LENGTH EXCEEDS MAXIMUM
The explicit route has a length in excess of the maximum possible
length (that is, a routing loop exists).
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.
UNEXPECTED TYPE BYTE X‘nn’
An unrecognizable failure code nn was received
from the rejecting node.

 IST524I  ermask is the reverse explicit route mask as
received in an NC_ER_ACT or NC_ER_ACT_REPLY RU. This mask indicates
the explicit route numbers for flow in the direction opposite the
direction of ER n.
If the explicit route activation failed in the network, VTAM issues message IST525I, indicating
the transmission group identifier (tg) at the point
of rejection.

 IST525I  subarea3 is the subarea address of the network
node rejecting the activation.
tg is the number of the transmission group
to or from an adjacent node.
subarea4 is the subarea address of the applicable
adjacent node.  Note: The transmission group number or the subarea
number of the adjacent node or both might be zero if these numbers
are unknown to the rejecting node.

 For a virtual route activation, messages
IST522I, IST523I, and (sometimes) IST524I will appear.
 Note: This
message group will appear only once in a display, though multiple
sessions might attempt to establish routing from subarea1 to subarea2.
 IST522I  n indicates the one-digit virtual route number.
subarea1 and subarea2 specify,
respectively, the node that began the route activation and the node
at the other end of the route.
TPi is the transmission priority of
the route activation.

 IST523I  This message indicates the problem in the rejecting node.
reason might be one of the following:  ACTVR RESPONSE SENSE IS  sense
The node that began the route activation sent the REASON information.
See the z/OS Communications Server: IP and SNA Codes for additional information on sense codes.
UNDEFINED EXPLICIT ROUTE REQUESTED
The explicit route defined for use with the virtual route is undefined
in this node.
INCORRECT EXPLICIT ROUTE REQUESTED
The node at the other end of the route specified one or more reverse
explicit route numbers that are inconsistent with the route definitions
in this node.
VIRTUAL ROUTE NOT DEFINED
The virtual route is not defined.

 IST524I  ermask is the reverse explicit route mask as
received in an NC_ER_ACT or NC_ER_ACT_REPLY RU. This mask indicates
the explicit route numbers for flow in the direction opposite the
direction of ER n.

System action
  If this VTAM node rejected
a route-activation attempt from another network node, processing continues
with no effect on this node.
If a route activation initiated by this node failed, then some
other network node rejected the route-activation request. The failing
host continues processing the generic BIND that caused the activation
attempt, and places it on some other available route in its requested
COS.
If no routes are available, the generic BIND fails or is queued
to wait for a usable route.

Operator response

 For a route-activation indicated
as FAILED:  The problem is probably at the node that rejected the route-activation
RU.
If message IST525I is present, it identifies the rejecting node.
If message IST525I is not present (as for a virtual route activation
failure), the node at the far end of the route subarea2 is
the rejecting node.
If an explicit route activation failed because it requires a currently
inactive transmission group (TG) in order to complete the route’s
physical connectivity, the TG might be activated if the node containing
the inactive TG is active or can be made active to this VTAM. Otherwise, call the operator of whatever
host owns the node containing the inactive TG and request activation
of the TG.
If route activation failed because it is a migration ER0 that
is not supported by VTAM, this
is probably a route-definition error. Bring this to the attention
of your system programmer.

 For a route-activation indicated as REJECTED:  If message IST522I indicates that his VTAM node rejected a route-activation RU, the
problem is in this node. With the following exceptions, your system
programmer will need to be informed. The exceptions are:  When an ER activation was rejected because the ER is not reversible.
When a VR activation was rejected because the VR is not defined.
(An ER that is "not reversible" either is not defined or is incompatibly
defined in the reverse direction, that is, in the direction from the
rejecting VTAM node issuing
this message to the node originating the ER activation.)

  In these cases, an appropriate path definition set might
be activated to cause the applicable route to become properly defined.

System programmer response
 The information in this group of
messages is basically that which appears in the NC_ER_ACT, NC_ER_ACT_REPLY,
or NC_ACTVR request units, or the sense information that might appear
in the NC_ACTVR response unit.
 If this host rejected a virtual
route's activation because an incorrect explicit route was requested,
you might not be able to resolve the problem. The situation is one
of the following:  The explicit route for the subject virtual route is defined on
a physical path different from that defined at the other end of the
route (that is, inconsistent route definitions).
The applicable path deck has only recently been activated, and
the other end of the route has tried to activate a virtual route before
being notified of one or more new explicit route definitions. Because
this is a timing problem, there is no action that you can take. The
next attempt to activate the virtual route should succeed.

Routing code
 8

Descriptor code
 4 