IFBOUT (HLI function) - Revision history

ELowell at 22:04, 12 July 2016

2016-07-12T22:04:32Z

← Older revision		Revision as of 22:04, 12 July 2016
Line 1:		Line 1:
	The conventions used on this page are described in [[HLI: Function ~~call list~~#Function call notation conventions\|Function call notation conventions]].		The conventions used on this page are described in [[HLI: Function summary#Function call notation conventions\|Function call notation conventions]].

	==Summary==		==Summary==

2016-07-11T21:03:31Z

← Older revision		Revision as of 21:03, 11 July 2016
Line 1:		Line 1:
			The conventions used on this page are described in [[HLI: Function call list#Function call notation conventions\|Function call notation conventions]].

	==Summary==		==Summary==
	<dl>		<dl>

2016-07-06T20:11:02Z

← Older revision		Revision as of 20:11, 6 July 2016
Line 1:		Line 1:
	==Summary==		==Summary==
	<dl>		<dl>
	<dt>Description		<dt>Description</dt>
	<dd>The IFBOUT call (BACK OUT) backs out an incomplete transaction on the thread or threads that are active for the transaction in which the thread participates.		<dd>The IFBOUT call (BACK OUT) backs out an incomplete transaction on the thread or threads that are active for the transaction in which the thread participates.</dd>
	<dt>Thread type		<dt>Thread type</dt>
	<dd>multiple cursor IFSTRT, single cursor IFSTRT		<dd>multiple cursor IFSTRT, single cursor IFSTRT</dd>
	<dt>IFCALL function number		<dt>IFCALL function number</dt>
	<dd>71		<dd>71</dd>
	</dl>		</dl>

Line 13:		Line 13:

	<dl>		<dl>
	<dt>Compile-only form		<dt>Compile-only form</dt>
	<dd>Not available		<dd>Not available</dd>
	<dt>Execute-only form		<dt>Execute-only form</dt>
	<dd>Not available		<dd>Not available</dd>
	</dl>		</dl>

2016-07-06T20:09:29Z

@@ Line 27: / Line 27: @@
 <td>RETCODE</td>
 <td>[O,i,r] The Model 204 return code is the required output parameter. The code is a binary integer value.</td>
 </tr>
 </table>
@@ Line 75: / Line 58: @@
 To ensure that all of the records and resource locks are released after the IFBOUT call executes in a multithreaded transaction, issue IFCMMT on all of the other single cursor IFSTRT threads participating in the transaction. </p>
 <p class="note"><b>Note:</b> A completed transaction cannot be backed out.</p> <p>For more information about transaction backout, see [[HLI: Transactions]].</p>
 ==Coding example (COBOL)==

2016-07-05T16:00:45Z

@@ Line 27: / Line 27: @@
 <td>RETCODE</td>
 <td>[O,i,r] The Model 204 return code is the required output parameter. The code is a binary integer value.</td>
 </tr>
 </table>
@@ Line 48: / Line 65: @@
 Single cursor IFSTRT threads that are started in a multithreaded IFAM2 or IFAM4 HLI job participate in a multithreaded transaction. See [[HLI: Transactions]] for more information about transaction processing in an HLI job. </p>
-==Completion return code (RETCODE)==
+<p>IFBOUT is not valid on a read-only type thread, that is, any thread that is started by IFSTRT with an update indicator of 0 for an IFAM2 / IFAM4 connection. </p>
 ===Record locking behavior===

2016-07-01T21:37:15Z

← Older revision		Revision as of 21:37, 1 July 2016
Line 1:		Line 1:
			==Summary==
	==~~Function~~==		<dl>
	<p>		<dt>Description
	The IFBOUT call (BACK OUT) backs out an incomplete transaction on the thread or threads that are active for the transaction in which the thread participates.</p>		<dd>The IFBOUT call (BACK OUT) backs out an incomplete transaction on the thread or threads that are active for the transaction in which the thread participates.
			<dt>Thread type
	==Thread type==		<dd>multiple cursor IFSTRT, single cursor IFSTRT
	multiple cursor IFSTRT, single cursor IFSTRT		<dt>IFCALL function number
			<dd>71
			</dl>

	==Syntax==		==Syntax==
	~~===Full syntax (71)===~~
	<p class="syntax">IFBOUT(RETCODE)</p>		<p class="syntax">IFBOUT(RETCODE)</p>

	~~===~~Compile-only ~~syntax===~~		<dl>
	<p>		<dt>Compile-only form
	~~A compile-only form of IFBOUT is not available.~~</p>		<dd>Not available
			<dt>Execute-only form
	~~===~~Execute-only ~~syntax===~~		<dd>Not available
	<p>		</dl>
	~~An execute-only form of IFBOUT is not available.~~</p>

	~~===Parameters===~~
	<table>		<table>
	<tr class="head">		<tr class="head">
Line 31:		Line 30:
	</table>		</table>

	==~~Notes and tips~~==		==Usage notes==
	<p>		<p>
	Use the IFBOUT call to activate the Model 204 backout mechanism. The backout function is valid only for transaction backout (TBO) files. </p>		Use the IFBOUT call to activate the Model 204 backout mechanism. The backout function is valid only for transaction backout (TBO) files. </p>

2016-07-01T20:44:09Z

2016-05-09T16:30:48Z

link repair

← Older revision		Revision as of 16:30, 9 May 2016
Line 47:		Line 47:
	</ul>		</ul>
	<p>		<p>
	Single cursor IFSTRT threads that are started in a multithreaded IFAM2 or IFAM4 HLI job participate in a multithreaded transaction. See [[HLI: ~~Transaction processing and recovery~~]] for more information about transaction processing in an HLI job. </p>		Single cursor IFSTRT threads that are started in a multithreaded IFAM2 or IFAM4 HLI job participate in a multithreaded transaction. See [[HLI: Transactions]] for more information about transaction processing in an HLI job. </p>

	==Completion return code (RETCODE)==		==Completion return code (RETCODE)==

2016-05-04T00:16:36Z

Admin moved page IFBOUT (HLI function call) to IFBOUT (HLI function): remove "function call" terminology; keep "function"

← Older revision	Revision as of 00:16, 4 May 2016
(No difference)

2016-05-03T21:29:50Z

ELowell moved page HLI: IFBOUT call to IFBOUT (HLI function call): better searchability; consistency with existing topic names

← Older revision	Revision as of 21:29, 3 May 2016
(No difference)