RESTORE command: Difference between revisions
m (link repair) |
m (→Syntax) |
||
(One intermediate revision by one other user not shown) | |||
Line 8: | Line 8: | ||
==Syntax== | ==Syntax== | ||
<p class="syntax">RESTORE [<span class="term">option</span>] FROM <span class="term">ddname</span> | <p class="syntax">RESTORE [<span class="term">option</span>] FROM <span class="term">ddname</span> [NBUFF <span class="term">I/Obuffers</span>] | ||
</p> | </p> | ||
Line 31: | Line 31: | ||
<tr> | <tr> | ||
<th>ddname</th> | <th>ddname</th> | ||
<td>The name of the data set from which the <var class="product">Model 204</var> file is being restored. If the < | <td>The name of the data set from which the <var class="product">Model 204</var> file is being restored. If the <code>FROM <i>ddname</i></code> clause points to a data set that was not created by the <var class="product">Model 204</var> <var>DUMP</var> command, the following error messages is issued: | ||
<p class="code">M204.2711: <var class="term">ddname</var> IS NOT A DUMP DATASET, CANNOT RESTORE INTO <var class="term">ddname2</var> | <p class="code">M204.2711: <var class="term">ddname</var> IS NOT A DUMP DATASET, CANNOT RESTORE INTO <var class="term">ddname2</var> | ||
</p></td> | </p></td> | ||
</tr> | </tr> | ||
<tr> | |||
<th>I/Obuffers</th> | |||
<td> | |||
<p>Optionally sets the number of sequential I/O buffers RESTORE can use. For example:</p> | |||
<p class="code">RESTORE 192 FROM 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> | </table> | ||
Latest revision as of 22:55, 15 August 2024
Summary
- Privileges
- File manager plus ad hoc updates
- Function
- Restores a Model 204 file from a dumped version of that file
Syntax
RESTORE [option] FROM ddname [NBUFF I/Obuffers]
Where:
option | A decimal value. Options can be summed. The options are:
| ||||||
---|---|---|---|---|---|---|---|
ddname | The name of the data set from which the Model 204 file is being restored. If the FROM ddname clause points to a data set that was not created by the Model 204 DUMP command, the following error messages is issued:
M204.2711: ddname IS NOT A DUMP DATASET, CANNOT RESTORE INTO ddname2 |
||||||
I/Obuffers |
Optionally sets the number of sequential I/O buffers RESTORE can use. 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. |
Example
OPEN CEN M204.0620: FILE CEN OPENED M204.1203: FILE CEN WAS LAST UPDATED ON hh:mm:ss RESTORE 192 FROM DUMPCEN M204.0500: FILE CEN: RESTORING FROM DUMP OF 88.262 SEP 19 14.24.29 M204.1760: FILE CEN: RESTORE BEGINNING AT 14.29.06 M204.1761: FILE CEN: RESTORE COMPLETED AT 14.29.24
Usage notes
- The RESTORE command restores a Model 204 file from a dumped version of that file. RESTORE takes a sequential data set produced by a DUMP command and turns it into a Model 204 file again.
Note: Before using the RESTORE (or REGENERATE) command, you need to have DUMP copies of the files. DUMP processing updates the file while making a backup copy (to a target media). Otherwise, when you do a media recovery using either RESTORE (which does not include journals) or REGENERATE (to include journals), the backup copy does not incorporate all updates, and you cannot detect this.
- The RESTORE command can be issued only in file context. (That is, the current default must be a file, not a group.) The file must be opened with file manager privileges and privileges to update with ad hoc requests.
- 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. Under a security interface, you must have READ privileges to read a file specified by this command. For more information, refer to the Security interfaces pages.
- If a file is skewed, the file can only be transferred from one device type to another through the Model 204 DUMP/RESTORE facility. File skewing is an obsolete feature.
- When RESTORE has finished processing, it automatically closes all private or semi-public files. Public files remain open.
- When it processes RESTORE, Model 204 ends any update unit in progress and begins a non-backoutable update unit.
- After Model 204 starts to restore a file, it displays a message showing the date and time the file was dumped. File dumping and restoring discusses the RESTORE options, along with a full presentation of DUMP, RESTORE, and their use in moving, renaming, and changing the size of files.
- Although the DUMP command copies the
FILE BROADCAST
message with the FPL, the RESTORE command leaves the current BROADCAST message in the file. For example:
OPEN FPLJUNK BROADCAST FILE BROADCAST MESSAGE NUMBER ONE DUMP TO DUMPFPL OPEN FPLJUNK BROADCAST FILE BROADCAST MESSAGE NUMBER TWO RESTORE FROM DUMPFPL OPEN FPLJUNK <broadcast message number two> is displayed.