Archive RESTORE statement

RESTORE statement

The RESTORE TYPE=ARC statement activates a manual restore of individual data sets that have been archived. Only one RESTORE statement is allowed per execution of ABR, but any number of data sets can be restored in one ABR step.

Simulated Restore

If Simulated Restore (SIMREST) is coded, ABR prints the data set names that are selected and the volumes necessary to do the restore. A restore operation is not done. It can be used to test RESTORE options or to pre-pull the tapes required.

RESTORE and SIMREST statements syntax

Archive restore procedure

The Archive Restore procedure restores data sets or groups of data sets that were archived by ABR. Since archived data sets usually do not exist on DASD, ABR allocates, catalogs, and restores the data set (although it restores to a preallocated data set as well). See DSF-Technical-Summary for details on how FDR allocates and catalogs data sets during restore.

ABR can also restore archived data sets automatically, when invoked from the ABR Catalog Locate exit (see ABR Catalog Locate Exit in ABR-Auto-Recall-Introduction).

Restore From Archive Backup in FDRABR-data-set-selection details how Archive Restore selects the appropriate Archive backup file on DASD or tape for each data set to be restored. If multiple data sets are to be restored from a given backup, that file is read only once. While reading a backup file, ABR can restore the selected data sets to one or more DASD volumes concurrently. The target DASD volume is selected for each data set by the following rules:

• If the NVOL= operand was specified on the SELECT statement that selected this data set, that volume or volumes is used. If NVOL= specified more than one volume serial, the first of those volumes is selected initially; allocation may be attempted on up to 64 of those volumes in turn until it is successful. If the NVOL list includes more than one type of DASD device, those with the same type as the input data set (“like” devices) are tried first. Any volumes in the NVOL list that are not online are ignored.
• If the output data set name is cataloged, then the volume to which it is cataloged is chosen. The output data set name is the original name or the new name if a NEWNAME=, NEWGROUP=, or NEWINDEX= operand was specified on the SELECT statement that selected the data set. If the data set is cataloged as being on multiple volume serials, then the volume serial number is selected from that list based on the volume sequence number in the F1 DSCB (field DS1VOLSQ) of the input data set
• If none of the above applies, then the serial of the volume from which the data set was dumped, as recorded by ABR in the Archive Control File, is used.
• If the data set was not preallocated on the selected volume, and the allocation fails on that volume for any reason, the ABR RESTORE ALLOCATION LIST, if enabled (see “Panel A.I.6 – ABR Protect Lists and Restore Allocation List in ABR-Options), is checked to see if there is an ALLOCATE statement that applies to this data set. If so, the NVOL list from that statement is used as described above for NVOL=. The RESTORE ALLOCATION LIST can be used to identify alternate volumes to which to restore data sets if their target volume is full or no longer exists.

If System Managed Storage (SMS) is active on this system, and the data set does not already exist on the volume selected by the rules above, SMS is invoked to decide if the data set should be SMS-managed. If so, SMS selects an output volume. SMS rules are detailed in SMS Support in DSF-Technical-Summary and System Managed Storage (SMS).

Restore VSAM files

ABR restores VSAM files using the base cluster name. ABR restores each individual component associated with this cluster name, and allocates VSAM files if they do not currently exist. ABR updates the appropriate fields within the VVR for each component. VSAM files except the VVDS itself are movable; except for the VVDS and catalogs they can be restored to a new name or group. If NEWGROUP= or NEWINDEX= are specified the new group name is applied to both the cluster name and all of its components. If NEWNAME= is specified for a cluster which is not allocated, ABR lets VSAM determine names for the components. Some information contained solely in the catalog, including protection (RACF or password) and expiration date are not updated. However, path names for Alternate Indexes (AIXs) and aliases of user catalogs are restored. See VSAM-Special-Considerations for a more detailed explanation.

RESTORE and SIMREST statement operands

Required to restore data sets from ABR Archive Backups. ABR attempts to restore all the data sets specified by the SELECT statements or remote queue data set.

Specifies that the ABR Restore Allocation List is not to be used for the selection of output volumes for the restore.

Default: The Restore Allocation List is used as described earlier in this section, if enabled in the FDR Global Options (see Panel A.I.6 – ABR Protect Lists and Restore Allocation List in ABR-Options).

BLKF=

nn

