M204.1796: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
 
m (add link)
 
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&nbsp;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&nbsp;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>

Latest revision as of 19:24, 12 March 2018

M204.1796  Process-to-process communications link has been closed

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:

  • The SOUL request issues an Open Process statement. This causes a partner process to be invoked.
  • The SOUL request issues a Send statement and waits.
  • 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.
  • The SOUL request regains control with the $Status and $StatusD functions returning the "serious error" and 1796 values, respectively.

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 Technical Support.

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
AUDITERWrites the message with line type ER to the audit trail
COUNTIncrements the error count (ERCNT) parameter
SAVESaves the message in the VIEW ERRORS table

Back to list of messages