RESTORE command: Difference between revisions

From m204wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by 2 users not shown)
Line 6: Line 6:
<dd>Restores a <var class="product">Model&nbsp;204</var> file from a dumped version of that file
<dd>Restores a <var class="product">Model&nbsp;204</var> file from a dumped version of that file
</dl>
</dl>
==Syntax==
==Syntax==
<p class="syntax">RESTORE [<i>option</i>] FROM <i>ddname</i>
<p class="syntax">RESTORE [<span class="term">option</span>] FROM <span class="term">ddname</span> [NBUFF <span class="term">I/Obuffers</span>]
</p>
</p>
   
   
<b>Where:</b>
Where:
<table>  
<table>  
<tr>
<tr>
<th>option</th>
<th>option</th>
<td> is a decimal value. Options can be summed. The options are:
<td>A decimal value. Options can be summed. The options are:
<table>
<table>
    
    
<tr> <th>
<tr class="head"> <th>Option</th>  
<p>Option</p>
<th>Meaning</th> </tr>
</th> <th>
<p>Meaning</p>
</th> </tr>
    
    
<tr> <th align="right"><var>
<tr> <th align="right"><var>128</var></th>  
<p>128</p>
<td>The size of a file data set or the number of data sets in a file is being changed. </td> </tr>
</var></th> <td>The size of a file data set or the number of data sets in a file is being changed. </td> </tr>
   
   
<tr> <th align="right"><var>
<tr> <th align="right"><var>64</var></th>  
<p>64</p>
<td>The name of a file is being changed.</td> </tr>  
</var></th> <td>
<p>The name of a file is being changed.</p>
</td> </tr>
 
</table>
</table>
</td>
</td></tr>
</tr>
   
   
<tr>
<tr>
<th>ddname</th>
<th>ddname</th>
<td> is the name of the data set from which the <var class="product">Model&nbsp;204</var> file is being restored. If the FROM <var class="term">ddname</var> clause points to a data set that was not created by the <var class="product">Model&nbsp;204</var> DUMP command, the following error messages is issued:  
<td>The name of the data set from which the <var class="product">Model&nbsp;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&nbsp;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>


Line 55: Line 54:
M204.1761: FILE CEN: RESTORE COMPLETED AT 14.29.24
M204.1761: FILE CEN: RESTORE COMPLETED AT 14.29.24
</p>
</p>
==Usage notes==
==Usage notes==
The RESTORE command restores a <var class="product">Model&nbsp;204</var> file from a dumped version of that file. RESTORE takes a sequential data set produced by a DUMP command and turns it into a <var class="product">Model&nbsp;204</var> file again.
<ul>
<p class="note"><b>Note:</b> 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.</p>
<li>The <var>RESTORE</var> command restores a <var class="product">Model&nbsp;204</var> file from a dumped version of that file. <var>RESTORE</var> takes a sequential data set produced by a <var>[[DUMP command|DUMP]]</var> command and turns it into a <var class="product">Model&nbsp;204</var> file again.
<p>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.</p>
<p class="note"><b>Note:</b> Before using the <var>RESTORE</var> (or <var>[[REGENERATE command|REGENERATE]]</var>) command, you need to have <var>DUMP</var> copies of the files. <var>DUMP</var> processing updates the file while making a backup copy (to a target media). Otherwise, when you do a media recovery using either <var>RESTORE</var> (which does not include journals) or <var>REGENERATE</var> (to include journals), the backup copy does not incorporate all updates, and you cannot detect this.</p></li>
<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. Under a security interface, you must have READ privileges to read a file specified by this command. For more information, refer to the <var>Model&nbsp;204 Security Interfaces Manual</var>.</p>
 
<p>If a file is skewed, the file can only be transferred from one device type to another through the <var class="product">Model&nbsp;204</var> DUMP/RESTORE facility. For a complete discussion of the obsolete skewing feature, refer to the "File skewing" section in the <var class="book">Model&nbsp;204 File Manager's Guide</var>.</p>
<li>The <var>RESTORE</var> 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.</li>
<p>When RESTORE has finished processing, it automatically closes all private or semi-public files. Public files remain open.</p>
 
<p>When it processes RESTORE, <var class="product">Model&nbsp;204</var> ends any update unit in progress and begins a non-backoutable update unit. For more information about <var class="product">Model&nbsp;204</var> update units, see the <var class="book">Model&nbsp;204 File Manager's Guide</var>.</p>
<li>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 [[:Category:Security interfaces|Security interfaces]] pages.</li>
<p>After <var class="product">Model&nbsp;204</var> starts to restore a file, it displays a message showing the date and time the file was dumped. The <var>Rocket Model&nbsp;204 File Manager's Guide</var> discusses the RESTORE options, along with a full presentation of DUMP, RESTORE, and their use in moving, renaming, and changing the size of files.</p>
 
<p>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:</p>
<li>If a file is skewed, the file can only be transferred from one device type to another through the <var class="product">Model&nbsp;204</var> DUMP/RESTORE facility. File skewing is an obsolete feature.</li>
 
<li>When <var>RESTORE</var> has finished processing, it automatically closes all private or semi-public files. Public files remain open.</li>
 
<li>When it processes <var>RESTORE</var>, <var class="product">Model&nbsp;204</var> ends any [[File integrity and recovery#Update units and transactions|update unit]] in progress and begins a non-backoutable update unit. </li>
 
<li>After <var class="product">Model&nbsp;204</var> starts to restore a file, it displays a message showing the date and time the file was dumped. [[File dumping and restoring]] discusses the <var>RESTORE</var> options, along with a full presentation of <var>DUMP</var>, <var>RESTORE</var>, and their use in moving, renaming, and changing the size of files.</li>
 
<li>Although the <var>DUMP</var> command copies the <code>FILE BROADCAST</code> message with the FPL, the <var>RESTORE</var> command leaves the current <var>[[BROADCAST command: Sending a file message|BROADCAST]]</var> message in the file. For example:</li>
<p class="code">OPEN FPLJUNK
<p class="code">OPEN FPLJUNK
BROADCAST FILE BROADCAST MESSAGE NUMBER ONE
BROADCAST FILE BROADCAST MESSAGE NUMBER ONE
DUMP TO DUMPFPL
DUMP TO DUMPFPL
OPEN FPLJUNK
OPEN FPLJUNK
BROADCAST FILE BRAODCAST MESSAGE NUMBER 2
BROADCAST FILE BROADCAST MESSAGE NUMBER TWO
RESTORE FROM DUMPFPL
RESTORE FROM DUMPFPL
OPEN FPLJUNK
OPEN FPLJUNK
&lt;broadcast message number two> is displayed.
&lt;broadcast message number two> is displayed.
</p>
</p></li>
</ul>
 
[[Category: File manager commands]]
[[Category: File manager commands]]
[[Category:Commands]]
[[Category:Commands]]

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:
Option Meaning
128 The size of a file data set or the number of data sets in a file is being changed.
64 The name of a file is being changed.
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.