Sense code 8019

Routing exception: a node is unable to perform the required routing function for a request.

Bytes 2 and 3 following the sense code contain sense code specific information.

0000: No specific code applies.
0001: Unknown routing group name.
0002: Unknown routing group name, routing element name combination.
0004: No connection is available for level of service required.
0005: The routing and targeting instructions GDS variable is is required but is not present.
0006: The internetwork route selection subfield (IRSS) was required to be included in a BIND RSCV, but was either missing or had a format which was not valid.
0007: The internetwork route selection subfield (IRSS) was required to be included in a locate request or reply, but was either missing or had format that was not valid.
0008: The border node detected multiple instances of its own name in the internetwork route selection subfield (IRSS) in a locate request or reply or in a BIND, indicating a routing loop.
0009: An explicit route was not available to permit activation of a virtual route-based APPN TG.
000A: An activation request was received that was not valid for the current state of the specified virtual route-based APPN TG.
000B: Origin node not found. TRS received a route calculation request with no origin endpoint TG vectors and could not find a node entry for the origin node in the topology database.
000C: When the DLUS node received a locate request for a DLUS-served dependent LU, the DLUS node determined that at least one intersubnetwork TG on the path between DLUS and the PLU was not between two extended border nodes.
VTAM® hint: The dependent LU server (DLUS) and the PLU node are in different APPN subnetworks, which requires that an extended border node be present in both the PLU subnetwork and the DLUS subnetwork. This session path does not have an extended border node in either the PLU subnetwork or the DLUS subnetwork.