DUMP command - Revision history

Ekern: /* Syntax */

2025-01-31T23:42:56Z

Syntax

← Older revision		Revision as of 23:42, 31 January 2025
Line 27:		Line 27:
	<tr>		<tr>
	<th>NBUFF</th>		<th>NBUFF</th>
			<td>
	<p>NBUFF set the number of sequential I/O buffers for BACKUP or RESTORE. Code the NBUFF keyword after the DUMP or RESTORE command. For example:		<p>NBUFF set the number of sequential I/O buffers for BACKUP or RESTORE. Code the NBUFF keyword after the DUMP or RESTORE command. For example:
	RESTORE 192 FROM TESTFILE NBUFF 50		RESTORE 192 FROM TESTFILE NBUFF 50
	Each buffer is equal in size to the blocksize of the sequential dataset. Thus, if NBUFF is 20, and the sequential dataset blocksize is 30920 bytes, 618,400 bytes of storage will be needed for the sequential I/O buffers. NBUFF can be set to any number between 1 and 99 inclusive.		Each buffer is equal in size to the blocksize of the sequential dataset. Thus, if NBUFF is 20, and the sequential dataset blocksize is 30920 bytes, 618,400 bytes of storage will be needed for the sequential I/O buffers. NBUFF can be set to any number between 1 and 99 inclusive.
	pagesize * 180 / blocksize</p>		pagesize * 180 / blocksize</p>
			</td>
	</tr>		</tr>
	</table>		</table>

Ekern: /* Syntax */

2025-01-31T23:41:48Z

Syntax

← Older revision		Revision as of 23:41, 31 January 2025
Line 24:		Line 24:
	<p>Each buffer is equal in size to the blocksize of the sequential dataset. Thus, if NBUFF is 20, and the sequential dataset blocksize is 30920 bytes, 618,400 bytes of storage will be needed for the sequential I/O buffers. NBUFF can be set to any number between 1 and 99 inclusive.</p>		<p>Each buffer is equal in size to the blocksize of the sequential dataset. Thus, if NBUFF is 20, and the sequential dataset blocksize is 30920 bytes, 618,400 bytes of storage will be needed for the sequential I/O buffers. NBUFF can be set to any number between 1 and 99 inclusive.</p>
	</td>		</td>
			</tr>
			<tr>
			<th>NBUFF</th>
			<p>NBUFF set the number of sequential I/O buffers for BACKUP or RESTORE. Code the NBUFF keyword after the DUMP or RESTORE command. For example:
			RESTORE 192 FROM TESTFILE NBUFF 50
			Each buffer is equal in size to the blocksize of the sequential dataset. Thus, if NBUFF is 20, and the sequential dataset blocksize is 30920 bytes, 618,400 bytes of storage will be needed for the sequential I/O buffers. NBUFF can be set to any number between 1 and 99 inclusive.
			pagesize * 180 / blocksize</p>
	</tr>		</tr>
	</table>		</table>

Goff: /* Syntax */

2024-08-15T22:54:48Z

Syntax

← Older revision		Revision as of 22:54, 15 August 2024
Line 8:		Line 8:

	==Syntax==		==Syntax==
	<p class="syntax">DUMP TO <span class="term">ddname</span>		<p class="syntax">DUMP TO <span class="term">ddname</span> [NBUFF <span class="term">I/Obuffers</span>]
	</p>		</p>

	Where <~~var class="term"~~>ddname</~~var~~> is the name of the sequential ~~data set~~ to which the file is written.		Where
			<table>
			<tr>
			<th>ddname</th>
			<td>Is the name of the sequential dataset to which the file is written.</td>
			</tr>
			<tr>
			<th>I/Obuffers</th>
			<td>
			<p>Optionally sets the number of sequential I/O buffers DUMP can use. For example:</p>
			<p class="code">DUMP TO TESTFILE NBUFF 50</p>
			<p>Each buffer is equal in size to the blocksize of the sequential dataset. Thus, if NBUFF is 20, and the sequential dataset blocksize is 30920 bytes, 618,400 bytes of storage will be needed for the sequential I/O buffers. NBUFF can be set to any number between 1 and 99 inclusive.</p>
			</td>
			</tr>
			</table>

	===Syntax notes===		===Syntax notes===

Dme: /* Usage notes */

2017-07-13T17:41:11Z

Usage notes

