JAL: add link

2018-03-12T19:24:20Z

add link

← Older revision		Revision as of 19:24, 12 March 2018
Line 1:		Line 1:
	{{Template:M204.1796 skeleton}}		{{Template:M204.1796 skeleton}}
	<P>		<P>
	The process-to-process communications link (CRAM or VMCF) closed unexpectedly. Data transmission is no longer possible. </P>		The process-to-process communications link ([[Cross-memory facilities CRAM and M204XSVC\|CRAM]] or VMCF) closed unexpectedly. Data transmission is no longer possible. </P>
	<p>		<p>
	<b>Response:</b> This could be a result of the partner process region closing the CRAM or VMCF channel unexpectedly. Also, it is possibly due to the partner process program abending. For example: </p>		<b>Response:</b> This could be a result of the partner process region closing the CRAM or VMCF channel unexpectedly. Also, it is possibly due to the partner process program abending. For example: </p>
	<ul>		<ul>
	<li>The SOUL request issues an ~~OPEN PROCESS~~ statement. This causes a partner process to be invoked. </li>		<li>The SOUL request issues an <var>Open Process</var> statement. This causes a partner process to be invoked. </li>

	<li>The SOUL request issues a ~~SEND~~ statement and waits. </li>		<li>The SOUL request issues a <var>Send</var> statement and waits. </li>

	<li>The partner process abends prior to calling the IFRECV function. This causes the Model 204 external interface (CICS, CMS or TSO) to ABEND and, therefore, the CRAM or VMCF connection is closed. </li>		<li>The partner process abends prior to calling the <var>IFRECV</var> function. This causes the Model 204 external interface (CICS, CMS or TSO) to ABEND and, therefore, the CRAM or VMCF connection is closed. </li>

	<li>The SOUL request regains control with the $~~STATUS~~ and $~~STATUSD~~ functions returning the "serious error" and 1796 values, respectively. </li>		<li>The SOUL request regains control with the <var>$Status</var> and <var>$StatusD</var> functions returning the "serious error" and 1796 values, respectively. </li>
	</ul>		</ul>
	<p>		<p>

DmeWiccan: Automatically generated page update

2018-03-07T16:11:31Z

Automatically generated page update

New page

{{Template:M204.1796 skeleton}}

The process-to-process communications link (CRAM or VMCF) closed unexpectedly. Data transmission is no longer possible. 

Response: This could be a result of the partner process region closing the CRAM or VMCF channel unexpectedly. Also, it is possibly due to the partner process program abending. For example: 
<ul>
<li>The SOUL request issues an OPEN PROCESS statement. This causes a partner process to be invoked. </li>

<li>The SOUL request issues a SEND statement and waits. </li>

<li>The partner process abends prior to calling the IFRECV function. This causes the Model 204 external interface (CICS, CMS or TSO) to ABEND and, therefore, the CRAM or VMCF connection is closed. </li>

<li>The SOUL request regains control with the $STATUS and $STATUSD functions returning the "serious error" and 1796 values, respectively. </li>
</ul>

System manager response: If this error occurs as a result of the Model 204 external interface (CICS, CMS or TSO) abending, save relevant information and contact [[Contacting Rocket Software Technical Support|Technical Support]].

{{Template:M204.1796 footer}}

M204.1796 - Revision history

JAL: add link

DmeWiccan: Automatically generated page update