Sense code 8013
Route not available: No route is available to connect the specified origin subarea (OSA) and destination subarea (DSA) for the specified COS.
Note: If none of the virtual routes specified in the VR
identifier list or route specification for the session is active or
can be activated, the reported reason is set based on a hierarchy
of failure events. The "highest" of the failures that occurred
within the set of virtual routes is returned on the response. For
example, if the VR manager receives a negative response to an NC_ACTVR
request for a VR specified in the VR identifier list and for all other
VRs in the list no VR to ER mapping is specified, reason X'nn06' is
reported. The hierarchy of the failure reasons is in ascending numeric
order; that is, reason X'nn02' is higher than reason X'nn01'.
Bytes 2 and 3 following the sense code indicate the environment
in which the failure was detected and the reason for the failure.
- 0000
- No specific code applies: This means an error occurred, but none
of the conditions listed below applies. This code is issued in a
single network environment. VTAM® hint: Possible causes for this error include, but are not limited to, the following ones:
- The subarea class of service is not known. Verify that the node issuing the sense code has a usable subarea class of service for the mode associated with the session request. This problem can occur when a mode table is copied from one node to another, and the subarea classes of service specified by the table no longer map to valid COS names defined at that node.
- There is an error in the path definitions.
- 0001
- No mapping specified: A session-activation request cannot be satisfied because for each VR in the VR identifier list for the session, no VR to ER mapping is specified.
- 0002
- No explicit routes defined: A session-activation request cannot be satisfied because each VR in the VR identifier list for the session maps to a corresponding ER that is not defined. This code is issued in a single network environment.
- 0003
- No VR resource available: A session-activation request cannot be satisfied because each VR specified in the VR identifier list for the session requires a node resource that is not available. This code is issued in a single network environment.
- 0004
- No explicit routes operative: A session-activation request cannot be satisfied because no underlying ER is operative for any VR specified in the VR identifier list for the session. This code is issued in a single network environment.
- 0005
- No explicit route can be activated: A session-activation request cannot be satisfied because no VR specified in the VR identifier list for the session mapped to a defined and operative ER that could be activated. This code is issued in a single network environment.
- 0006
- No virtual route can be activated: A session-activation request cannot be satisfied because no VR specified in the VR identifier list for the session can be activated by the PU, though, for at least one VR, an underlying ER is defined, operative, and activated. This code is issued in a single network environment.
- 0007
- No virtual route identifier list available: A session-activation request cannot be satisfied because a route specification is unavailable or incomplete. A valid route specification is either a VR identifier list or a route dynamics route specification control vector. This code is issued in a single network environment.
- 0100
- No specific code applies: This means an error occurred, but none of the conditions listed below applies. This code is issued in an interconnected network. The failure was detected at a node in a subnetwork other than that of the NAU sending the activation request.
- 0101
- No mapping specified: A session-activation request cannot be satisfied
because for each VR in the VR identifier list for the session, no
VR to ER mapping is specified. This code is issued in an interconnected
network. The failure was detected at a node in a subnetwork other
than that of the NAU sending the activation request.
VTAM hint: Ensure that the PATH definition statement for the gateway NCP contains VRs coded for the networks in both directions.
- 0102
- No explicit routes defined: A session-activation request cannot be satisfied because each VR in the VR identifier list for the session maps to a corresponding ER that is not defined. This code is issued in an interconnected network. The failure was detected at a node in a subnetwork other than that of the NAU sending the activation request.
- 0103
- No VR resource available: A session-activation request cannot be satisfied because each VR specified in the VR identifier list for the session requires a node resource that is not available. This code is issued in an interconnected network. The failure was detected at a node in a subnetwork other than that of the NAU sending the activation request.
- 0104
- No explicit routes operative: A session-activation request cannot be satisfied because no underlying ER is operative for any VR specified in the VR identifier list for the session. This code is issued in an interconnected network. The failure was detected at a node in a subnetwork other than that of the NAU sending the activation request.
- 0105
- No explicit route can be activated: A session-activation request cannot be satisfied because no VR specified in the VR identifier list for the session mapped to a defined and operative ER that could be activated. This code is issued in an interconnected network. The failure was detected at a node in a subnetwork other than that of the NAU sending the activation request.
- 0106
- No virtual route can be activated: A session-activation request cannot be satisfied because no VR specified in the VR identifier list for the session can be activated by the PU, though, for at least one VR, an underlying ER is defined, operative, and activated. This code is issued in an interconnected network. The failure was detected at a node in a subnetwork other than that of the NAU sending the activation request.
- 0107
- No virtual route identifier list available: A session-activation request cannot be satisfied because a route specification is unavailable or incomplete. A valid route specification is either a VR identifier list or a route dynamics route specification control vector.