Skip to Content
Information
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.

Assumptions about the IMS, DB2, and VSAM processes

The IMS, DB2, and VSAM processes make the following assumptions:

  • You are running the BMC AMI Recovery for VSAM (RUV) product, which was formerly known as the VSAM Recovery Services (VRS) product from Defining the Moment or as the BMC AMI Recovery for VSAM product, at the local and DR sites.
  • You are using the RUV Batch Journaling function and retaining the logs, or you are running RUV backups after batch updates.
  • You are using standard RUV backups.
  • You are using Transaction Server 1.2 or later. (CICS 4.1 is supported, but the process would be different.)
  • The coordination driver is IMS in this example. The process is a little different if you are using DB2 and VSAM without IMS.
  • The following processes include sample JCL references, which are included at the end of this topic. These samples include the RUV commands needed to implement the process, but these commands must be modified to fit your particular implementation standards and requirements and require additional RUV configuration (such as defining your VSAM files, groups, and output models).


Related topic

Add-CICS-VSAM-to-the-coordinated-recovery-process

 

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

RECOVERY MANAGER for IMS 5.1