M204.2590: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
m (add link) |
||
Line 2: | Line 2: | ||
<P> | <P> | ||
The Horizon for TCP/IP interface received notification that a socket is ready for reading, but the Horizon session manager does not recognize this socket connection as extant. This may be the result of an application | The [[Horizon TCP/IP|Horizon for TCP/IP]] interface received notification that a socket is ready for reading, but the Horizon session manager does not recognize this socket connection as extant. This may be the result of an application error, a temporary increase in system load, or an internal error in the Horizon for TCP/IP interface or in TCP/IP itself.</P> | ||
error, a temporary increase in system load, or an internal error in the Horizon for TCP/IP interface or in TCP/IP itself.</P> | |||
<p> | <p> | ||
<b>Response:</b> Contact your system manager.</p> | <b>Response:</b> Contact your system manager.</p> |
Latest revision as of 20:05, 20 March 2018
M204.2590 SESD for socket token link token2 unexpectedly deallocated before socket data could be read
The Horizon for TCP/IP interface received notification that a socket is ready for reading, but the Horizon session manager does not recognize this socket connection as extant. This may be the result of an application error, a temporary increase in system load, or an internal error in the Horizon for TCP/IP interface or in TCP/IP itself.
Response: Contact your system manager.
System manager response: Contact Technical Support for further instructions.
Message attributes:
RETCODEO=0 | Sets online return code |
---|---|
RETCODEB=0 | Sets batch (single user) return code |
CLASS=I | Information class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter |
AUDITAD | Writes the message with line type AD to the audit trail |
NOCOUNT | Does not increment the error count (ERCNT) parameter |