M204.2350: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
 
m (add <var>s)
 
Line 2: Line 2:


<P>
<P>
A TCP/IP socket call was awaiting a completion notification from the TCPIP address space when an event (thread bump, IUCV sever, or CLOSE LINK) occurred making it impossible to wait any longer. Model&nbsp;204 attempts to send
A TCP/IP socket call was awaiting a completion notification from the TCPIP address space when an event (thread bump, IUCV sever, or <var>CLOSE LINK</var>) occurred making it impossible to wait any longer. Model&nbsp;204 attempts to send
a message to TCPIP requesting that the outstanding socket call be canceled, and this causes the socket call to complete with an abnormal return code. </P>
a message to TCPIP requesting that the outstanding socket call be canceled, and this causes the socket call to complete with an abnormal return code. </P>
<p>
<p>
<b>Response:</b> This message is intended mainly to audit the effects of certain unusual events on normal thread processing. The message will usually be seen on threads that are actively using TCP/IP when the LINK is closed forcibly, or
<b>Response:</b> This message is intended mainly to audit the effects of certain unusual events on normal thread processing. The message will usually be seen on threads that are actively using TCP/IP when the link is closed forcibly, or
when the thread is bumped by operator command. Less often it will be seen when the TCPIP address space is shut down or some other event causes an IUCV sever to occur. </p>
when the thread is bumped by operator command. Less often it will be seen when the TCPIP address space is shut down or some other event causes an IUCV sever to occur.  
</p>
{{Template:M204.2350 footer}}
{{Template:M204.2350 footer}}
<!-- skeleton as it was in pdf/SOCKET CALL COMPLETED ABNORMALLY DUE TO event /-->
<!-- skeleton as it was in pdf/SOCKET CALL COMPLETED ABNORMALLY DUE TO event /-->

Latest revision as of 22:04, 16 March 2018

M204.2350  Socket call completed abnormally due to token

A TCP/IP socket call was awaiting a completion notification from the TCPIP address space when an event (thread bump, IUCV sever, or CLOSE LINK) occurred making it impossible to wait any longer. Model 204 attempts to send a message to TCPIP requesting that the outstanding socket call be canceled, and this causes the socket call to complete with an abnormal return code.

Response: This message is intended mainly to audit the effects of certain unusual events on normal thread processing. The message will usually be seen on threads that are actively using TCP/IP when the link is closed forcibly, or when the thread is bumped by operator command. Less often it will be seen when the TCPIP address space is shut down or some other event causes an IUCV sever to occur.

Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITMSWrites the message with line type MS to the audit trail
NOCOUNTDoes not increment the error count (ERCNT) parameter

Back to list of messages