M204.1101: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
m (remove 0 from token0) |
||
| Line 3: | Line 3: | ||
Horizon has received unexpected data, possibly due to an LU 6.2 protocol violation by the remote partner. </p> | Horizon has received unexpected data, possibly due to an LU 6.2 protocol violation by the remote partner. </p> | ||
<p> | <p> | ||
<var class="term"> | <var class="term">token</var> identifies the type of data that was expected. </p> | ||
<p> | <p> | ||
<var class="term"> | <var class="term">hexValue</var> shows the 3-byte SNA Communications Server | ||
(also known as VTAM) request header, in hexadecimal. </p> | (also known as VTAM) request header, in hexadecimal. </p> | ||
<p> | <p> | ||
Latest revision as of 17:33, 26 March 2018
M204.1101 Unexpected token receipt -- rh=hexValue, ru=hexValue2...
Horizon has received unexpected data, possibly due to an LU 6.2 protocol violation by the remote partner.
token identifies the type of data that was expected.
hexValue shows the 3-byte SNA Communications Server (also known as VTAM) request header, in hexadecimal.
hexValue2 shows the first 16 bytes of the SNA Communications Server request unit, in hexadecimal.
This message is preceded by message M204.1100, which contains additional diagnostic information.
Response: Contact the System Manager
System manager response: See message M204.1100.
Message attributes:
| RETCODEO=0 | Sets online return code |
|---|---|
| RETCODEB=4 | Sets batch (single user) return code |
| CLASS=E | Error class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter |
| AUDITER | Writes the message with line type ER to the audit trail |
| COUNT | Increments the error count (ERCNT) parameter |