M204.2036: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
m (add <var>'s) |
||
| 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 /--> | ||
Latest revision as of 17:20, 15 March 2018
M204.2036 Sync level not supported
This error arises in two situations:
- 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.
- 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.
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.
Message attributes:
| RETCODEO=0 | Sets online return code |
|---|---|
| RETCODEB=4 | Sets batch (single user) return code |
| CLASS=E | Error class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter |
| AUDITER | Writes the message with line type ER to the audit trail |
| COUNT | Increments the error count (ERCNT) parameter |
| NOTERM | Does not display the message on the user's terminal |
| OPR | Writes the message to the (operator) console |
| SAVE | Saves the message in the VIEW ERRORS table |