Transaction back out - Revision history

ELowell at 17:34, 19 February 2019

2019-02-19T17:34:44Z

← Older revision		Revision as of 17:34, 19 February 2019
Line 220:		Line 220:
	Non-backoutable update units are defined in [[ File integrity and recovery#Update units and transactions\|Update units and transactions]]. </p>		Non-backoutable update units are defined in [[ File integrity and recovery#Update units and transactions\|Update units and transactions]]. </p>
	<p>		<p>
	In addition to the ~~indvidual~~ <var>FRCVOPT</var> and <var>FOPT</var> parameter description pages, see the discussion of <var>[[File integrity and recovery#frcvAndFOpts\|FRCVOPT and FOPT]]</var> as used in file integrity and recovery. </p>		In addition to the individual <var>FRCVOPT</var> and <var>FOPT</var> parameter description pages, see the discussion of <var>[[File integrity and recovery#frcvAndFOpts\|FRCVOPT and FOPT]]</var> as used in file integrity and recovery. </p>

	==Completed transactions==		==Completed transactions==

ELowell: /* Turning off transaction back out */

2019-02-19T17:31:57Z

Turning off transaction back out

← Older revision		Revision as of 17:31, 19 February 2019
Line 220:		Line 220:
	Non-backoutable update units are defined in [[ File integrity and recovery#Update units and transactions\|Update units and transactions]]. </p>		Non-backoutable update units are defined in [[ File integrity and recovery#Update units and transactions\|Update units and transactions]]. </p>
	<p>		<p>
	in addition to ~~their~~ indvidual parameter description pages, see the discussion of ~~the~~ <var>[[File integrity and recovery#frcvAndFOpts\|FRCVOPT and FOPT]]</var> ~~parameters~~. </p>		In addition to the indvidual <var>FRCVOPT</var> and <var>FOPT</var> parameter description pages, see the discussion of <var>[[File integrity and recovery#frcvAndFOpts\|FRCVOPT and FOPT]]</var> as used in file integrity and recovery. </p>

	==Completed transactions==		==Completed transactions==

Dme: /* Turning off transaction back out */

2019-02-17T17:40:41Z

Turning off transaction back out

← Older revision		Revision as of 17:40, 17 February 2019
Line 220:		Line 220:
	Non-backoutable update units are defined in [[ File integrity and recovery#Update units and transactions\|Update units and transactions]]. </p>		Non-backoutable update units are defined in [[ File integrity and recovery#Update units and transactions\|Update units and transactions]]. </p>
	<p>		<p>
	in addition to ~~hteir invidual~~ description pages, the <var>~~FRCVOPT</var> and <var>FOPT</var> parameters are discussed in greater detail in~~		in addition to their indvidual parameter description pages, see the discussion of the <var>[[File integrity and recovery#frcvAndFOpts\|FRCVOPT and FOPT]]</var> parameters. </p>
	[[File integrity and recovery#~~FRCVOPT and FOPT parameters~~\|FRCVOPT and FOPT ~~parameters~~]]. </p>

	==Completed transactions==		==Completed transactions==

JAL: mention acronym TBO

2018-01-29T17:26:33Z

mention acronym TBO

← Older revision		Revision as of 17:26, 29 January 2018
Line 3:		Line 3:
	==Overview==		==Overview==
	<p>		<p>
	Transaction back out is a file integrity facility that can logically undo the effects of incomplete transactions on file data. This logical inversion of a transaction is called a back out. Back outs can be initiated for incomplete transactions either by an application or by <var class="product">Model 204</var>. <var class="product">Model 204</var> automatically backs out an incomplete transaction for a transaction back out file if a user's request is canceled, if <var class="product">Model 204</var> detects a file problem, such as a table full condition, or if <var class="product">Model 204</var> is restarting the user. Transaction back out is the default file designation. </p>		Transaction back out is a file integrity facility that can logically undo the effects of incomplete transactions on file data. This logical inversion of a transaction is called a back out. </p>
	<p>		<p>
	This page describes the components of the ~~Transaction~~ back out facility and how it works, its effects on a file and on file recovery, and some factors to consider when choosing whether to implement transaction back out for a file.</p>		Back outs can be initiated for incomplete transactions by an application or by <var class="product">Model 204</var>. <var class="product">Model 204</var> automatically backs out an incomplete transaction for a transaction back out (TBO) file if a user's request is canceled, if <var class="product">Model 204</var> detects a file problem, such as a table full condition, or if <var class="product">Model 204</var> is restarting the user. Transaction back out is the default file designation. </p>
			<p>
			This page describes the components of the transaction back out facility and how it works, its effects on a file and on file recovery, and some factors to consider when choosing whether to implement transaction back out for a file.</p>

	===Components of the transaction back out facility===		===Components of the transaction back out facility===
Line 431:		Line 433:
	===<b id="tboAndNon"></b>Updates to TBO and non-TBO files in the same request===		===<b id="tboAndNon"></b>Updates to TBO and non-TBO files in the same request===
	<p>		<p>
	You can update a non-TBO file, commit it, and then update a TBO file-or reverse file order-in the same request.</p>		You can update a non-TBO file, commit it, and then update a TBO file — or reverse file order — in the same request.</p>
	<p>		<p>
	Requests that attempt to update TBO and non-TBO files without an intervening COMMIT statement will compile, but will fail during evaluation with the following message:</p>		Requests that attempt to update TBO and non-TBO files without an intervening COMMIT statement will compile, but they will fail during evaluation with the following message:</p>
	<p class="code"><b></b>*** 1 Cancelling request; M204.2771: Attempt to update TBO and non-TBO files in the same transaction </p>		<p class="code"><b></b>*** 1 Cancelling request;
			M204.2771: Attempt to update TBO and non-TBO files in the same transaction </p>

	<p class="note"><b>Note:</b> If you need to store temporary application data, ~~you might~~ consider defining a class and using a SOUL [[Collections\|collection]]. </p>		<p class="note"><b>Note:</b> If you need to store temporary application data, consider defining a class and using a SOUL [[Collections\|collection]]. </p>

	</div> <!-- end of toclimit div -->		</div> <!-- end of toclimit div -->

	[[Category:Model 204 files]]		[[Category:Model 204 files]]

JAL: typo

2017-11-27T23:15:00Z

typo

← Older revision		Revision as of 23:15, 27 November 2017
Line 434:		Line 434:
	<p>		<p>
	Requests that attempt to update TBO and non-TBO files without an intervening COMMIT statement will compile, but will fail during evaluation with the following message:</p>		Requests that attempt to update TBO and non-TBO files without an intervening COMMIT statement will compile, but will fail during evaluation with the following message:</p>
	<p class="code"><b></b>*** 1 Cancelling request; M204.2771: Attempt to update TBO and non-TBO files in the same transaction		<p class="code"><b></b>*** 1 Cancelling request; M204.2771: Attempt to update TBO and non-TBO files in the same transaction </p>
	</p>

	<p class="note"><b>Note:</b> If you need to store temporary application data, you might consider defining a class and using a SOUL ~~<var>~~[[Collections\|collection]].		<p class="note"><b>Note:</b> If you need to store temporary application data, you might consider defining a class and using a SOUL [[Collections\|collection]]. </p>

	</div> <!-- end of toclimit div -->		</div> <!-- end of toclimit div -->

	[[Category:Model 204 files]]		[[Category:Model 204 files]]

Dme: /* Updates to TBO and non-TBO files in the same request */

2017-11-23T17:08:04Z

Updates to TBO and non-TBO files in the same request

← Older revision		Revision as of 17:08, 23 November 2017
Line 436:		Line 436:
	<p class="code"><b></b>*** 1 Cancelling request; M204.2771: Attempt to update TBO and non-TBO files in the same transaction		<p class="code"><b></b>*** 1 Cancelling request; M204.2771: Attempt to update TBO and non-TBO files in the same transaction
	</p>		</p>

			<p class="note"><b>Note:</b> If you need to store temporary application data, you might consider defining a class and using a SOUL <var>[[Collections\|collection]].

	</div> <!-- end of toclimit div -->		</div> <!-- end of toclimit div -->

	[[Category:Model 204 files]]		[[Category:Model 204 files]]

Dme: /* Updates to TBO and non-TBO files in the same request */

2017-11-23T14:48:56Z

Updates to TBO and non-TBO files in the same request

← Older revision		Revision as of 14:48, 23 November 2017
Line 429:		Line 429:
	A transaction back out file has many advantages, but the feature must be used carefully to obtain the benefits of these advantages. The key point is not to abuse the application's privilege of defining the number of operations in a transaction. If possible, ensure that transactions do not include many updates to a file or span terminal I/O points in the application. </p>		A transaction back out file has many advantages, but the feature must be used carefully to obtain the benefits of these advantages. The key point is not to abuse the application's privilege of defining the number of operations in a transaction. If possible, ensure that transactions do not include many updates to a file or span terminal I/O points in the application. </p>

	===Updates to TBO and non-TBO files in the same request===		===<b id="tboAndNon"></b>Updates to TBO and non-TBO files in the same request===
	<p>		<p>
	You can update a non-TBO file, commit it, and then update a TBO file-or reverse file order-in the same request.</p>		You can update a non-TBO file, commit it, and then update a TBO file-or reverse file order-in the same request.</p>

Dme: /* Updates to TBO and non-TBO files in the same request */

2017-11-23T14:47:28Z

Updates to TBO and non-TBO files in the same request

← Older revision		Revision as of 14:47, 23 November 2017
Line 434:		Line 434:
	<p>		<p>
	Requests that attempt to update TBO and non-TBO files without an intervening COMMIT statement will compile, but will fail during evaluation with the following message:</p>		Requests that attempt to update TBO and non-TBO files without an intervening COMMIT statement will compile, but will fail during evaluation with the following message:</p>
	<p class="code"><b></b>*** 1 ~~CANCELLING REQUEST~~; M204.2771: ~~ATTEMPT TO UPDATE~~ TBO ~~AND NON~~-TBO ~~FILES IN THE SAME TRANSACTION~~		<p class="code"><b></b>*** 1 Cancelling request; M204.2771: Attempt to update TBO and non-TBO files in the same transaction
	</p>		</p>

ELowell: /* Requesting back outs through the Host Language Interface */

2017-04-14T19:17:25Z

Requesting back outs through the Host Language Interface

← Older revision		Revision as of 19:17, 14 April 2017
Line 135:		Line 135:
	====Requesting back outs through the Host Language Interface====		====Requesting back outs through the Host Language Interface====
	<p>		<p>
	A Host Language Interface application can back out an incomplete transaction using the <var>IFBOUT~~</var>~~ function~~. See the <var class="book">[[Media:M204 HLIReference V75.pdf~~\|~~Rocket Model 204 Host Language Interface Reference Manual~~]]</var> ~~for complete details~~.</p>		A Host Language Interface application can back out an incomplete transaction using the <var>[[IFBOUT (HLI function)\|IFBOUT]]</var> function.</p>

	===Automatic back outs===		===Automatic back outs===
	<p>		<p>

ELowell: /* Requesting back outs in SOUL */

2017-04-14T19:15:15Z

Requesting back outs in SOUL

← Older revision		Revision as of 19:15, 14 April 2017
Line 131:		Line 131:
	see [[Data recovery#Manual backout\|Manual backout]]. </p>		see [[Data recovery#Manual backout\|Manual backout]]. </p>
	<p>		<p>
	For information about using <var>BACKOUT</var> with remote files for PQO sites, see ~~the~~		For information about using <var>BACKOUT</var> with remote files for PQO sites, see [[PQO: Remote files and scattered groups]].</p>
	~~<var class="book">Parallel Query Option/204 User's Guide</var>~~.</p>

	====Requesting back outs through the Host Language Interface====		====Requesting back outs through the Host Language Interface====
	<p>		<p>