M204.3002: Difference between revisions

From m204wiki
Jump to navigation Jump to search
Add description for Imagine Transparency message
 
Clarify commit handling; tighten wording
Line 3: Line 3:
The connection to the Imagine broker was lost. Model 204 issues this wherever it
The connection to the Imagine broker was lost. Model 204 issues this wherever it
finds the connection gone: during a call, while sending updates, at commit, or
finds the connection gone: during a call, while sending updates, at commit, or
while syncing a file. The request is cancelled and any transaction in progress
while syncing a file. In most cases the request is cancelled and any transaction
is backed out.
in progress is backed out.
</p>
</p>
<p>
<p>
Losing the connection after a commit has been sent but before the response
A commit is the exception. Model 204 has sent the commit but has not received the
arrives is the awkward case, because Model 204 then knows neither that the
response, so it cannot know whether Imagine committed the transaction, and it
transaction committed nor that it did not. It asks a broker what became of it,
cannot simply back out. It must find another broker, waiting for one if none is
and reports that it is still asking with M204.3013.
currently available, and ask whether the transaction completed. Only when that
has been definitively established can Model 204 decide whether to commit or back
out its own updates. M204.3013 is issued while it waits.
</p>
</p>
<p>
<p>

Revision as of 02:15, 4 October 2026

M204.3002  Connection to Imagine Broker lost

The connection to the Imagine broker was lost. Model 204 issues this wherever it finds the connection gone: during a call, while sending updates, at commit, or while syncing a file. In most cases the request is cancelled and any transaction in progress is backed out.

A commit is the exception. Model 204 has sent the commit but has not received the response, so it cannot know whether Imagine committed the transaction, and it cannot simply back out. It must find another broker, waiting for one if none is currently available, and ask whether the transaction completed. Only when that has been definitively established can Model 204 decide whether to commit or back out its own updates. M204.3013 is issued while it waits.

Response:

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
AUDITMSWrites the message with line type MS to the audit trail
CANCELCancels the user's request
NOCOUNTDoes not increment the error count (ERCNT) parameter

Back to list of messages