Changes the block size (BLKSIZE) of certain RECFM=FB and VB data sets. BLKF= specifies blocks per track (1 to 10) and calculates a new block size based on the output track size.

DSORG=PS (sequential) data sets are physically re-blocked during the restore. DSORG=PO (partitioned) data sets use the new block size for new members. Other data set types are not re-blocked.

Default: Data sets are not re-blocked during restore.

FULL – ENQs used to access the ACF or EACF continue to work as they have in previous releases of FDRABR. That is, ENQs are acquired and maintained throughout execution of the process accessing the ACF or EACF. 

LIMITED – ENQs used to access the ACF or EACF are acquired and only held as long as necessary to complete the current update. This results in an increase in the number of times ENQs are obtained and released but reduces delays experienced by other processes that required serialized access to the ACF or EACF. 

Default: FULL 

BYPASSACS

The SMS ACS (Automatic Class Selection) routines are not to be invoked for data sets that must be allocated. If a data set has an SMS storage class assigned (see STORCLAS= in SELECT-and-EXCLUDE-Statements) it is SMS-managed, and SMS is invoked to allocate the data set on an SMS chosen volume, but SMS is not allowed to override the storage class or management class assigned to the data set.

Default: On an SMS system, the SMS ACS routines are invoked for every data set that has to be allocated. The assigned storage and management classes are passed to those routines, which can approve or override them. A data set is passed to SMS for allocation if the storage class ACS routine assigns a storage class to the data set.

SMS-managed data sets are directly allocated on SMS-managed volumes, bypassing normal SMS storage group and volume selection. The selected output volume must be an SMS-managed DASD volume, and the data sets being restored must have an SMS storage class assigned (see BYPASSACS in and STORCLAS= in SELECT-and-EXCLUDE-Statements). The data sets are allocated and cataloged according to SMS standards.

Normal SMS facilities do not allow allocation of data sets on specific volume serials, but BYPASSSMS does, allowing data sets to be located for performance or other reasons.

Default: For data sets that have a storage class and must be allocated, the SMS storage group ACS routine is invoked to select a storage group and SMS selects an SMS-managed volume and allocates and catalogs the data sets.

BYPASSACS and BYPASSSMS are primarily for use by storage administration personnel, since they bypass normal SMS allocation controls and rules. In order to use BYPASSACS or BYPASSSMS, the user of ABR must be authorized to the RACF profile STGADMIN.ADR.RESTORE.BYPASSACS in class FACILITY, or the equivalent in other security systems.

