REGENERATE ONEPASS command - Revision history

ELowell: /* Usage notes */

2014-02-12T20:14:20Z

Usage notes

@@ Line 96: / Line 96: @@
 <p>When processing REGENERATE ONEPASS, <var class="product">Model&nbsp;204</var> ends any update unit in progress and begins an update unit that cannot be backed out. For more information about <var class="product">Model&nbsp;204</var> update units, see [[File_integrity_and_recovery#Update_units_and_transactions|Update units and transactions]].</p>
 <p>For a single-user (batch) <var class="product">Model&nbsp;204</var> run, specify a REGENERATE ONEPASS command on User 0's command line. REGENERATE ONEPASS need not be the first command issued. User Language procedures and other batch functions can be intermixed with REGENERATE ONEPASS commands.</p>
 [[Category:Commands]]

ELowell: /* Usage notes */

2014-02-12T17:56:48Z

Usage notes

← Older revision		Revision as of 17:56, 12 February 2014
Line 88:		Line 88:

	==Usage notes==		==Usage notes==
	<p class="note"><b>Note:</b> The TO clause options for a REGENERATE ONEPASS command are restricted in scope when compared to the REGENERATE command, because no stopping point is known without reading the entire CCAGEN data set. (See the [[REGENERATE command]].)</p>		<p class="note"><b>Note:</b> The TO clause options for a REGENERATE ONEPASS command are restricted in scope when compared to the REGENERATE command, because no stopping point is known without reading the entire CCAGEN data set. (See the <var>[[REGENERATE command\|REGENERATE]]</var> command.)</p>
	<p>An incorrect TO clause generates the following error message.</p>		<p>An incorrect TO clause generates the following error message.</p>
	<p class="code">M204.1410: REGENERATE COMMAND REJECTED		<p class="code">M204.1410: REGENERATE COMMAND REJECTED
Line 94:		Line 94:
	<p>The algorithm for identifying starting points, used whether or not a FROM clause is present, is to find the start of the first update unit with a time greater than the last updated time of the file being processed. </p>		<p>The algorithm for identifying starting points, used whether or not a FROM clause is present, is to find the start of the first update unit with a time greater than the last updated time of the file being processed. </p>
	<p>If REGENERATE ONEPASS processing opens a file for which it is <i>not</i> performing a restore, and if that file is marked physically inconsistent, REGENERATE ONEPASS processing for that file is discontinued.</p>		<p>If REGENERATE ONEPASS processing opens a file for which it is <i>not</i> performing a restore, and if that file is marked physically inconsistent, REGENERATE ONEPASS processing for that file is discontinued.</p>
	<p>When processing REGENERATE ONEPASS, <var class="product">Model 204</var> ends any update unit in progress and begins an update unit that cannot be backed out. For more information about <var class="product">Model 204</var> update units, see ~~the <var class="book">Model 204 File Manager's Guide</var>~~.</p>		<p>When processing REGENERATE ONEPASS, <var class="product">Model 204</var> ends any update unit in progress and begins an update unit that cannot be backed out. For more information about <var class="product">Model 204</var> update units, see [[File_integrity_and_recovery#Update_units_and_transactions\|Update units and transactions]].</p>
	<p>For a single-user (batch) <var class="product">Model 204</var> run, specify a REGENERATE ONEPASS command on User 0's command line. REGENERATE ONEPASS need not be the first command issued. User Language procedures and other batch functions can be intermixed with REGENERATE ONEPASS commands.</p>		<p>For a single-user (batch) <var class="product">Model 204</var> run, specify a REGENERATE ONEPASS command on User 0's command line. REGENERATE ONEPASS need not be the first command issued. User Language procedures and other batch functions can be intermixed with REGENERATE ONEPASS commands.</p>
	[[Category:Commands]]		[[Category:Commands]]

ELowell: /* Syntax */

2014-02-12T17:49:37Z

Syntax

← Older revision		Revision as of 17:49, 12 February 2014
Line 16:		Line 16:

	<b>Where:</b>		<b>Where:</b>
	REGENERATE ONEPASS processing runs only Pass One through the CCAGEN data set. If you must regenerate across a recovery process, two passes of the journal are required. You must build [[REGENERATE command \| REGENERATE]] commands, not REGENERATE ONEPASS commands, which are invalid.		REGENERATE ONEPASS processing runs only Pass One through the CCAGEN data set.
			<p>REGENERATE ONEPASS is significantly faster than REGENERATE but cannot be used across recovery runs or discontinuities (such as file create or delete).</p>
			<p>If you must regenerate across a recovery process, two passes of the journal are required. You must build <var>[[REGENERATE command \| REGENERATE]]</var> commands, not REGENERATE ONEPASS commands, which are invalid.</p>
	<ul>		<ul>
	<li>		<li>

ELowell: /* Usage notes */

2013-10-17T16:18:24Z

Usage notes

← Older revision		Revision as of 16:18, 17 October 2013
Line 86:		Line 86:

	==Usage notes==		==Usage notes==
	<p class="note"><b>Note:</b> The TO clause options for a REGENERATE ONEPASS command are restricted in scope when compared to the REGENERATE command, because no stopping point is known without reading the entire CCAGEN data set. (See [[REGENERATE command~~\|REGENERATE: Recovering a file in two passes~~]].)</p>		<p class="note"><b>Note:</b> The TO clause options for a REGENERATE ONEPASS command are restricted in scope when compared to the REGENERATE command, because no stopping point is known without reading the entire CCAGEN data set. (See the [[REGENERATE command]].)</p>
	<p>An incorrect TO clause generates the following error message.</p>		<p>An incorrect TO clause generates the following error message.</p>
	<p class="code">M204.1410: REGENERATE COMMAND REJECTED		<p class="code">M204.1410: REGENERATE COMMAND REJECTED

ELowell: /* Syntax */

2013-10-17T15:53:55Z

Syntax

← Older revision		Revision as of 15:53, 17 October 2013
Line 16:		Line 16:

	<b>Where:</b>		<b>Where:</b>
	REGENERATE ONEPASS processing ~~executes~~ only Pass One through the CCAGEN data set. If you must regenerate across a recovery process, two passes of the journal are required. You must build REGENERATE commands, not REGENERATE ONEPASS commands, which are invalid~~. See [[REGENERATE command\|"REGENERATE: Recovering a file in two passes"]]~~.		REGENERATE ONEPASS processing runs only Pass One through the CCAGEN data set. If you must regenerate across a recovery process, two passes of the journal are required. You must build [[REGENERATE command \| REGENERATE]] commands, not REGENERATE ONEPASS commands, which are invalid.
	<ul>		<ul>
	<li>		<li>

ELowell: /* Summary */

2013-10-17T15:51:46Z

Summary

← Older revision		Revision as of 15:51, 17 October 2013
Line 4:		Line 4:
	<dd>User 0		<dd>User 0
	<dt>Function		<dt>Function
	<dd>In the event of a media failure, for example, a disk head crash, a REGENERATE ONEPASS command recovers a <var class="product">Model 204</var> file by reapplying some or all of the updates that have been made to the file since the ~~time of the last~~ dump.		<dd>In the event of a media failure, for example, a disk head crash, a REGENERATE ONEPASS command recovers a <var class="product">Model 204</var> file by reapplying some or all of the updates that have been made to the file since the previous dump.
	</dl>		</dl>

	==Syntax==		==Syntax==
	<p class="syntax"><b>REGEN</b>ERATE <b>ONEPASS</b> FILE <i>filename</i> [FROM <span class="term">dumpname</span>]		<p class="syntax"><b>REGEN</b>ERATE <b>ONEPASS</b> FILE <i>filename</i> [FROM <span class="term">dumpname</span>]

JDamon: /* Examples */ Added the OF clause TO UPDATE n examples. Changed all examples to year 13

2013-08-06T15:31:31Z

Examples: Added the OF clause TO UPDATE n examples. Changed all examples to year 13

← Older revision		Revision as of 15:31, 6 August 2013
Line 73:		Line 73:
	<p class="code">REGENERATE ONEPASS FILE DB1 FROM DUMPDB1		<p class="code">REGENERATE ONEPASS FILE DB1 FROM DUMPDB1
	REGEN ONEPASS FILE DB1 FROM DUMPDB1 TO LAST UPDATE		REGEN ONEPASS FILE DB1 FROM DUMPDB1 TO LAST UPDATE
	REGEN ONEPASS FILE DB1 FROM DUMPDB2 TO UPDATE 3		REGEN ONEPASS FILE DB1 FROM DUMPDB2 TO UPDATE 3 OF 13.116 10:15:25.00
	REGEN ONEPASS FILE MODFILE FROM DUMPMOD TO -		REGEN ONEPASS FILE MODFILE FROM DUMPMOD TO -
	CHECKPOINT 02.~~216~~ 01:05:22.99		CHECKPOINT 13.116 01:05:22.99
	REGEN ONEPASS		REGEN ONEPASS
	FILE DB1 FROM DUMPDB1 TO CHECKPOINT -		FILE DB1 FROM DUMPDB1 TO CHECKPOINT -
	02.~~241~~ 11:44:30.15		13.116 11:44:30.15
	FILE DB2 FROM DUMPDB2		FILE DB2 FROM DUMPDB2
	FILE DB3 FROM DUMPDB3 TO UPDATE 5		FILE DB3 FROM DUMPDB3 TO UPDATE 5 OF 13.116 14:32:22.00
	END		END
	</p>		</p>

	==Usage notes==		==Usage notes==
	<p class="note"><b>Note:</b> The TO clause options for a REGENERATE ONEPASS command are restricted in scope when compared to the REGENERATE command, because no stopping point is known without reading the entire CCAGEN data set. (See [[REGENERATE command\|REGENERATE: Recovering a file in two passes]].)</p>		<p class="note"><b>Note:</b> The TO clause options for a REGENERATE ONEPASS command are restricted in scope when compared to the REGENERATE command, because no stopping point is known without reading the entire CCAGEN data set. (See [[REGENERATE command\|REGENERATE: Recovering a file in two passes]].)</p>

ELowell: /* Syntax */

2013-08-05T18:07:20Z

Syntax

← Older revision		Revision as of 18:07, 5 August 2013
Line 7:		Line 7:
	</dl>		</dl>
	==Syntax==		==Syntax==
	<p class="syntax"><b>REGEN</b>ERATE <b>ONEPASS</b> FILE <i>filename</i> [FROM <i>dumpname</i>]		<p class="syntax"><b>REGEN</b>ERATE <b>ONEPASS</b> FILE <i>filename</i> [FROM <span class="term">dumpname</span>]
	[TO {<u>LAST UPDATE</u>		[TO {<u>LAST UPDATE</u>
	\| TO UPDATE <i>nn </i>OF <i>yy.ddd hh:mm:ss.th</i>		\| TO UPDATE <span class="term">nn</span> OF <span class="term">yy.ddd hh:mm:ss.th</span>
	\| TO CHECKPOINT <i>yy.ddd hh:mm:ss.th}</i>]		\| TO CHECKPOINT <span class="term">yy.ddd hh:mm:ss.th</span>}]
	</p>		</p>
	<p>For more than one file, specify REGENERATE ONEPASS only once; the remaining syntax is repeated for each file.</p>		<p>For more than one file, specify REGENERATE ONEPASS only once; the remaining syntax is repeated for each file.</p>
Line 54:		Line 54:

	<tr> <th><var>		<tr> <th><var>
	<p>~~UPDATE~~ nn</p>		UPDATE</var> <var class="term">nn</var> OF <var class="term">yy.ddd hh:mm:ss.th</var>
	</var></th> <td>And including the specified ~~update~~. </td> </tr>		</th> <td>And including the update specified by number and date-timestamp. </td> </tr>

	<tr> <th><var>		<tr> <th>
	<p>~~CHECKPOINT~~ yy.ddd hh:mm:ss.th</p>		<var>CHECKPOINT</var> <var class="term">yy.ddd hh:mm:ss.th</var>
	~~</var>~~</th> <td>		</th> <td>
	<p>Specified checkpoint with a date-timestamp.</p>		<p>Specified checkpoint with a date-timestamp.</p>
	</td> </tr>		</td> </tr>

JDamon at 17:28, 5 August 2013

2013-08-05T17:28:12Z

← Older revision		Revision as of 17:28, 5 August 2013
Line 9:		Line 9:
	<p class="syntax"><b>REGEN</b>ERATE <b>ONEPASS</b> FILE <i>filename</i> [FROM <i>dumpname</i>]		<p class="syntax"><b>REGEN</b>ERATE <b>ONEPASS</b> FILE <i>filename</i> [FROM <i>dumpname</i>]
	[TO {<u>LAST UPDATE</u>		[TO {<u>LAST UPDATE</u>
	\| TO UPDATE <i>nn OF yy.ddd hh:mm:ss.th </i>		\| TO UPDATE <i>nn </i>OF <i>yy.ddd hh:mm:ss.th</i>
	\| TO CHECKPOINT <i>yy.ddd hh:mm:ss.th}</i>]		\| TO CHECKPOINT <i>yy.ddd hh:mm:ss.th}</i>]
	</p>		</p>

JDamon: Minor change to syntax when UPDATE nn is used. Must be followed by UPDATE nn OF yy.ddd hh:mm:ss.th

2013-08-05T17:24:07Z

Minor change to syntax when UPDATE nn is used. Must be followed by UPDATE nn OF yy.ddd hh:mm:ss.th

← Older revision		Revision as of 17:24, 5 August 2013
Line 9:		Line 9:
	<p class="syntax"><b>REGEN</b>ERATE <b>ONEPASS</b> FILE <i>filename</i> [FROM <i>dumpname</i>]		<p class="syntax"><b>REGEN</b>ERATE <b>ONEPASS</b> FILE <i>filename</i> [FROM <i>dumpname</i>]
	[TO {<u>LAST UPDATE</u>		[TO {<u>LAST UPDATE</u>
	\| TO UPDATE <i>nn</i>		\| TO UPDATE <i>nn OF yy.ddd hh:mm:ss.th </i>
	\| TO CHECKPOINT <i>yy.ddd hh:mm:ss.th}</i>]		\| TO CHECKPOINT <i>yy.ddd hh:mm:ss.th}</i>]
	</p>		</p>