JAL: add `'s`

2018-03-15T17:20:49Z

add <var>'s

← Older revision		Revision as of 17:20, 15 March 2018
Line 3:		Line 3:
	<P>This error arises in two situations: </P>		<P>This error arises in two situations: </P>
	<ul>		<ul>
	<LI>Receiving an attach request for an inbound process — The remote process is running on a processgroup whose CONFIRM/NOCONFIRM parameter does not match that of the processgroup to which the local process belongs. </LI>		<LI>Receiving an attach request for an inbound process — The remote process is running on a processgroup whose <var>CONFIRM/NOCONFIRM</var> parameter does not match that of the processgroup to which the local process belongs. </LI>

	<LI>Evaluating the CONFIRM verb — SOUL (either inbound or outbound) issued the CONFIRM verb, but the conversation is using a processgroup that does not support the CONFIRM sync level. </LI>		<LI>Evaluating the <var>CONFIRM</var> verb — SOUL (either inbound or outbound) issued the <var>CONFIRM</var> verb, but the conversation is using a processgroup that does not support the <var>CONFIRM</var> sync level. </LI>
	</ul>		</ul>
	<p>		<p>
	<b>Response:</b> Work with your system administrator to clarify the sync level requirements of your application (or of the partner application). Both the local and the remote processgroups that support the conversation must have the same		<b>Response:</b> Work with your system administrator to clarify the sync level requirements of your application (or of the partner application). Both the local and the remote processgroups that support the conversation must have the same
	sync level (specified by the CONFIRM/NOCONFIRM keyword in the DEFINE PROCESSGROUP command). If either program intends to issue the CONFIRM verb, the sync level must be CONFIRM.		sync level (specified by the <var>CONFIRM</var>/<var>NOCONFIRM</var> keyword in the <var>DEFINE PROCESSGROUP</var> command). If either program intends to issue the <var>CONFIRM</var> verb, the sync level must be <var>CONFIRM</var>.
	</p>		</p>
	{{Template:M204.2036 footer}}		{{Template:M204.2036 footer}}
	<!-- skeleton as it was in pdf/SYNC LEVEL NOT SUPPORTED /-->		<!-- skeleton as it was in pdf/SYNC LEVEL NOT SUPPORTED /-->

DmeWiccan: Automatically generated page update

2018-03-14T03:27:42Z

Automatically generated page update

New page

{{Template:M204.2036 skeleton}}

This error arises in two situations: 
<ul>
<LI>Receiving an attach request for an inbound process — The remote process is running on a processgroup whose CONFIRM/NOCONFIRM parameter does not match that of the processgroup to which the local process belongs. </LI>

<LI>Evaluating the CONFIRM verb — SOUL (either inbound or outbound) issued the CONFIRM verb, but the conversation is using a processgroup that does not support the CONFIRM sync level. </LI>
</ul>

Response: Work with your system administrator to clarify the sync level requirements of your application (or of the partner application). Both the local and the remote processgroups that support the conversation must have the same
sync level (specified by the CONFIRM/NOCONFIRM keyword in the DEFINE PROCESSGROUP command). If either program intends to issue the CONFIRM verb, the sync level must be CONFIRM.

{{Template:M204.2036 footer}}

M204.2036 - Revision history

JAL: add 's

DmeWiccan: Automatically generated page update

JAL: add `'s`