RESTART command - Revision history

JAL: /* Example of processing output with IGNORE option on RESTART */ remove blank

2017-10-31T22:16:15Z

Example of processing output with IGNORE option on RESTART: remove blank

← Older revision		Revision as of 22:16, 31 October 2017
Line 122:		Line 122:
	The following example shows processing output with the <var>IGNORE</var> option: </p>		The following example shows processing output with the <var>IGNORE</var> option: </p>
	<p class="code">M204.2512: ROLL BACK WILL USE THE FOLLOWING DATASET: RESTART		<p class="code">M204.2512: ROLL BACK WILL USE THE FOLLOWING DATASET: RESTART
	M204.1523: EOF REACHED IN FIRST PASS OF RESTART STREAM AFTER SEQ# 5558 OF 11.181 17:10:36.0		M204.1523: EOF REACHED IN FIRST PASS OF RESTART STREAM AFTER SEQ# 5558 OF 11.181 17:10:36.0
	M204.2915: IGNORE SPECIFIED FOR FILE K100VAIL BUT RECOVERABLE UPDATES WERE AVAILABLE		M204.2915: IGNORE SPECIFIED FOR FILE K100VAIL BUT RECOVERABLE UPDATES WERE AVAILABLE
	M204.2915: IGNORE SPECIFIED FOR FILE DEBCPROC WHICH HAD NO RECOVERABLE UPDATES		M204.2915: IGNORE SPECIFIED FOR FILE DEBCPROC WHICH HAD NO RECOVERABLE UPDATES

ELowell: /* Rolling back and rolling forward */

2017-06-08T20:46:53Z

Rolling back and rolling forward