← Older revision		Revision as of 17:41, 13 July 2017
Line 27:		Line 27:

	==Usage notes==		==Usage notes==
	The <var>DUMP</var> command copies an open <var class="product">Model 204</var> file to a sequential data set that is located on either a magnetic tape or a direct access device. <var>DUMP</var> backs up a file so that the dumped version is available in case of a system or media failure. The dumped version can subsequently be restored using either the <var>RESTORE</var> or the <var>REGENERATE</var> command.		The <var>DUMP</var> command copies an open <var class="product">Model 204</var> file to a sequential data set that is located on either a magnetic tape or a direct access device. <var>DUMP</var> backs up a file so that the dumped version is available in case of a system or media failure. The dumped version can subsequently be restored using either the <var>[[RESTORE command\|RESTORE]]</var> command or the <var>[[REGENERATE command\|REGENERATE]]</var> command.
	<p class="note"><b>Note:</b> Use the DUMP command before using either the REGENERATE or the RESTORE command. DUMP updates the file while making a backup copy (to a target media). Otherwise, when you do a media recovery using either REGENERATE (to include journals) or RESTORE (without journals), the backup copy does not incorporate all updates, but you cannot detect this.</p>		<p class="note"><b>Note:</b> Use the DUMP command before using either the REGENERATE or the RESTORE command. DUMP updates the file while making a backup copy (to a target media). Otherwise, when you do a media recovery using either REGENERATE (to include journals) or RESTORE (without journals), the backup copy does not incorporate all updates, but you cannot detect this.</p>
	<p>		<p>

JAL at 19:27, 29 January 2015

2015-01-29T19:27:23Z

← Older revision		Revision as of 19:27, 29 January 2015
Line 6:		Line 6:
	<dd>Backs up a <var class="product">Model 204</var> file to a sequential data set		<dd>Backs up a <var class="product">Model 204</var> file to a sequential data set
	</dl>		</dl>

	==Syntax==		==Syntax==
	<p class="syntax">DUMP TO <i>ddname</i>		<p class="syntax">DUMP TO <span class="term">ddname</span>
	</p>		</p>

	<b>~~Where:~~</b>		Where <var class="term">ddname</var> is the name of the sequential data set to which the file is written.
	~~ddname~~ is the name of the sequential data set to which the file is written
	===Syntax notes===		===Syntax notes===
	DUMP must be issued in file context (that is, the current default must be a file, not a group).		<var>DUMP</var> must be issued in file context (that is, the current default must be a file, not a group).

	==Example==		==Example==
	<p class="code">OPEN PEOPLE		<p class="code">OPEN PEOPLE