Non-VSAM output data sets are cataloged even if they were preallocated (not allocated by ABR, subject to the NOCAT and RECAT operands.

Default: Output data sets are cataloged only when the restore allocates them.

n

Specifies the copy (1-9) of the backup from which the restore is to be attempted. COPY=2 can be specified if a duplicate backup (TAPExx) was created at backup time.

Default: COPY=1 unless overridden in the FDR Global Options (see BKPCOPY in ).

Specifies whether a SYSDSN enqueue should be issued for each of the data sets being restored. See Data Set Enqueue Option in FDRABR-processing-options-and-requirements for more details. If you are restoring over an existing data set and the enqueue fails, the data set is bypassed with an error message. If the restore must allocate the output data set and the enqueue fails, no error message is issued and the restore is still done. The options for DSNENQ= are:

Enqueue the data sets. If an enqueue fails, ask the operator what to do.

No data set enqueue is issued.

Do not enqueue the data sets, but test to see if they are enqueued to another task.

Enqueue the data sets. This is the most frequently used option.

Default: USE.

Specifies that ABR is to dynamically allocate the backup data sets using a ddname of TAPE#. This option should be used if the backup is on DASD, in an Automated Tape Library (ATL) or a mix of backup device types are read, such as 3490E and 3590.

DYNTAPE2 allocates two drives that improve performance when restoring from multi-volume tape backups on 3480 cartridges. DYNTAPE2 should not be used if backup files on DASD might be involved.

Default: The first TAPEx DD statement found in the step JCL is used to mount all backups. The type of device assigned must be the correct type for reading all required backups.

Used when the FDR e-mail notification facility has been invoked by including an FDREMAIL DD Statement in the FDR execution JCL.

E-mail notifications are sent from successful FDR operations as well as failures.

Default: E-mail notifications are sent only for FDR failures

Applies to VSAM files only. Specifies the source of the catalog name to be used if an output VSAM cluster must be allocated.

Determine the catalog from the alias name in the master catalog. Multi-Level Alias (MLA) is supported.

Use the catalog in which the original dumped cluster was cataloged.

Default: ORIGINAL, except that if the cluster is being restored to a new name (NEWGROUP or NEWINDEX specified) the default is ALIAS. If the output cluster is SMS-managed, ALIAS is forced.

Accept additional SELECT and EXCLUDE statements (over 100).

Default: 100 statements.

NOCAT

Specifies that output data sets are not cataloged. This option is ignored for VSAM clusters and SMS-managed data sets, since these must always be cataloged.

Specifies that non-VSAM output data sets are cataloged even if they are currently cataloged to another volume. If a data set by that name actually exists on the volume to which it is currently cataloged, and it is SMS-managed, it is deleted; otherwise, it becomes an uncataloged data set.

Default: Catalog output non-VSAM data sets only if they are not currently cataloged.

NOCAT and RECAT are mutually exclusive. The restore normally attempts to catalog only output data sets that it allocates (not preallocated) unless the CATIFALLOC operand is also specified.

Requests that an operator message FDRW24 be issued for each tape necessary to complete the restore. This option gives the operator the ability to pre-pull required tapes or bypass a tape that may not be available at this time.

Output data sets that already exist on the target output volume are not restored. This may be used to avoid restoring data sets that have already been restored. If the output data sets do not exist on the target volume, they are allocated and restored.

Default: Preallocated data sets have their contents overlaid.

ABR does not restore data sets that are marked in the Archive Control File as having been previously restored.

RLSE

%FREE=

All of the unused space in the output Physical Sequential (PS) and PO (partitioned) data sets is released.

%FREE=nn

A percentage (nn%) of the PS and PO data sets to be left free after the restore. However, the data sets are never made larger than their original size. “nn” may range from zero (0) that frees all of the free space (same as RLSE) to 99 that attempts to leave the data sets with 99% free space.

Space is released only from data sets allocated by the restore; space is actually released by recalculating the required space during the allocation.

Default: The output data sets are allocated the same size as the input data sets (unless overridden by TRK=/CYL= on the SELECT statement).

If one or more of the SELECT or EXCLUDE statements was never referenced (no data set was selected from the Archive Control File by the statement):

A condition code or abend is not to be issued at step termination. You might use SELTERR=NO when you expect some unmatched SELECT or EXCLUDE statements, perhaps because some data sets may not exist.

A condition code or abend is issued at step termination to call attention to a possible control statement error.

Default: YES, unless overridden in the FDR Global Options (for more information, see SELTERR).

Specifies the status of SMS-managed Generation Data Group (GDG) data sets, if allocated by the restore.

Sets the GDG to ACTIVE status.

Sets the GDG to DEFERRED status.

Sets the GDG to ROLLEDOFF status.

Sets the GDG to the original SMS status of the GDG generation, as recorded on the backup tape. If the original GDG was not SMS-managed, it is set ACTIVE if that generation is currently cataloged, otherwise DEFERRED.

If a GDG is restored as DEFERRED, you may need to execute an IDCAMS “ALTER ROLLIN” to make the generation active.

Default: DEFERRED, except that on automatic recall (other than via the remote queue) the default is INPUT.

VRECAT

Allows VSAM clusters to be allocated and cataloged even if they already exist in the target catalog. If an attempt to define a VSAM cluster fails with a code indicating the cluster or component name already exists in the catalog, this indicates that either the cluster currently exists on another volume or the cluster is cataloged but is not on the cataloged volume. With VRECAT, the cataloged cluster is scratched (by DELETE or, if that fails, DELETE NOSCRATCH). The define is then re-issued. VRECAT is useful when restoring a cluster when its catalog has been restored, but the cluster on DASD has not, or when restoring a cluster to a new volume.

VRECAT is ignored when:

• Restoring a catalog.
• The restore does not include the base data component (such as restoring an alternate index on a volume by itself or a volume containing only a base index component).
• Components of the cluster do exist on the volume to which FDR is restoring. In this case, FDR attempts to restore on top of those existing components and VRECAT is not involved.

Default: VSAM clusters cannot be allocated if the cluster name already exists in the catalog (even if the catalog points to the output volume).