Information

This site will undergo a brief period of maintenance on Friday, 18 December at 12:30 AM Central/12:00 PM IST. During a 30 minute window, site availability may be intermittent.

FDRAPPL RESTORE Statement


RESTORE statement

The RESTORE TYPE=APPL statement invokes a restore from an Application Backup. Only one RESTORE statement is allowed per execution of FDRAPPL, but any or all of the data sets for the application can be restored in one FDRAPPL step. The ARCHIVE DD statement points to an Application Control File that contains the records of data sets that were dumped with Application Backup.

SIMREST statement

If SIMREST is specified, FDRAPPL prints the data set names that are selected and the tape volumes necessary to do the restore. A restore operation is not done. SIMREST can be used to pre-pull the required tapes, or to verify that the expected data sets are restored.

RESTORE statement syntax

RESTORE|SIMREST


TYPE=APPL


,BLKF=nn


,COPY=1|n


,DSNENQ=HAVE|NONE|TEST|USE


,DYNTAPE


,ICFCAT=ALIAS|ORIGINAL


,MAXCARDS=100|nnnn


,NOCAT|RECAT


,PRESTAGE


,SELTERR=NO|YES


,SMSGDG=ACTIVE|DEFERRED|INPUT|ROLLEDOFF


,VRECAT

RESTORE statement rarely used options

There are some additional operands that can be specified on a RESTORE statement, but they are rarely used with FDRAPPL. Their definitions are found in Archive-RESTORE-statement. They are:



,ALLOCATELIST=


,BYPASSACS


,BYPASSSMS


,CATIFALLOC


,DATA=


,EMSG=OK


,OPERATOR


,RLSE|%FREE=nnn

Application restore procedure

If the data sets being restored already exist on the selected target DASD, the restore simply overlays them with the data from the backup tape (unless PRESTAGE is specified), so there is no need to delete the data sets before restoring them. If you are restoring at your home site, the restore simply refreshes the contents of the data sets. If they do not exist, the restore allocates and catalogs them before restoring them.

The rules for selection of a target volume for each data set are detailed in “Archive Restore Procedure” in Archive-RESTORE-statement, but briefly, these tests are done in this order:

  • An NVOL= operand on the SELECT statement specifies one or more target volumes.
  • If the output data set is cataloged, FDRAPPL assumes it must exist there and uses that volume as the target.
  • The original volume serial of the data set is used.
  • The installation may specify a global RESTORE ALLOCATION LIST that provides target volume serials based on data set name and/or original volume serial.
  • If the data set is not on the first target volume, SMS may override FDRAPPL’s choice of target volume.

Restore VSAM files

FDRAPPL restores VSAM files using the base cluster name. FDRAPPL restores each individual component associated with this cluster name, and allocates VSAM files if they do not currently exist. FDRAPPL 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, FDRAPPL lets VSAM determine names for the components. Some information contained solely in the catalog, including protection (RACF or password) and expiration date is 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 statement operands

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 reblocked during the restore. DSORG=PO (partitioned) data sets use the new block size for new members. Other data set types are not reblocked.

Default: Data sets are not reblocked during restore.

COPY=

n

Specifies the copy (1 or 2) of the backup from which the restore is to be attempted. COPY=2 can be specified if a duplicate tape copy (TAPExx) was created during the backup.

Default: COPY=1 unless COPY1 has expired, then COPY2 is the default if it exists. The default can be made COPY=2 in the FDR Global Options (see “BKPCOPY” in ABR-Options); this is useful at a disaster site where the COPY2 backup is the only one available.

DSNENQ=

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:

USE

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

HAVE

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

NONE

No data set enqueue is issued.

TEST

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

Default: USE.

Warning

Important

NONE or TEST may allow other jobs to attempt to read the data set being restored before ABR has restored all of the data tracks.

Success

Tip

Use DSNENQ=USE or HAVE if you want to be sure that no other task uses the data set until the restore is complete. However, use DSNENQ=NONE when another data set by the same name on another volume may be in use (for example, restoring data sets to an alternate SYSRES volume). You may suppress enqueues for specific data sets by the DSNENQ=NONE operand on SELECT statements.

DYNTAPE

Specifies that FDRAPPL 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, which improves 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.

ICFCAT=

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

ALIAS

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

ORIGINAL

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.

ICFCAT= might be needed if an Application Backup is restored on an existing system with a different catalog structure.

MAXCARDS=

Accept additional SELECT and EXCLUDE statements (over 100).

Default: 100 statements.

NOCAT
RECAT
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.

RECAT

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.

Warning

Important

Allocation of SMS-managed data sets fails if they cannot be cataloged. If a SMS-managed data set is being restored and it is currently cataloged to another volume you can specify either RECAT or delete the data set before restore.

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.

Success

Tip

RECAT is recommended for Application Restore so that the catalog is updated if they must be restored to a new volume.

PRESTAGE

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.

Warning

Important

FDRAPPL only looks for the data set on the first target volume it selects, based on the rules at the top of this section. If the data set exists on another volume; FDRAPPL may still try to allocate it.

Default: Preallocated data sets have their contents overlaid.

SELTERR=

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

NO

A condition code or abend is not to be issued at step termination. SELTERR=NO can be used when some unmatched SELECT/EXCLUDE statements are expected, perhaps because some data sets may not exist.

YES

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 (see “SELTERR” in General-Options).

SMSGDG=

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

ACTIVE

Sets the GDG to ACTIVE status.

DEFERRED

Sets the GDG to DEFERRED status.

INPUT

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

ROLLEDOFF

Sets the GDG to ROLLEDOFF status.

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

Default: INPUT. If you want to change this default, please contact BMC Support for assistance.

VRECAT

Allows VSAM clusters to be allocated and cataloged even if they already exist in the target ICF 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 an ICF 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).

Error
Warning

VRECAT will DELETE the original cluster, with all its components, Alternate Indexes (AIXs), and PATHs, from the catalog and DASD volumes. If the DELETE fails for some reason, the DELETE NOSCRATCH may leave uncataloged components on DASD.

Success

Tip

VRECAT is recommended for Application Restore so that VSAM clusters can be restored to a new volume.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Storage FDR 6.1