Line 23:		Line 25:
	<b>CLOSE PEOPLE</b>		<b>CLOSE PEOPLE</b>
	</p>		</p>

	==Usage notes==		==Usage notes==
	The DUMP command copies an open <var class="product">Model 204</var> file to a sequential data set that is located on either a magnetic tape or a direct access device. DUMP backs up a file so that the dumped version is available in case of a system or media failure. The dumped version can subsequently be restored using either the RESTORE or the REGENERATE command.		The <var>DUMP</var> command copies an open <var class="product">Model 204</var> file to a sequential data set that is located on either a magnetic tape or a direct access device. <var>DUMP</var> backs up a file so that the dumped version is available in case of a system or media failure. The dumped version can subsequently be restored using either the <var>RESTORE</var> or the <var>REGENERATE</var> command.
	<p class="note"><b>Note:</b> Use the DUMP command before using either the REGENERATE or the RESTORE command. DUMP updates the file while making a backup copy (to a target media). Otherwise, when you do a media recovery using either REGENERATE (to include journals) or RESTORE (without journals), the backup copy does not incorporate all updates, but you cannot detect this.</p>		<p class="note"><b>Note:</b> Use the DUMP command before using either the REGENERATE or the RESTORE command. DUMP updates the file while making a backup copy (to a target media). Otherwise, when you do a media recovery using either REGENERATE (to include journals) or RESTORE (without journals), the backup copy does not incorporate all updates, but you cannot detect this.</p>
	<p>If a file is skewed, the file can be transferred from one device type to another only through the <var class="product">Model 204</var> DUMP/RESTORE facility. ~~For a complete discussion of the~~ obsolete ~~skewing~~ feature~~, see "File skewing" in the <var class="product">Model 204</var> File Manager's Guide~~.</p>		<p>
	<p>Dump files can be accessed and updated during execution of the DUMP command. After the DUMP command has been issued, the DUMP waits until all existing transactions that might update the file are complete and the existing copy of the file is in a consistent state. At that point the DUMP begins. If a subsequent user request updates the file being dumped, preimages of database pages to be updated are dumped before the update is allowed. The dumped copy matches the state of the file at the time the DUMP begins.</p>		If a file is skewed, the file can be transferred from one device type to another only through the <var class="product">Model 204</var> DUMP/RESTORE facility. File skewing is an obsolete feature.</p>
	<p>If updates are not complete when the DUMP command for a file is issued, you receive a message that the file is still in use. The DUMP can be canceled at this juncture. If errors are detected during the file dump, the dump is ended. A message to this effect is displayed.</p>		<p>
	<p>Job level enqueuing is not affected by this facility. A BATCH204 job cannot be started to dump files that are being updated in another <var class="product">Model 204</var> job. Use of the DUMP command from any <var class="product">Model 204</var> job requires exclusive access to the file by that copy of <var class="product">Model 204</var>.</p>		Dump files can be accessed and updated during execution of the <var>DUMP</var> command. After the <var>DUMP</var> command has been issued, the <var>DUMP</var> waits until all existing transactions that might update the file are complete and the existing copy of the file is in a consistent state. At that point the <var>DUMP</var> begins. If a subsequent user request updates the file being dumped, preimages of database pages to be updated are dumped before the update is allowed. The dumped copy matches the state of the file at the time the <var>DUMP</var> begins.</p>
	<p>If an external security interface is active, the user ID issuing the command is checked for the proper data set usage authorization. If the authorization check fails, the attempt is logged as a security violation and the command is not executed. </p>		<p>
	<p>With a security interface, you must have WRITE, ALTER, or UPDATE privileges to use the DUMP command with sequential data sets. For more information, refer to the ~~<var>Model 204~~ Security ~~Interfaces Guide</var>~~. </p>		If updates are not complete when the <var>DUMP</var> command for a file is issued, you receive a message that the file is still in use. The DUMP can be canceled at this juncture. If errors are detected during the file dump, the dump is ended. A message to this effect is displayed.</p>
	<p>When it processes DUMP, <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. ~~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>
	<p>~~The DUMP, RESTORE, and REGENERATE~~ commands and their use in dumping, restoring, and regenerating files are explained in ~~detail in the <var class="product">Model 204</var>~~ File ~~Manager's Guide~~.</p>		Job level enqueuing is not affected by this facility. A BATCH204 job cannot be started to dump files that are being updated in another <var class="product">Model 204</var> job. Use of the <var>DUMP</var> command from any <var class="product">Model 204</var> job requires exclusive access to the file by that copy of <var class="product">Model 204</var>.</p>
			<p>
			If an external security interface is active, the user ID issuing the command is checked for the proper data set usage authorization. If the authorization check fails, the attempt is logged as a security violation and the command is not executed. </p>
			<p>
			With a security interface, you must have <var>WRITE</var>, <var>ALTER</var>, or <var>UPDATE</var> privileges to use the DUMP command with sequential data sets. For more information, refer to the [[:Category:Security interfaces\|Security interfaces]] pages. </p>
			<p>
			When it processes <var>DUMP</var>, <var class="product">Model 204</var> ends any [[File integrity and recovery#Update units and transactions\|update unit]] in progress and begins a non-backoutable update unit. </p>
			<p>
			The <var>DUMP</var>, <var>RESTORE</var>, and <var>REGENERATE</var> commands and their use in dumping, restoring, and regenerating files are explained in [[File dumping and restoring]] and [[Media recovery]].</p>

	[[Category: File manager commands]]		[[Category: File manager commands]]
	[[Category:Commands]]		[[Category:Commands]]

JALWiccan: Automatically generated page update

2013-04-20T01:26:27Z

Automatically generated page update

← Older revision		Revision as of 01:26, 20 April 2013
Line 32:		Line 32:
	<p>If an external security interface is active, the user ID issuing the command is checked for the proper data set usage authorization. If the authorization check fails, the attempt is logged as a security violation and the command is not executed. </p>		<p>If an external security interface is active, the user ID issuing the command is checked for the proper data set usage authorization. If the authorization check fails, the attempt is logged as a security violation and the command is not executed. </p>
	<p>With a security interface, you must have WRITE, ALTER, or UPDATE privileges to use the DUMP command with sequential data sets. For more information, refer to the <var>Model 204 Security Interfaces Guide</var>. </p>		<p>With a security interface, you must have WRITE, ALTER, or UPDATE privileges to use the DUMP command with sequential data sets. For more information, refer to the <var>Model 204 Security Interfaces Guide</var>. </p>
	<p>When it processes DUMP, <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. For more information about <var class="product">Model 204</var> update units, see the <var>Model 204 File Manager's Guide</var>.</p>		<p>When it processes DUMP, <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. 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>The DUMP, RESTORE, and REGENERATE commands and their use in dumping, restoring, and regenerating files are explained in detail in the <var class="product">Model 204</var> File Manager's Guide.</p>		<p>The DUMP, RESTORE, and REGENERATE commands and their use in dumping, restoring, and regenerating files are explained in detail in the <var class="product">Model 204</var> File Manager's Guide.</p>
	[[Category: File manager commands]]		[[Category: File manager commands]]
	[[Category:Commands]]		[[Category:Commands]]

Alex: Automatically generated page update

2013-02-28T01:04:58Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>File manager
<dt>Function
<dd>Backs up a <var class="product">Model 204</var> file to a sequential data set
</dl>
==Syntax==
DUMP TO ddname


Where:
ddname is the name of the sequential data set to which the file is written
===Syntax notes===
DUMP must be issued in file context (that is, the current default must be a file, not a group).
==Example==
OPEN PEOPLE
M204.0620: FILE PEOPLE OPENED
M204.1203: FILE PEOPLE WAS LAST UPDATED ON hh:mm:ss
DUMP TO DUMPPEOP
M204.1760: FILE PEOPLE: DUMP BEGINNING AT hh:mm:ss
M204.1761: FILE PEOPLE: DUMP COMPLETED AT hh:mm:ss
CLOSE PEOPLE

==Usage notes==
The DUMP command copies an open <var class="product">Model 204</var> file to a sequential data set that is located on either a magnetic tape or a direct access device. DUMP backs up a file so that the dumped version is available in case of a system or media failure. The dumped version can subsequently be restored using either the RESTORE or the REGENERATE command.
Note: Use the DUMP command before using either the REGENERATE or the RESTORE command. DUMP updates the file while making a backup copy (to a target media). Otherwise, when you do a media recovery using either REGENERATE (to include journals) or RESTORE (without journals), the backup copy does not incorporate all updates, but you cannot detect this.
If a file is skewed, the file can be transferred from one device type to another only through the <var class="product">Model 204</var> DUMP/RESTORE facility. For a complete discussion of the obsolete skewing feature, see "File skewing" in the <var class="product">Model 204</var> File Manager's Guide.
Dump files can be accessed and updated during execution of the DUMP command. After the DUMP command has been issued, the DUMP waits until all existing transactions that might update the file are complete and the existing copy of the file is in a consistent state. At that point the DUMP begins. If a subsequent user request updates the file being dumped, preimages of database pages to be updated are dumped before the update is allowed. The dumped copy matches the state of the file at the time the DUMP begins.
If updates are not complete when the DUMP command for a file is issued, you receive a message that the file is still in use. The DUMP can be canceled at this juncture. If errors are detected during the file dump, the dump is ended. A message to this effect is displayed.
Job level enqueuing is not affected by this facility. A BATCH204 job cannot be started to dump files that are being updated in another <var class="product">Model 204</var> job. Use of the DUMP command from any <var class="product">Model 204</var> job requires exclusive access to the file by that copy of <var class="product">Model 204</var>.
If an external security interface is active, the user ID issuing the command is checked for the proper data set usage authorization. If the authorization check fails, the attempt is logged as a security violation and the command is not executed. 
With a security interface, you must have WRITE, ALTER, or UPDATE privileges to use the DUMP command with sequential data sets. For more information, refer to the <var>Model 204 Security Interfaces Guide</var>. 
When it processes DUMP, <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. For more information about <var class="product">Model 204</var> update units, see the <var>Model 204 File Manager's Guide</var>.
The DUMP, RESTORE, and REGENERATE commands and their use in dumping, restoring, and regenerating files are explained in detail in the <var class="product">Model 204</var> File Manager's Guide.
[[Category: File manager commands]]
[[Category:Commands]]