30.01.2013 Views

DCP Series Telcon Message Manual - Public Support Login - Unisys

DCP Series Telcon Message Manual - Public Support Login - Unisys

DCP Series Telcon Message Manual - Public Support Login - Unisys

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Sense Data<br />

800A Too-Long PIU. Transmission was truncated by a receiving node because the<br />

PIU exceeded a maximum length or sufficient buffering was not available.<br />

800B Incomplete TH. Transmission received was shorter than a TH.<br />

Note: It is usually not possible to send a response for this exception<br />

condition because information (FID, addresses) required to<br />

generate a response is not available. It is logged as an error if this<br />

capability exists in the receiver.<br />

800C DFC Error. Data Count field inconsistent with transmission length.<br />

800D Lost Contact. Contact with the link station for which the transmission was<br />

intended has been lost, but the link has not failed. If the difference between<br />

link failure and loss of contact is not detectable, link failure (X'8002') is sent.<br />

800E Unrecognized Origin. The origin address specified in the TH was not<br />

recognized.<br />

800F The address combination is invalid.<br />

8010 Segmented RU Length Error. An RU was found to exceed a maximum length or<br />

required buffer allocation that might cause future buffer depletion.<br />

8011 ER Inoperative or Undefined. A PIU was received from subarea node that does<br />

not support ER and VR protocols and the explicit route to the destination is<br />

inoperative or undefined.<br />

8012 Subarea PU Not Active or Invalid Virtual Route. A session-activation request<br />

for a peripheral PU or LU cannot be satisfied because there is no active SSCP–<br />

PU session for the subarea node providing boundary function support, or the<br />

virtual route for the specified SSCP–PU (type1 or type 2 nodes) or SSCP–LU<br />

session is not the same as that used for the SSCP–PU session of the type 1 or<br />

type 2 node's PU or the LU's subarea PU.<br />

8013 COS Not Available. A session activation request cannot be satisfied because<br />

none of the virtual routes requested for the session is available.<br />

8014 Reserved.<br />

through<br />

8016<br />

8017 PIU from Adjacent Pre-ER-VR Subarea Node Rejected. A PIU that requires<br />

intermediate path-control routing was received by a subarea node from an<br />

adjacent subarea node that does not support ER–VR protocols, but the<br />

receiving subarea node does not support intermediate path-control routing for<br />

adjacent subarea nodes that do not support ER–VR protocols.<br />

8018 Management Services component is unable to find or recognize the name of the<br />

application transaction program specified in the request.<br />

7436 0728–303 D–27

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!