File dumping and restoring - Revision history

JAL: misc formatting

2017-07-24T21:49:29Z

misc formatting

JAL: /* Using DUMP and RESTORE with media recovery */ link repair

2016-11-02T20:08:44Z

Using DUMP and RESTORE with media recovery: link repair

← Older revision		Revision as of 20:08, 2 November 2016
Line 45:		Line 45:
	==Using DUMP and RESTORE with media recovery==		==Using DUMP and RESTORE with media recovery==
	<p>		<p>
	If your site uses media recovery ~~(described in~~		If your site uses [[Media recovery\|media recovery]] to recover files in the event of a media failure, such as a disk head crash, be sure to dump all <var class="product">Model 204</var> files on a regular basis. In addition, ensure that journals are produced for runs that update files between dumps. </p>
	~~the <var class="book">[http://docs.rocketsoftware.com/nxt/gateway.dll/RKBnew556/model%20204/v7.4/m204_v7r4_system_manager.pdf Rocket Model 204 System Manager's Guide~~]~~</var>)~~
	to recover files in the event of a media failure, such as a disk head crash, be sure to dump all <var class="product">Model 204</var> files on a regular basis. In addition, ensure that journals are produced for runs that update files between dumps. </p>
	<p>		<p>
	When a dump is taken, <var class="product">Model 204</var> records the time and date on both the dump data set and the journal data set (if journaling is active). When media recovery is performed, the starting point in the journal for reapplying updates to a file is the first update that occurs after the time and date of the dump data set. (See ~~the~~		When a dump is taken, <var class="product">Model 204</var> records the time and date on both the dump data set and the journal data set (if journaling is active). When media recovery is performed, the starting point in the journal for reapplying updates to a file is the first update that occurs after the time and date of the dump data set. (See [[Tracking system activity (CCAJRNL, CCAAUDIT, CCAJLOG)]] for information about journaling, and also see the description of the <var>[[REGENERATE command\|REGENERATE]]</var> command.)</p>
	~~<var class="book">Rocket Model 204 System Manager's Guide</var>~~
	for information about journaling, ~~as well as~~ the description of the <var>REGENERATE</var> command.)</p>

	==Dumping files==		==Dumping files==

JAL at 16:14, 22 October 2014

2014-10-22T16:14:12Z

← Older revision		Revision as of 16:14, 22 October 2014
Line 141:		Line 141:
	</ul>		</ul>
	<p>		<p>
	If the data set is on tape, you can use the ~~<var>~~LABEL~~</var>~~ parameter.</p>		If the data set is on tape, you can use the LABEL parameter.</p>
	<p>		<p>
	If the data set is on disk, the ~~<var>~~SPACE~~</var>~~ parameter must be present and set equivalent to the amount of space occupied by the <var class="product">Model 204</var> file.</p>		If the data set is on disk, the SPACE parameter must be present and set equivalent to the amount of space occupied by the <var class="product">Model 204</var> file.</p>
	<p>		<p>
	Omit DCB information unless your site uses blocking as discussed in [[#Blocking DUMP data sets\|Blocking DUMP data sets]]. </p>		Omit DCB information unless your site uses blocking as discussed in [[#Blocking DUMP data sets\|Blocking DUMP data sets]]. </p>

JAL at 16:08, 22 October 2014

2014-10-22T16:08:01Z

← Older revision		Revision as of 16:08, 22 October 2014
Line 141:		Line 141:
	</ul>		</ul>
	<p>		<p>
	If the data set is on tape, you can use the <var>[[LABEL ~~parameter\|LABEL]]~~</var> parameter.</p>		If the data set is on tape, you can use the <var>LABEL</var> parameter.</p>
	<p>		<p>
	If the data set is on disk, the <var>[[SPACE ~~parameter\|SPACE]]~~</var> parameter must be present and set equivalent to the amount of space occupied by the <var class="product">Model 204</var> file.</p>		If the data set is on disk, the <var>SPACE</var> parameter must be present and set equivalent to the amount of space occupied by the <var class="product">Model 204</var> file.</p>
	<p>		<p>
	Omit DCB information unless your site uses blocking as discussed in [[#Blocking DUMP data sets\|Blocking DUMP data sets]]. </p>		Omit DCB information unless your site uses blocking as discussed in [[#Blocking DUMP data sets\|Blocking DUMP data sets]]. </p>

DmeWiccan: Automatically generated page update

2014-05-09T22:45:45Z

Automatically generated page update

← Older revision		Revision as of 22:45, 9 May 2014
Line 959:		Line 959:
	</div> <!-- end of toc limit div -->		</div> <!-- end of toc limit div -->

	[[Category:~~File management~~]]		[[Category:Model 204 files]]

JAL: more cleanup

2014-02-06T00:32:26Z

more cleanup

Show changes

JAL at 20:38, 4 February 2014

2014-02-04T20:38:34Z

Show changes

JAL: more conversion cleanup

2014-02-04T19:30:02Z

more conversion cleanup

Show changes

ELowell: /* Blocking DUMP data sets */

2014-01-21T19:26:41Z

Blocking DUMP data sets

← Older revision		Revision as of 19:26, 21 January 2014
Line 100:		Line 100:
	<p>DUMP data sets can be blocked. In z/OS, specify a BLKSIZE entry in the DCB parameter in the DD statement. The specified block size must be a multiple of 6184 (that is, PAGESZ). If it is not, <var class="product">Model 204</var> rounds the block size down to the next multiple of 6184. </p>		<p>DUMP data sets can be blocked. In z/OS, specify a BLKSIZE entry in the DCB parameter in the DD statement. The specified block size must be a multiple of 6184 (that is, PAGESZ). If it is not, <var class="product">Model 204</var> rounds the block size down to the next multiple of 6184. </p>

	<p>As of version 7.5, if a BLKSIZE is not specified, the z/OS operating system calculates the optimal BLKSIZE.		<p>As of version 7.5, if the BLKSIZE is zero or is not specified, the z/OS operating system calculates the optimal BLKSIZE.
	In version 7.4 and earlier, if a BLKSIZE is not specified, 6184 is used as the default block size.		In version 7.4 and earlier, if the BLKSIZE is zero or is not specified, 6184 is used as the default block size.
	</p>		</p>

ELowell: /* Blocking DUMP data sets */

2014-01-21T19:24:32Z

Blocking DUMP data sets

← Older revision		Revision as of 19:24, 21 January 2014
Line 100:		Line 100:
	<p>DUMP data sets can be blocked. In z/OS, specify a BLKSIZE entry in the DCB parameter in the DD statement. The specified block size must be a multiple of 6184 (that is, PAGESZ). If it is not, <var class="product">Model 204</var> rounds the block size down to the next multiple of 6184. </p>		<p>DUMP data sets can be blocked. In z/OS, specify a BLKSIZE entry in the DCB parameter in the DD statement. The specified block size must be a multiple of 6184 (that is, PAGESZ). If it is not, <var class="product">Model 204</var> rounds the block size down to the next multiple of 6184. </p>

	<p>As of ~~verion~~ 7.5, if a BLKSIZE is not specified, the z/OS operating system calculates the optimal BLKSIZE.		<p>As of version 7.5, if a BLKSIZE is not specified, the z/OS operating system calculates the optimal BLKSIZE.
	In version 7.4 and earlier, if a BLKSIZE is not specified, 6184 is used as the default block size.		In version 7.4 and earlier, if a BLKSIZE is not specified, 6184 is used as the default block size.
	</p>		</p>