File integrity and recovery - Revision history

ELowell at 00:24, 1 January 2020

2020-01-01T00:24:58Z

← Older revision		Revision as of 00:24, 1 January 2020
Line 564:		Line 564:
	</tr>		</tr>
	</table>		</table>

			For information about the commit exits feature, which enables you to set up SOUL code to run at commit time, see [[Application_Subsystem_development#Commit_exits\|Application Subsystem development]].

	====Other ways to end active update units====		====Other ways to end active update units====
Line 694:		Line 696:
	In User Language, ending a transaction does not start a new transaction. A new transaction does not start until a User Language statement performs an update operation on a transaction back out file. </p>		In User Language, ending a transaction does not start a new transaction. A new transaction does not start until a User Language statement performs an update operation on a transaction back out file. </p>

	~~===Commit exits===~~
	~~For information about the commit exits feature, which enables you to set up SOUL code to run at commit time, see [[Application_Subsystem_development#Commit_exits\|Application Subsystem development]].~~
	===Host Language Interface update units===		===Host Language Interface update units===
	<p>		<p>

ELowell: /* Host Language Interface update units */

2020-01-01T00:20:59Z

Host Language Interface update units

← Older revision		Revision as of 00:20, 1 January 2020
Line 694:		Line 694:
	In User Language, ending a transaction does not start a new transaction. A new transaction does not start until a User Language statement performs an update operation on a transaction back out file. </p>		In User Language, ending a transaction does not start a new transaction. A new transaction does not start until a User Language statement performs an update operation on a transaction back out file. </p>

			===Commit exits===
			For information about the commit exits feature, which enables you to set up SOUL code to run at commit time, see [[Application_Subsystem_development#Commit_exits\|Application Subsystem development]].
	===Host Language Interface update units===		===Host Language Interface update units===
	<p>		<p>

Dme: /* FRCVOPT and FOPT parameters */

2019-02-17T19:21:43Z

FRCVOPT and FOPT parameters

← Older revision		Revision as of 19:21, 17 February 2019
Line 36:		Line 36:
	The <var>[[REGENERATE command\|REGENERATE]]</var> command invokes the Restore and Roll Forward facilities automatically. In a media recovery run, the RESTORE and RESTART commands are not specified. </p>		The <var>[[REGENERATE command\|REGENERATE]]</var> command invokes the Restore and Roll Forward facilities automatically. In a media recovery run, the RESTORE and RESTART commands are not specified. </p>

	==<b id="frcvAndFOpts~~"></b><b id="FRCVOPT parameter~~"></b>FRCVOPT and FOPT parameters==		==<b id="frcvAndFOpts"></b>FRCVOPT and FOPT parameters==
	<p>		<p>
	The <var>[[FRCVOPT parameter\|FRCVOPT]]</var> (file recovery options) parameter determines whether or not an installation logs checkpoint and/or Roll Forward information. The system manager also must include the <var>[[RESTART command\|RESTART]]</var> command in a <var class="product">Model 204</var> job in order for recovery to run. If an installation uses the system recovery facilities, the file manager can control how files are affected. </p>		The <var>[[FRCVOPT parameter\|FRCVOPT]]</var> (file recovery options) parameter determines whether or not an installation logs checkpoint and/or Roll Forward information. The system manager also must include the <var>[[RESTART command\|RESTART]]</var> command in a <var class="product">Model 204</var> job in order for recovery to run. If an installation uses the system recovery facilities, the file manager can control how files are affected. </p>

Dme: /* FRCVOPT and FOPT parameters */

2019-02-17T17:40:23Z

FRCVOPT and FOPT parameters

← Older revision		Revision as of 17:40, 17 February 2019
Line 36:		Line 36:
	The <var>[[REGENERATE command\|REGENERATE]]</var> command invokes the Restore and Roll Forward facilities automatically. In a media recovery run, the RESTORE and RESTART commands are not specified. </p>		The <var>[[REGENERATE command\|REGENERATE]]</var> command invokes the Restore and Roll Forward facilities automatically. In a media recovery run, the RESTORE and RESTART commands are not specified. </p>

	==<b id="frcvAndFOpts"</b><b id="FRCVOPT parameter"></b>FRCVOPT and FOPT parameters==		==<b id="frcvAndFOpts"></b><b id="FRCVOPT parameter"></b>FRCVOPT and FOPT parameters==
	<p>		<p>
	The <var>[[FRCVOPT parameter\|FRCVOPT]]</var> (file recovery options) parameter determines whether or not an installation logs checkpoint and/or Roll Forward information. The system manager also must include the <var>[[RESTART command\|RESTART]]</var> command in a <var class="product">Model 204</var> job in order for recovery to run. If an installation uses the system recovery facilities, the file manager can control how files are affected. </p>		The <var>[[FRCVOPT parameter\|FRCVOPT]]</var> (file recovery options) parameter determines whether or not an installation logs checkpoint and/or Roll Forward information. The system manager also must include the <var>[[RESTART command\|RESTART]]</var> command in a <var class="product">Model 204</var> job in order for recovery to run. If an installation uses the system recovery facilities, the file manager can control how files are affected. </p>

Dme: /* FRCVOPT parameter */

2019-02-17T17:36:09Z

FRCVOPT parameter

← Older revision		Revision as of 17:36, 17 February 2019
Line 36:		Line 36:
	The <var>[[REGENERATE command\|REGENERATE]]</var> command invokes the Restore and Roll Forward facilities automatically. In a media recovery run, the RESTORE and RESTART commands are not specified. </p>		The <var>[[REGENERATE command\|REGENERATE]]</var> command invokes the Restore and Roll Forward facilities automatically. In a media recovery run, the RESTORE and RESTART commands are not specified. </p>

	==FRCVOPT parameter==		==<b id="frcvAndFOpts"</b><b id="FRCVOPT parameter"></b>FRCVOPT and FOPT parameters==
	<p>		<p>
	The <var>[[FRCVOPT parameter\|FRCVOPT]]</var> (file recovery options) parameter determines whether or not an installation logs checkpoint and/or Roll Forward information. The system manager also must include the <var>[[RESTART command\|RESTART]]</var> command in a <var class="product">Model 204</var> job in order for recovery to run. If an installation uses the system recovery facilities, the file manager can control how files are affected. </p>		The <var>[[FRCVOPT parameter\|FRCVOPT]]</var> (file recovery options) parameter determines whether or not an installation logs checkpoint and/or Roll Forward information. The system manager also must include the <var>[[RESTART command\|RESTART]]</var> command in a <var class="product">Model 204</var> job in order for recovery to run. If an installation uses the system recovery facilities, the file manager can control how files are affected. </p>
Line 111:		Line 111:
	<p>		<p>
	In case of failure, <var class="product">Model 204</var> makes every effort to clean up files and shut down softly. If <var class="product">Model 204</var> or the operating system under which it is running crashes, any <var class="product">Model 204</var> file being updated is flagged by a special setting of the <var>[[FISTAT parameter\|FISTAT]]</var> parameter. The FILE PHYSICALLY INCONSISTENT message is issued whenever the file is opened thereafter until recovery procedures have been executed. In this case, or in the case of a hard crash, integrity can be recovered using the DUMP/RESTORE utility or restart/recovery facility. </p>		In case of failure, <var class="product">Model 204</var> makes every effort to clean up files and shut down softly. If <var class="product">Model 204</var> or the operating system under which it is running crashes, any <var class="product">Model 204</var> file being updated is flagged by a special setting of the <var>[[FISTAT parameter\|FISTAT]]</var> parameter. The FILE PHYSICALLY INCONSISTENT message is issued whenever the file is opened thereafter until recovery procedures have been executed. In this case, or in the case of a hard crash, integrity can be recovered using the DUMP/RESTORE utility or restart/recovery facility. </p>

	==FISTAT parameter==		==FISTAT parameter==
	<p>		<p>

JAL: link repair

2018-04-27T18:21:45Z

link repair

← Older revision		Revision as of 18:21, 27 April 2018
Line 325:		Line 325:
	Retrieval-only Host Language Interface threads are not included in update units. Passing data from a retrieval-only thread to an update thread can result in logical inconsistencies to the updated file during Roll Forward.		Retrieval-only Host Language Interface threads are not included in update units. Passing data from a retrieval-only thread to an update thread can result in logical inconsistencies to the updated file during Roll Forward.
	To prevent these inconsistencies, start the thread as an update thread and use a retrieval-only password to open the file, thus providing share-mode enqueuing and preventing updating from this thread.		To prevent these inconsistencies, start the thread as an update thread and use a retrieval-only password to open the file, thus providing share-mode enqueuing and preventing updating from this thread.
	The file also is prevented from being marked physically inconsistent in the event of a hard restart or system crash. See [[/HLI: Job design factors#Recovery considerations for single and multicursor IFAM2 threads\|Recovery considerations for single and multicursor IFAM2 threads]] for further description.</p>		The file also is prevented from being marked physically inconsistent in the event of a hard restart or system crash. See [[HLI: Job design factors#Recovery considerations for single and multicursor IFAM2 threads\|Recovery considerations for single and multicursor IFAM2 threads]] for further description.</p>

	==Update units and transactions==		==Update units and transactions==

JAL: /* Designing Host Language Interface jobs */ add link

2017-11-29T22:03:28Z

Designing Host Language Interface jobs: add link

← Older revision		Revision as of 22:03, 29 November 2017
Line 321:		Line 321:
	===Designing Host Language Interface jobs===		===Designing Host Language Interface jobs===
	<p>		<p>
	For Host Language Interface jobs, set the update indicator in the IFSTRT function only when updating is really occurring, and issue the IFCHKPT call at various points during a long updating program. </p>		For Host Language Interface jobs, set the update indicator in the IFSTRT function only when updating is really occurring, and issue the IFCHKPT call at various points during a long updating program. </p>
	<p>		<p>
	Retrieval-only Host Language Interface threads are not included in update units. Passing data from a retrieval-only thread to an update thread can result in logical inconsistencies to the updated file during Roll Forward.		Retrieval-only Host Language Interface threads are not included in update units. Passing data from a retrieval-only thread to an update thread can result in logical inconsistencies to the updated file during Roll Forward.
	To prevent these inconsistencies, start the thread as an update thread and use a retrieval-only password to open the file, thus providing share-mode enqueuing and preventing updating from this thread.		To prevent these inconsistencies, start the thread as an update thread and use a retrieval-only password to open the file, thus providing share-mode enqueuing and preventing updating from this thread.
	The file also is prevented from being marked physically inconsistent in the event of a hard restart or system crash. See ~~the<var class="book">Model 204 Host Language Interface Reference Manual<~~/~~var>~~ for further description.</p>		The file also is prevented from being marked physically inconsistent in the event of a hard restart or system crash. See [[/HLI: Job design factors#Recovery considerations for single and multicursor IFAM2 threads\|Recovery considerations for single and multicursor IFAM2 threads]] for further description.</p>

	==Update units and transactions==		==Update units and transactions==

ELowell at 16:09, 27 October 2017

2017-10-27T16:09:52Z

← Older revision		Revision as of 16:09, 27 October 2017
Line 176:		Line 176:
	<li>Phone is hung up</li>		<li>Phone is hung up</li>

	<li>No input is coming in on a thread (with the inactive thread timeout feature enabled) for a specified number of seconds. ~~Ssee~~ [[Defining the user environment (CCAIN)#User environment control parameters\|User environment control parameters]] for information on the TIMEOUT parameter.</li>		<li>No input is coming in on a thread (with the inactive thread timeout feature enabled) for a specified number of seconds. See [[Defining the user environment (CCAIN)#User environment control parameters\|User environment control parameters]] for information on the TIMEOUT parameter.</li>

	<li>Full server tables</li>		<li>Full server tables</li>

Admin: link repair

2017-07-25T23:00:57Z

link repair

← Older revision		Revision as of 23:00, 25 July 2017
Line 460:		Line 460:
	<table>		<table>
	<tr>		<tr>
	<td><var>[[SECURE ~~FILE~~ command\|SECURE ~~FILE~~]]</var></td>		<td><var>[[SECURE command: File\|SECURE]]</var></td>
	</tr>		</tr>

ELowell at 22:21, 28 September 2016

2016-09-28T22:21:59Z

← Older revision		Revision as of 22:21, 28 September 2016
Line 701:		Line 701:

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