JAL: add `s`

2018-03-16T22:04:45Z

add <var>s

← Older revision		Revision as of 22:04, 16 March 2018
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 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 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 /-->

DmeWiccan: Automatically generated page update

2018-03-14T03:42:47Z

Automatically generated page update

New page

{{Template:M204.2350 skeleton}}


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. 
{{Template:M204.2350 footer}}

M204.2350 - Revision history

JAL: add s

DmeWiccan: Automatically generated page update

JAL: add `s`