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 />

IBM/<strong>Unisys</strong> State Error (Category X'20')<br />

D–22<br />

Indicates a sequence number error or an RH or RU that is not allowed for the receiver's<br />

current session control or data flow control state. These errors prevent delivery of the<br />

request to the intended component.<br />

For LU 6.2 this category will be indicated within UNBIND or on negative response to<br />

BIND.<br />

The sense code is in hexadecimal.<br />

2001 Sequence Number. Sequence number received on normal-flow request was not<br />

1 greater than the last.<br />

2002 Chaining. Error in the sequence of the chain indicator settings (BCI, ECI), such<br />

as first, middle, first.<br />

2003 Bracket. Error resulting from failure of sender to enforce bracket rules for<br />

session. (This error does not apply to contention or race conditions.)<br />

2004 Direction. Error resulting from a normal-flow request received while the<br />

half-duplex flip-flop state was Not Receive.<br />

2005 Data Traffic Reset. An FMD or normal-flow DFC request received by a<br />

half-session whose session activation state was active, but whose data traffic<br />

state was not active.<br />

2006 Data Traffic Quiesced. An FMD or DFC request received from a half-session<br />

that has QUIESCE COMPLETE or SHUTDOWN COMPLETE and has not<br />

responded to RELEASE QUIESCE.<br />

2007 Data Traffic Not Reset. A session control request (for example, STSN) allowed<br />

only while the data traffic state is reset, was received while the data traffic<br />

state was not reset.<br />

2008 No Begin Bracket. An FMD request specifying BBI = BB was received after the<br />

receiver had previously received a BRACKET INITIATION STOPPED request.<br />

2009 Session Control Protocol Violation. An SC protocol has been violated. A<br />

request, allowed only after a successful exchange of an SC request and its<br />

associated positive response, has been received before such a successful<br />

exchange has occurred (for example, an FMD request has preceded a required<br />

CRYPTOGRAPHY VERIFICATION request). The request code of the particular<br />

SC request or response required, or X'00' if determined, appears in the fourth<br />

byte of the sense data.<br />

200A Immediate Request Mode Error. The immediate request mode protocol has<br />

been violated by the request.<br />

200B Queued Response Error. The Queued Response protocol has been violated by<br />

a request; for example, QRI = ¬QR when an outstanding request had QRI = QR.<br />

7436 0728–303

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

Saved successfully!

Ooh no, something went wrong!