REGENERATE command - Revision history

Ekern: /* The USING option */

2025-01-31T23:28:30Z

The USING option

← Older revision		Revision as of 23:28, 31 January 2025
Line 127:		Line 127:

	==== The USING option====		==== The USING option====
	<p>Allows for user to specify ddname for input journal stream to be used by REGENERATE command. This is a new addition as of <var>[[https://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_Model_204_version_7.8#~~Media_Recovery_in_a_multi-user_environment~~:M204 v7.8]]</var></p>		<p>Allows for user to specify ddname for input journal stream to be used by REGENERATE command. This is a new addition as of <var>[[https://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_Model_204_version_7.8#Recovery_enhancements:M204 v7.8]]</var></p>

	====Using REGENERATE with multiple files====		====Using REGENERATE with multiple files====

Ekern: /* The USING option */

2025-01-31T23:25:53Z

The USING option

← Older revision		Revision as of 23:25, 31 January 2025
Line 127:		Line 127:

	==== The USING option====		==== The USING option====
	<p>Allows for user to specify ddname for input journal stream to be used by REGENERATE command. This is a new addition as of <var>[[https://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_Model_204_version_7.8#Media_Recovery_in_a_multi-user_environment\|M204 v7.8]]</var></p>		<p>Allows for user to specify ddname for input journal stream to be used by REGENERATE command. This is a new addition as of <var>[[https://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_Model_204_version_7.8#Media_Recovery_in_a_multi-user_environment:M204 v7.8]]</var></p>

	====Using REGENERATE with multiple files====		====Using REGENERATE with multiple files====

Ekern: /* The USING option */

2025-01-31T01:38:11Z

The USING option

← Older revision		Revision as of 01:38, 31 January 2025
Line 127:		Line 127:

	==== The USING option====		==== The USING option====
	<p>Allows for user to specify ddname for input journal stream to be used by REGENERATE command. This is a new addition as of <var>M204 v7.8</var></p>		<p>Allows for user to specify ddname for input journal stream to be used by REGENERATE command. This is a new addition as of <var>[[https://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_Model_204_version_7.8#Media_Recovery_in_a_multi-user_environment\|M204 v7.8]]</var></p>

	====Using REGENERATE with multiple files====		====Using REGENERATE with multiple files====

Ekern: /* Usage notes */

2025-01-31T01:28:32Z

Usage notes

← Older revision		Revision as of 01:28, 31 January 2025
Line 125:		Line 125:
	And this message is also displayed:		And this message is also displayed:
	<p class="code">M204.1435: Error during regenerate</p>		<p class="code">M204.1435: Error during regenerate</p>

			==== The USING option====
			<p>Allows for user to specify ddname for input journal stream to be used by REGENERATE command. This is a new addition as of <var>M204 v7.8</var></p>

	====Using REGENERATE with multiple files====		====Using REGENERATE with multiple files====

Goff: Add USING ddname

2024-11-20T20:06:18Z

Add USING ddname

← Older revision		Revision as of 20:06, 20 November 2024
Line 7:		Line 7:
	</dl>		</dl>
	==Syntax==		==Syntax==
	<p class="syntax"><b>REGEN</b>ERATE FILE <span class="term">filename</span> [FROM <span class="term">dumpname</span> \| IGNORE]		<p class="syntax"><b>REGEN</b>ERATE [USING <span class="term">ddname</span>] FILE <span class="term">filename</span> [FROM <span class="term">dumpname</span> \| IGNORE]
	[TO {<u>LAST UPDATE</u> [BEFORE <span class="term">yy.ddd hh:mm:ss.th</span>]		[TO {<u>LAST UPDATE</u> [BEFORE <span class="term">yy.ddd hh:mm:ss.th</span>]
	\| LAST CHECKPOINT [BEFORE <span class="term">yy.dd hh:mm:ss.th</span>]		\| LAST CHECKPOINT [BEFORE <span class="term">yy.dd hh:mm:ss.th</span>]
Line 17:		Line 17:
	<b>Where:</b>		<b>Where:</b>
	<ul>		<ul>
			<li>
			<p><var class="term">ddname</var> allows an alternate ddname to be used for the input journal to be used by REGENERATE. It is one to eight characters long and defaults to <span class="term">CCAGEN</span> if not specified</p>
			</li>

	<li>		<li>
	<p><var class="term">filename</var> is the name of a <var class="product">Model 204</var> file that is one to eight characters long.</p>		<p><var class="term">filename</var> is the name of a <var class="product">Model 204</var> file that is one to eight characters long.</p>

Goff: /* Syntax */

2024-08-14T23:14:19Z

Syntax

← Older revision		Revision as of 23:14, 14 August 2024
Line 7:		Line 7:
	</dl>		</dl>
	==Syntax==		==Syntax==
	<p class="syntax"><b>REGEN</b>ERATE ~~[FROM <span class="term"USING "term">ddname</span>]~~ FILE <span class="term">filename</span> [FROM <span class="term">dumpname</span> \| IGNORE]		<p class="syntax"><b>REGEN</b>ERATE FILE <span class="term">filename</span> [FROM <span class="term">dumpname</span> \| IGNORE]
	[TO {<u>LAST UPDATE</u> [BEFORE <span class="term">yy.ddd hh:mm:ss.th</span>]		[TO {<u>LAST UPDATE</u> [BEFORE <span class="term">yy.ddd hh:mm:ss.th</span>]
	\| LAST CHECKPOINT [BEFORE <span class="term">yy.dd hh:mm:ss.th</span>]		\| LAST CHECKPOINT [BEFORE <span class="term">yy.dd hh:mm:ss.th</span>]

Goff: /* Syntax */

2024-08-14T23:13:30Z

Syntax

← Older revision		Revision as of 23:13, 14 August 2024
Line 7:		Line 7:
	</dl>		</dl>
	==Syntax==		==Syntax==
	<p class="syntax"><b>REGEN</b>ERATE FILE <span class="term">filename</span> [FROM <span class="term">dumpname</span> \| IGNORE]		<p class="syntax"><b>REGEN</b>ERATE [FROM <span class="term"USING "term">ddname</span>] FILE <span class="term">filename</span> [FROM <span class="term">dumpname</span> \| IGNORE]
	[TO {<u>LAST UPDATE</u> [BEFORE <span class="term">yy.ddd hh:mm:ss.th</span>]		[TO {<u>LAST UPDATE</u> [BEFORE <span class="term">yy.ddd hh:mm:ss.th</span>]
	\| LAST CHECKPOINT [BEFORE <span class="term">yy.dd hh:mm:ss.th</span>]		\| LAST CHECKPOINT [BEFORE <span class="term">yy.dd hh:mm:ss.th</span>]

JAL: /* Syntax */

2014-03-07T23:19:16Z

Syntax

← Older revision		Revision as of 23:19, 7 March 2014
Line 46:		Line 46:
	<table>		<table>

	<tr> <th>		<tr class="head"> <th>
	<p>Option</p>		<p>Option</p>
	</th> <th>		</th> <th>
Line 52:		Line 52:
	</th> </tr>		</th> </tr>

	<tr> <th><var>		<tr> <th><var>LAST UPDATE</var></th> <td>All. This is the default. </td> </tr>
	<p>LAST UPDATE~~</p>~~
	</var></th> <td>All. This is the default. </td> </tr>

	<tr> <th><var>		<tr> <th><var>LAST CHECKPOINT</var></th>
	<p>LAST CHECKPOINT~~</p>~~		<td>Last checkpoint on the input journal.
	</var></th> <td>
	<p>Last checkpoint on the input journal.~~</p>~~
	</td> </tr>		</td> </tr>

	<tr> <th nowrap><var>		<tr> <th nowrap><var>UPDATE <i>number</i> OF <i>id</i></var></th> <td>And including the update specified by <i>number</i> and <i>id</i>. The ID is the date/time stamp from the END OF UPDATE message, specified in the form: yy.ddd hh:mm:ss.th.</td> </tr>
	<p>UPDATE <i>number</i> OF <i>id</i>~~</p>~~
	</var></th> <td>And including the update specified by <i>number</i> and <i>id</i>. The ID is the date/time stamp from the END OF UPDATE message, specified in the form: yy.ddd hh:mm:ss.th.</td> </tr>

	<tr> <th><var>		<tr> <th><var>CHECKPOINT <i>id</i></var></th>
	<p>CHECKPOINT <i>id</i>~~</p>~~		<td>Specified checkpoint. The ID is specified in the form: yy.ddd hh:mm:ss.th. </td> </tr>
	</var></th> <td>
	<p>Specified checkpoint. The ID is specified in the form: yy.ddd hh:mm:ss.th. ~~</p>~~
	</td> </tr>

	</table>		</table>
	</li>		</li>

ELowell: /* Using the TO UPDATE option */

2014-02-12T20:01:51Z

Using the TO UPDATE option

← Older revision		Revision as of 20:01, 12 February 2014
Line 125:		Line 125:
	<p>If TO UPDATE <var class="term">nn</var> OF <var class="term">id</var> is specified, it must appear only on the first FILE statement, and no other ‘TO’ options are allowed on subsequent files.</p>		<p>If TO UPDATE <var class="term">nn</var> OF <var class="term">id</var> is specified, it must appear only on the first FILE statement, and no other ‘TO’ options are allowed on subsequent files.</p>
	(In Model 204 version 7.6, the new message: <code>M204:1664 "TO UPDATE" only allowed on first line of REGENerate</code> appears any time more than one TO UPDATE is specified, or if TO UPDATE is specified on a line other than the first.)		(In Model 204 version 7.6, the new message: <code>M204:1664 "TO UPDATE" only allowed on first line of REGENerate</code> appears any time more than one TO UPDATE is specified, or if TO UPDATE is specified on a line other than the first.)
	<p>All additional files ~~will be~~ recovered as though they each specified the same 'TO UPDATE' option. The <var class="term">id</var>' timestamp is the END OF TRANSACTION timestamp. Once the 'end of transaction' is reached, further processing ~~will stop~~, all inflight transactions ~~will be~~ backed out, and RC=0 ~~will be~~ set.</p>		<p>All additional files are recovered as though they each specified the same 'TO UPDATE' option. The <var class="term">id</var>' timestamp is the END OF TRANSACTION timestamp. Once the 'end of transaction' is reached, further processing stops, all inflight transactions are backed out, and RC=0 is set.</p>

	<p>If the update is not found in the journal, then the run stops immediately after pass 1. RC=4 is set. This message is displayed for each file: </p>		<p>If the update is not found in the journal, then the run stops immediately after pass 1. RC=4 is set. This message is displayed for each file: </p>

ELowell: /* Using the TO UPDATE option */

2014-02-12T20:00:18Z

Using the TO UPDATE option

← Older revision		Revision as of 20:00, 12 February 2014
Line 127:		Line 127:
	<p>All additional files will be recovered as though they each specified the same 'TO UPDATE' option. The <var class="term">id</var>' timestamp is the END OF TRANSACTION timestamp. Once the 'end of transaction' is reached, further processing will stop, all inflight transactions will be backed out, and RC=0 will be set.</p>		<p>All additional files will be recovered as though they each specified the same 'TO UPDATE' option. The <var class="term">id</var>' timestamp is the END OF TRANSACTION timestamp. Once the 'end of transaction' is reached, further processing will stop, all inflight transactions will be backed out, and RC=0 will be set.</p>

	<p>If the update is not found in the journal, then the run stops immediately after pass 1. This message is displayed for each file: </p>		<p>If the update is not found in the journal, then the run stops immediately after pass 1. RC=4 is set. This message is displayed for each file: </p>
	<p class="code">M204.1409: MISSING STOPPING POINT FOR FILE <var class="term">filename</var></p>		<p class="code">M204.1409: MISSING STOPPING POINT FOR FILE <var class="term">filename</var></p>
	And this message is also displayed:		And this message is also displayed: