M204.2561 - Revision history

ELowell at 22:10, 27 March 2018

2018-03-27T22:10:50Z

← Older revision		Revision as of 22:10, 27 March 2018
Line 2:		Line 2:

	<P>		<P>
	An External Call Facility (ECF) operation failed when processing the external module named in the message.</P>		An [[External Call Facility]] (ECF) operation failed when processing the external module named in the message.</P>
	<ul>		<ul>
	<LI>Operation (<var class="term">~~token0~~</var>) can be one of:		<LI>Operation (<var class="term">token</var>) can be one of:
	<TABLE>		<TABLE>
	<TR class="head"><TH><P>Operation </P></TH>		<TR class="head"><TH><P>Operation </P></TH>

JAL: add periods

2018-03-20T18:52:12Z

add periods

← Older revision		Revision as of 18:52, 20 March 2018
Line 47:		Line 47:
	</ul>		</ul>
	<P>		<P>
	The message always reports either a Return code or a Completion code and associated Reason code</P>		The message always reports either a Return code or a Completion code and associated Reason code.</P>
	<p>		<p>
	<b>Response:</b> Determine what action needs to be taken, based on the error code		<b>Response:</b> Determine what action needs to be taken, based on the error code.
	</p>		</p>
	{{Template:M204.2561 footer}}		{{Template:M204.2561 footer}}
	<!-- skeleton as it was in pdf/ECF operation MODULE=name COMPLETION=code REASON=code RETURN=code ECTASK=addr TCB=addr/-->		<!-- skeleton as it was in pdf/ECF operation MODULE=name COMPLETION=code REASON=code RETURN=code ECTASK=addr TCB=addr/-->

DmeWiccan: Automatically generated page update

2018-03-13T17:33:23Z

Automatically generated page update

New page

{{Template:M204.2561 skeleton}}


An External Call Facility (ECF) operation failed when processing the external module named in the message.
<ul>
<LI>Operation (<var class="term">token0</var>) can be one of:
<TABLE>
<TR class="head"><TH>Operation </TH>
<TH>You issued ECF statement </TH>
<TH>z/OS response</TH></TR>

<TR><TD>CALL </TD>
<TD>EXTERNAL CALL </TD>
<TD>ABEND external program</TD></TR>

<TR><TD>DELETE </TD>
<TD>EXTERNAL DELETE </TD>
<TD>Issue an error to DELETE request</TD></TR>

<TR><TD>LOAD ABENDED </TD>
<TD>EXTERNAL LOAD </TD>
<TD>ABEND during this processing</TD></TR>

<TR><TD>LOAD FAILED </TD>
<TD>EXTERNAL LOAD </TD>
<TD>Issue an error to LOAD request</TD></TR>
</TABLE></li>

<LI>Completion code (<var class="term">token3</var>) has two formats:
<TABLE>
<TR class="head"><TH>Completion code </TH>
<TH>Type of code</TH></TR>

<TR><TD>Snnn </TD>
<TD>z/OS system code, described in <var class="book">IBM z/OS System Codes, GC28-1780</var></TD></TR>

<TR>
<TD>Unnnn </TD>
<TD>User ABEND code, issued by the external program that ABENDed</TD></TR>
</TABLE>

The Completion code is a hexadecimal value for system codes and a decimal value for user ABEND codes.</li>

<LI>Reason code (<var class="term">token4</var>) is a hexadecimal value.</LI>

<LI>Return code (<var class="term">token5</var>) is a decimal value.</LI>
</ul>

The message always reports either a Return code or a Completion code and associated Reason code

Response: Determine what action needs to be taken, based on the error code

{{Template:M204.2561 footer}}