DCP Series Telcon Message Manual - Public Support Login - Unisys

Sense Data
IBM/Unisys Path Error (Category X'80')
D–26
Indicates that the request could not be delivered to the intended receiver because of a
path outage, an invalid sequence of activation requests, or one of the listed path
information unit (PIU) errors. Some PIU errors fall into other categories. For example,
sequence number errors are sense code category X'20'. A path error received while the
session is active usually indicates that the path to the session partner was lost.
The sense code is in hexadecimal.
8001 Intermediate Node Failure. Machine or program check in a node providing
intermediate routing function. A response may or may not be possible.
8002 Link Failure. Data link failure.
8003 NAU Inoperative. The NAU is unable to process requests or responses. For
example, the NAU has been disrupted by an abnormal termination.
8004 Unrecognized Destination. A node in the path has no routing information for
the destination specified either by the SLU name in a BIND request or by the
TH.
8005 No Session. No half-session is active in the receiving end node for the
indicated origination-destination pair or no boundary function session
connector is active for the origin-destination pair in a node providing the
boundary function. A session activation request is needed.
8006 Invalid FID. Invalid FID for the receiving node.
Note: It is usually not possible to send a response for this exception
condition because information (FID, addresses) required to
generate a response is not available. It is logged as an error if this
capability exists in the receiver.
8007 Segmenting Error. First BIU segment had less than 10 bytes; mapping field
sequencing error, such as first, last, middle; or segmenting not supported and
mapping field not set to BBIU, EBIU.
Note: If segmenting is not supported, a negative response is returned for
the first segment only, since this contains the RH. Subsequent
segments are discarded.
8008 PU Not Active. The SSCP–PU secondary half-session in the receiving node has
not been activated and the request was not ACTPU for this half-session. For
example, the request was ACTLU from an SSCP that does not have an active
SSCP–PU session with the PU associated with the addressed LU.
8009 LU Not Active. The destination address specifies an LU for which the SSCP–LU
secondary half-session has not been activated and the request was not ACTLU.
7436 0728–303