M204.1968 - Revision history

ELowell at 21:28, 10 April 2018

2018-04-10T21:28:16Z

← Older revision		Revision as of 21:28, 10 April 2018
Line 2:		Line 2:
	<P>		<P>
	A [[Horizon]] statement failed to complete in the length of time specified by the <var>TIMEOUT</var> parameter of the <var>[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM\|DEFINE PROCESS]]</var> command. The process is automatically closed, the SNA Communications Server (also known as VTAM)		A [[Horizon]] statement failed to complete in the length of time specified by the <var>TIMEOUT</var> parameter of the <var>[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM\|DEFINE PROCESS]]</var> command. The process is automatically closed, the SNA Communications Server (also known as VTAM)
	session is terminated, and the Horizon statement ends with <var>$Status</var> codes of <code>53-2</code>. The SNA Communications Server request that timed out is identified by <var class="term">~~token0~~</var>. This error is most likely to occur when a process expects a reply from the partner		session is terminated, and the Horizon statement ends with <var>$Status</var> codes of <code>53-2</code>. The SNA Communications Server request that timed out is identified by <var class="term">token</var>. This error is most likely to occur when a process expects a reply from the partner
	(as in RECEIVE or CONFIRM) and does not receive one within the time limit. </P>		(as in RECEIVE or CONFIRM) and does not receive one within the time limit. </P>
	<p>		<p>

JAL: add link

2018-03-26T21:06:49Z

add link

← Older revision		Revision as of 21:06, 26 March 2018
Line 1:		Line 1:
	{{Template:M204.1968 skeleton}}		{{Template:M204.1968 skeleton}}
	<P>		<P>
	A Horizon statement failed to complete in the length of time specified by the <var>TIMEOUT</var> parameter of the <var>[[~~DEFINE_PROCESS_command~~:~~_Horizon_for_TCP~~/~~IP_and_VTAM~~\|DEFINE PROCESS]]</var> command. The process is automatically closed, the SNA Communications Server (also known as VTAM)		A [[Horizon]] statement failed to complete in the length of time specified by the <var>TIMEOUT</var> parameter of the <var>[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM\|DEFINE PROCESS]]</var> command. The process is automatically closed, the SNA Communications Server (also known as VTAM)
	session is terminated, and the Horizon statement ends with <var>$Status</var> codes of <code>53-2</code>. The SNA Communications Server request that timed out is identified by <var class="term">token0</var>. This error is most likely to occur when a process expects a reply from the partner		session is terminated, and the Horizon statement ends with <var>$Status</var> codes of <code>53-2</code>. The SNA Communications Server request that timed out is identified by <var class="term">token0</var>. This error is most likely to occur when a process expects a reply from the partner
	(as in RECEIVE or CONFIRM) and does not receive one within the time limit. </P>		(as in RECEIVE or CONFIRM) and does not receive one within the time limit. </P>
Line 9:		Line 9:
	<p>		<p>
	<b>System manager response:</b> Determine whether or not an SNA Communications Server session was ever established for the conversation. If not, try to determine why a session could not be established with the remote LU. Otherwise, obtain the audit		<b>System manager response:</b> Determine whether or not an SNA Communications Server session was ever established for the conversation. If not, try to determine why a session could not be established with the remote LU. Otherwise, obtain the audit
	trail, any audit information available from the remote LU, and an SNA Communications Server trace, and contact [[Contacting Rocket Software Technical Support\|Technical Support]]. </p>		trail, any audit information available from the remote LU, and an SNA Communications Server trace, and contact [[Contacting Rocket Software Technical Support\|Technical Support]].
			</p>
	{{Template:M204.1968 footer}}		{{Template:M204.1968 footer}}
	<!-- skeleton as it was in pdf/PROCESS TIMED OUT WAITING FOR COMPLETION OF VTAM_function /-->		<!-- skeleton as it was in pdf/PROCESS TIMED OUT WAITING FOR COMPLETION OF VTAM_function /-->

ELowell at 23:05, 16 March 2018

2018-03-16T23:05:13Z

← Older revision		Revision as of 23:05, 16 March 2018
Line 1:		Line 1:
	{{Template:M204.1968 skeleton}}		{{Template:M204.1968 skeleton}}
	<P>		<P>
	A Horizon statement failed to complete in the length of time specified by the <var>TIMEOUT</var> parameter of the <var>DEFINE PROCESS</var> command. The process is automatically closed, the SNA Communications Server (also known as VTAM)		A Horizon statement failed to complete in the length of time specified by the <var>TIMEOUT</var> parameter of the <var>[[DEFINE_PROCESS_command:_Horizon_for_TCP/IP_and_VTAM\|DEFINE PROCESS]]</var> command. The process is automatically closed, the SNA Communications Server (also known as VTAM)
	session is terminated, and the Horizon statement ends with <var>$Status</var> codes of <code>53-2</code>. The SNA Communications Server request that timed out is identified by <var class="term">token0</var>. This error is most likely to occur when a process expects a reply from the partner		session is terminated, and the Horizon statement ends with <var>$Status</var> codes of <code>53-2</code>. The SNA Communications Server request that timed out is identified by <var class="term">token0</var>. This error is most likely to occur when a process expects a reply from the partner
	(as in RECEIVE or CONFIRM) and does not receive one within the time limit. </P>		(as in RECEIVE or CONFIRM) and does not receive one within the time limit. </P>

DmeWiccan: Automatically generated page update

2018-03-07T17:38:06Z

Automatically generated page update

New page

{{Template:M204.1968 skeleton}}

A Horizon statement failed to complete in the length of time specified by the <var>TIMEOUT</var> parameter of the <var>DEFINE PROCESS</var> command. The process is automatically closed, the SNA Communications Server (also known as VTAM)
session is terminated, and the Horizon statement ends with <var>$Status</var> codes of <code>53-2</code>. The SNA Communications Server request that timed out is identified by <var class="term">token0</var>. This error is most likely to occur when a process expects a reply from the partner
(as in RECEIVE or CONFIRM) and does not receive one within the time limit. 

Response: Make sure that the value of the <var>TIMEOUT</var> parameter on the <var>DEFINE PROCESS</var> command is reasonable. Take into account the length of time the partner process may need to be compiled and to perform whatever processing is
necessary before sending its reply. If you are confident that the <var>TIMEOUT</var> parameter is reasonable, contact the system manager. 

System manager response: Determine whether or not an SNA Communications Server session was ever established for the conversation. If not, try to determine why a session could not be established with the remote LU. Otherwise, obtain the audit
trail, any audit information available from the remote LU, and an SNA Communications Server trace, and contact [[Contacting Rocket Software Technical Support|Technical Support]]. 
{{Template:M204.1968 footer}}