← Older revision		Revision as of 20:46, 8 June 2017
Line 94:		Line 94:
	<p>		<p>
	If the system manager does not include the <var>ROLL BACK</var> argument in the <var>RESTART</var> command and replies <code>NO</code> to the <code>ROLL BACK</code> prompt, <var class="product">Model 204</var> does not perform ROLL BACK, and the new Online job starts immediately. The database is left in the state it was in at the time of the system failure. In general, if the previous Online job ended abnormally or if the entire system crashed, the ROLL BACK facility should be invoked.</p>		If the system manager does not include the <var>ROLL BACK</var> argument in the <var>RESTART</var> command and replies <code>NO</code> to the <code>ROLL BACK</code> prompt, <var class="product">Model 204</var> does not perform ROLL BACK, and the new Online job starts immediately. The database is left in the state it was in at the time of the system failure. In general, if the previous Online job ended abnormally or if the entire system crashed, the ROLL BACK facility should be invoked.</p>

			====RESTART recovery requirements====
			For information on recovery requirements for <var>CCATEMP</var>, <var>NFILES</var>, and <var>NDIR</var>, see [[System_and_media_recovery#RESTART_recovery_requirements_-_CCATEMP.2C_NFILES.2C_NDIR\|RESTART recovery requirements]].

	====Rolling back and rolling forward====		====Rolling back and rolling forward====

ELowell: /* Rolling back and rolling forward */

2017-06-08T19:40:31Z

Rolling back and rolling forward

← Older revision		Revision as of 19:40, 8 June 2017
Line 101:		Line 101:
	If ROLL BACK is performed, all files are rolled back to the specified checkpoint. Any changes made to files since that time are undone. If a checkpoint is not specified, <var class="product">Model 204</var> rolls back to the last checkpoint. During ROLL BACK processing, errors in opening files are handled as specified in the <var>ERROR</var> clause. Regardless of this argument, <var class="product">Model 204</var> sends to the operator's console a list of files that can be rolled back and a list of those that cannot be rolled back. </p>		If ROLL BACK is performed, all files are rolled back to the specified checkpoint. Any changes made to files since that time are undone. If a checkpoint is not specified, <var class="product">Model 204</var> rolls back to the last checkpoint. During ROLL BACK processing, errors in opening files are handled as specified in the <var>ERROR</var> clause. Regardless of this argument, <var class="product">Model 204</var> sends to the operator's console a list of files that can be rolled back and a list of those that cannot be rolled back. </p>
	<p>		<p>
	If the system manager includes the <var>ROLL FORWARD</var> argument in the <var>RESTART</var> command or replies <code>YES</code> to the <code>ROLL FORWARD</code> prompt, <var class="product">Model 204</var> reapplies as many file updates as possible after performing ROLL BACK. <var class="product">Model 204</var> recovery facilities are also discussed in [[System and media recovery]].</p>		If the system manager includes the <var>ROLL FORWARD</var> argument in the <var>RESTART</var> command or replies <code>YES</code> to the <code>ROLL FORWARD</code> prompt, <var class="product">Model 204</var> reapplies as many file updates as possible after performing ROLL BACK. <var class="product">Model 204</var> recovery facilities, including ROLL BACK and ROLL FORWARD, are also discussed in [[System and media recovery]].</p>

	====RESTART under z/VSE====		====RESTART under z/VSE====

ELowell: /* See also */

2017-06-08T19:36:26Z

JAL: remove Sys Man guide

2014-11-17T22:52:30Z

remove Sys Man guide

Show changes

ELowell: /* Recovering dynamically allocated data sets */

2013-06-27T21:04:39Z

Recovering dynamically allocated data sets

← Older revision		Revision as of 21:04, 27 June 2013
Line 140:		Line 140:
	</p>		</p>
	====Recovering dynamically allocated data sets====		====Recovering dynamically allocated data sets====
	<p>Data sets that were dynamically allocated are normally closed and released after recovery. Therefore, you must reallocate the data sets when recovery is over. However, if a dynamically allocated data set was opened in deferred update mode and the NODYNAM option is not chosen, the data set remains opened and allocated after recovery. In this way deferred updates performed after recovery do not overwrite records sent to the deferred update data set before the system failure. The deferred update feature is explained in detail in the <var class="book">Model 204 File Manager's Guide</var>.</p>		<p>Data sets that were dynamically allocated are normally closed and released after recovery. Therefore, you must reallocate the data sets when recovery is over. However, if a dynamically allocated data set was opened in deferred update mode and the NODYNAM option is not chosen, the data set remains opened and allocated after recovery. In this way deferred updates performed after recovery do not overwrite records sent to the deferred update data set before the system failure. The deferred update feature is explained in detail in the <var class="book">Rocket Model 204 File Manager's Guide</var>.</p>
	<p>If the NODYNAM option is chosen, files that were dynamically allocated before a system failure are not dynamically allocated during recovery. The only files recovered are those specified in the JCL for recovery. Under z/VM, only files specified through FILEDEF statements are recovered. </p>		<p>If the NODYNAM option is chosen, files that were dynamically allocated before a system failure are not dynamically allocated during recovery. The only files recovered are those specified in the JCL for recovery. Under z/VM, only files specified through FILEDEF statements are recovered. </p>

	====Undoing ROLL FORWARD processing====		====Undoing ROLL FORWARD processing====
	<p>ROLL FORWARD processing cannot specify a stopping point. Updates are reapplied to the place where RESTART recovery began. </p>		<p>ROLL FORWARD processing cannot specify a stopping point. Updates are reapplied to the place where RESTART recovery began. </p>

Dme: /* Undoing ROLL FORWARD processing */

2013-05-08T19:55:22Z

Undoing ROLL FORWARD processing

← Older revision		Revision as of 19:55, 8 May 2013
Line 154:		Line 154:
	<p>Because the RESTART command must be the first command in a run, each of the previously listed RESTART commands must be in a separate recovery run. </p>		<p>Because the RESTART command must be the first command in a run, each of the previously listed RESTART commands must be in a separate recovery run. </p>
	<p class="note"><b>Note:</b> After recovery is successful, you can use the RERUNRB option to force the roll back to recur. By running RESTART commands, similar to the previous sequence, one after another, you can roll files back to the job start, or intermediate locations, and then roll them forward to the job end as many times as you wish.</p>		<p class="note"><b>Note:</b> After recovery is successful, you can use the RERUNRB option to force the roll back to recur. By running RESTART commands, similar to the previous sequence, one after another, you can roll files back to the job start, or intermediate locations, and then roll them forward to the job end as many times as you wish.</p>
			==See also==
			<ul>
			<li>The <var>[[RESTART operator command\|RESTART]]</var>[[RESTART operator command\| operator command]] is an entirely different command, which requests a user abend of a <var class="product">Model 204</var> user or task, for example, to break a CPU loop.
			</ul>
	[[Category:Commands]]		[[Category:Commands]]

JALWiccan: Automatically generated page update

2013-04-20T01:30:33Z

Automatically generated page update

← Older revision		Revision as of 01:30, 20 April 2013
Line 113:		Line 113:
	<p>The system manager can request ROLL BACK and/or ROLL FORWARD processing for system recovery. ROLL BACK processing rolls back to the specified checkpoint all updates made to <var class="product">Model 204</var> files since the time of that checkpoint. This process leaves the database in a consistent state. Then, ROLL FORWARD processing reapplies as many updates performed prior to the system failure as possible.</p>		<p>The system manager can request ROLL BACK and/or ROLL FORWARD processing for system recovery. ROLL BACK processing rolls back to the specified checkpoint all updates made to <var class="product">Model 204</var> files since the time of that checkpoint. This process leaves the database in a consistent state. Then, ROLL FORWARD processing reapplies as many updates performed prior to the system failure as possible.</p>
	<p>If ROLL BACK is performed, all files are rolled back to the specified checkpoint. Any changes made to files since that time are undone. If a checkpoint is not specified, <var class="product">Model 204</var> rolls back to the last checkpoint. During ROLL BACK processing, errors in opening files are handled as specified in the ERROR clause. Regardless of this argument, <var class="product">Model 204</var> sends to the operator's console a list of files that can be rolled back and a list of those that cannot be rolled back. </p>		<p>If ROLL BACK is performed, all files are rolled back to the specified checkpoint. Any changes made to files since that time are undone. If a checkpoint is not specified, <var class="product">Model 204</var> rolls back to the last checkpoint. During ROLL BACK processing, errors in opening files are handled as specified in the ERROR clause. Regardless of this argument, <var class="product">Model 204</var> sends to the operator's console a list of files that can be rolled back and a list of those that cannot be rolled back. </p>
	<p>If the system manager includes the ROLL FORWARD argument in the RESTART command or replies YES to the ROLL FORWARD prompt, <var class="product">Model 204</var> reapplies as many file updates as possible after performing ROLL BACK. <var class="product">Model 204</var> recovery facilities are also discussed in the <var>Model 204 System Manager's Guide</var>.</p>		<p>If the system manager includes the ROLL FORWARD argument in the RESTART command or replies YES to the ROLL FORWARD prompt, <var class="product">Model 204</var> reapplies as many file updates as possible after performing ROLL BACK. <var class="product">Model 204</var> recovery facilities are also discussed in the <var class="book">Model 204 System Manager's Guide</var>.</p>
	====RESTART under z/VSE====		====RESTART under z/VSE====
	<p>Under z/VSE, the DEFINE DATASET command must precede the User 0 parameter line in the CCAIN input stream, if tape journals or checkpoint datasets are used in RESTART recovery. Refer to [[DEFINE DATASET command\|DEFINE DATASET: Data set or file characteristics]] for more information on this requirement.</p>		<p>Under z/VSE, the DEFINE DATASET command must precede the User 0 parameter line in the CCAIN input stream, if tape journals or checkpoint datasets are used in RESTART recovery. Refer to [[DEFINE DATASET command\|DEFINE DATASET: Data set or file characteristics]] for more information on this requirement.</p>

JALWiccan: Automatically generated page update

2013-04-20T01:26:46Z

Automatically generated page update

← Older revision		Revision as of 01:26, 20 April 2013
Line 140:		Line 140:
	</p>		</p>
	====Recovering dynamically allocated data sets====		====Recovering dynamically allocated data sets====
	<p>Data sets that were dynamically allocated are normally closed and released after recovery. Therefore, you must reallocate the data sets when recovery is over. However, if a dynamically allocated data set was opened in deferred update mode and the NODYNAM option is not chosen, the data set remains opened and allocated after recovery. In this way deferred updates performed after recovery do not overwrite records sent to the deferred update data set before the system failure. The deferred update feature is explained in detail in the <var>Model 204 File Manager's Guide</var>.</p>		<p>Data sets that were dynamically allocated are normally closed and released after recovery. Therefore, you must reallocate the data sets when recovery is over. However, if a dynamically allocated data set was opened in deferred update mode and the NODYNAM option is not chosen, the data set remains opened and allocated after recovery. In this way deferred updates performed after recovery do not overwrite records sent to the deferred update data set before the system failure. The deferred update feature is explained in detail in the <var class="book">Model 204 File Manager's Guide</var>.</p>
	<p>If the NODYNAM option is chosen, files that were dynamically allocated before a system failure are not dynamically allocated during recovery. The only files recovered are those specified in the JCL for recovery. Under z/VM, only files specified through FILEDEF statements are recovered. </p>		<p>If the NODYNAM option is chosen, files that were dynamically allocated before a system failure are not dynamically allocated during recovery. The only files recovered are those specified in the JCL for recovery. Under z/VM, only files specified through FILEDEF statements are recovered. </p>
	====Undoing ROLL FORWARD processing====		====Undoing ROLL FORWARD processing====

Alex: Automatically generated page update

2013-02-28T01:05:23Z

Automatically generated page update

Show changes

← Older revision		Revision as of 19:36, 8 June 2017
Line 160:		Line 160:
	==See also==		==See also==
	<ul>		<ul>
			<li>[[System and media recovery]] for information on RESTART recovery data sets, RESTART recovery requirements, rerunning RESTART recovery, sub-transaction checkpoints, and more.</li>
	<li>The <var>[[RESTART operator command\|RESTART]]</var>[[RESTART operator command\| operator command]] is an entirely different command, which requests a user abend of a <var class="product">Model 204</var> user or task, for example, to break a CPU loop.		<li>The <var>[[RESTART operator command\|RESTART]]</var>[[RESTART operator command\| operator command]] is an entirely different command, which requests a user abend of a <var class="product">Model 204</var> user or task, for example, to break a CPU loop.
	</ul>		</ul>

	[[Category:Commands]]		[[Category:Commands]]