Space announcement We are no longer updating this space, and you cannot comment on this space. The RECOVERY MANAGER for IMS component is now documented in BMC AMI Backup and Recovery for IMS.

Recover to alternate databases (Create Recovery JCL function)

If you are using the BMC Recovery utility, you can use the Create Recovery JCL function to recover databases to alternate database data sets.

You can also use the Index Rebuild function to rebuild indexes for alternate full-function, HALDB, or Fast Path databases. You can use the resulting alternate databases for testing and other purposes.

Note

You cannot request a simulated recovery and recovery to alternate databases at the same time.

When you choose a recovery to alternate databases, there is no need to stop the original databases during the execution of the Create Recovery JCL function. Therefore, the function sets the value of the DBR option (to stop the databases with a /DBR command) to NO.

The Create Recovery JCL function creates the recovery JCL with the following BMC Recovery utility keywords:

  • The DBRC(Y) keyword is required so that the Recovery utility can identify and dynamically allocate the input data sets.
  • The AUTH(N) keyword is required to bypass DBRC authorization because the recovery uses database data set names that are different from the names that are defined in the RECONs.
  • The DBALLOC(N) keyword is required to bypass dynamic allocation of the output data sets because the alternate database DD statements are hard-coded in the JCL from the information that you provide.
  • The IDCAMS(*) keyword is included if you specify that the function should obtain allocation information from the profile.

Note

You can use the Automatic Delete/Define (DRAMS) utility to create AMSPDS members with alternate data set, volume, and SMS class values.

The Create Recovery JCL function creates the JCL for the Index Rebuild function; DBRC is turned off. It creates hard-coded DD statements to allocate the alternate database indexes.

The Create Recovery JCL function does not create the following elements:

  • Steps or commands to stop the databases
  • Steps or keywords to perform an image copy after or during the recovery
  • Steps or keywords to invoke pointer checking
  • Steps or jobs to start the database after the recovery

This section contains the following topics:

Related topic

Create-and-execute-recovery-JCL

 

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