Skip to Content

Recovering to alternate data sets

The Recovery utility provides enhanced techniques that you can use to recover a database to alternate data sets, in effect creating a functional duplicate of your production database.

You can use the alternate data sets for a variety of shadow, testing, and backup purposes. These enhanced techniques support full function, HALDB, and Fast Path databases.

Related topics

Specifying-the-database-data-sets

To recover a database to alternate data sets without these enhanced techniques, you must create an MDA member to define the alternate data set name for each database to be recovered, or you must allocate the new (alternate) data set in the JCL. For a HALDB, you must pre-allocate each new (alternate) data set group (DSG), indirect list data set (ILDS), and index in the JCL.

With these enhanced techniques, you can expend a minimal effort to recover a database to alternate data sets:

  • You can specify the DBDEF control statement to define how the utility should resolve the substitution variables and apply the data set name mask.
  • You can specify substitution variables in AMSPDS members.
  • You can specify data set name masks by using the ALTDBNAM keyword in the DBDEF control statement.

The Recovery utility also incorporates validation logic to ensure that production databases are not destroyed inadvertently during an AUTH(N) recovery process.

This section contains the following topics: 

 

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

BMC AMI Backup and Recovery for IMS 5.2