M204.3013 - Revision history

Alex: Note the blank-value variant and what it indicates

2026-10-05T01:17:08Z

Note the blank-value variant and what it indicates

← Older revision		Revision as of 01:17, 5 October 2026
Line 4:		Line 4:
	cannot determine whether the transaction committed. It queries a broker to		cannot determine whether the transaction committed. It queries a broker to
	establish the outcome, issuing this message every five seconds until the outcome		establish the outcome, issuing this message every five seconds until the outcome
	is known~~. The message names the resource awaited: an Imagine Transparency~~		is known. Until the outcome is known, the Model 204 updates are neither
	~~Broker, or CCATEMP pages~~. Until the outcome is known, the Model 204 updates are		committed nor backed out.
	~~neither~~ committed nor backed out.		</p>
			<p>
			The value shown is the resource being waited for, normally an Imagine
			Transparency Broker, or CCATEMP pages when CCATEMP is the shortage. The message
			may also appear with no value at all, which indicates that a broker was
			contacted but the exchange with it failed.
	</p>		</p>
	<p>		<p>

Alex: Rewrite description to match house style

2026-10-04T13:13:38Z

Rewrite description to match house style

← Older revision		Revision as of 13:13, 4 October 2026
Line 1:		Line 1:
	{{Template:M204.3013 skeleton}}		{{Template:M204.3013 skeleton}}
	<p>		<p>
	Model 204 ~~has~~ sent a commit to Imagine and ~~has~~ not ~~received~~ the response, so it		Model 204 sent a commit to Imagine and did not receive the response, so it
	cannot determine whether the transaction committed. It ~~retries until it~~		cannot determine whether the transaction committed. It queries a broker to
	~~establishes~~ the outcome, issuing this message every five seconds ~~while it does~~		establish the outcome, issuing this message every five seconds until the outcome
	so. The ~~value shown is~~ the resource ~~being waited for~~: an Imagine Transparency		is known. The message names the resource awaited: an Imagine Transparency
	Broker, or CCATEMP pages ~~when CCATEMP is the shortage~~.		Broker, or CCATEMP pages. Until the outcome is known, the Model 204 updates are
	~~</p>~~		neither committed nor backed out.
	~~<p>~~
	Until the outcome is ~~established the transaction is in doubt~~, ~~and~~ the Model 204
	updates are neither committed nor backed out~~. If the message continues to be~~
	~~issued, no broker has established the outcome, and the thread cannot complete~~
	~~the transaction until one does~~.
	</p>		</p>
	<p>		<p>

Alex: State the substituted value and the in-doubt consequence precisely

2026-10-04T02:19:10Z

State the substituted value and the in-doubt consequence precisely

← Older revision		Revision as of 02:19, 4 October 2026
Line 2:		Line 2:
	<p>		<p>
	Model 204 has sent a commit to Imagine and has not received the response, so it		Model 204 has sent a commit to Imagine and has not received the response, so it
	cannot determine whether the transaction committed. It ~~queries a broker to~~		cannot determine whether the transaction committed. It retries until it
	~~establish~~ the outcome ~~and repeats~~ this message every five seconds ~~until the~~		establishes the outcome, issuing this message every five seconds while it does
	~~outcome is known~~. The value shown is ~~what it~~ is ~~waiting for~~.		so. The value shown is the resource being waited for: an Imagine Transparency
			Broker, or CCATEMP pages when CCATEMP is the shortage.
	</p>		</p>
	<p>		<p>
	~~The~~ Model 204 updates ~~can be~~ neither committed nor backed out ~~until a broker~~		Until the outcome is established the transaction is in doubt, and the Model 204
	~~answers definitively~~. If the message ~~repeats indefinitely~~, no broker ~~is able to~~		updates are neither committed nor backed out. If the message continues to be
	~~supply that answer~~.		issued, no broker has established the outcome, and the thread cannot complete
			the transaction until one does.
	</p>		</p>
	<p>		<p>

Alex: Clarify commit handling; tighten wording

2026-10-04T02:15:27Z

Clarify commit handling; tighten wording

← Older revision		Revision as of 02:15, 4 October 2026
Line 1:		Line 1:
	{{Template:M204.3013 skeleton}}		{{Template:M204.3013 skeleton}}
	<p>		<p>
	Model 204 sent a commit to Imagine and ~~did~~ not ~~receive~~ the response, so it ~~can~~		Model 204 has sent a commit to Imagine and has not received the response, so it
	~~neither commit~~ the transaction ~~nor back it out until it discovers what Imagine~~		cannot determine whether the transaction committed. It queries a broker to
	~~did with it~~. It ~~asks~~ a broker, and repeats this message every five seconds ~~for~~		establish the outcome and repeats this message every five seconds until the
	~~as long as it has no answer~~. The value shown is what it is waiting for.		outcome is known. The value shown is what it is waiting for.
	</p>		</p>
	<p>		<p>
	The ~~wait ends as soon as~~ a broker answers. If the message ~~continues~~		The Model 204 updates can be neither committed nor backed out until a broker
	indefinitely, ~~the brokers are not in a position~~ to answer~~, and the thread cannot~~		answers definitively. If the message repeats indefinitely, no broker is able to
	~~go either way until they are~~.		supply that answer.
	</p>		</p>
	<p>		<p>

Alex: Add description for Imagine Transparency message

2026-10-04T01:19:34Z

Add description for Imagine Transparency message

New page

{{Template:M204.3013 skeleton}}

Model 204 sent a commit to Imagine and did not receive the response, so it can
neither commit the transaction nor back it out until it discovers what Imagine
did with it. It asks a broker, and repeats this message every five seconds for
as long as it has no answer. The value shown is what it is waiting for.


The wait ends as soon as a broker answers. If the message continues
indefinitely, the brokers are not in a position to answer, and the thread cannot
go either way until they are.


Response:

{{Template:M204.3013 footer}}