Overview of configuring RUV

RUV provides quick and easy VSAM data recovery processing. With RUV you can focus on the data that you are recovering, not on the process that recovers the data. You can use RUV to recover VSAM data sets in the following situations:

• Physical VSAM data is lost or damaged, which may occur for the following reasons:
  • A hardware failure occurred.
  • A part of a DASD is not readable.
  • The data was deleted.
  • A natural disaster, such as a fire or a storm, occurred.
• Logical data integrity is lost, which may occur for the following reasons:
  • An application error occurred.

  • A failure occurred during CICS transaction backout.

    Warning

    Note

    Loss of logical data integrity occurs when a CICS application incorrectly updates your VSAM spheres. CICS transaction backout maintains logical data integrity by backing out partially completed transactions from VSAM data sets. For example, if I/O errors occur as CICS accesses a VSAM data set, transaction backout will fail.

RUV recovers your damaged VSAM data sets if these situations occur. RUV recovers all updates that were made before the problem occurred. Recovery is a sequence of tasks that begins with the last usable backup and may include logs, journals, and archival data sets. Recovery is complete when data has been recovered and processing capability has been restored.

Before you start RUV, see the following installation topics:

• Proper security setup, see Setting-up-security.
• Customizing RUV for different implementation scenarios, see Performing-implementation-tasks.
• Installing and implementing the SNAPSHOT UPGRADE FEATURE (SUF), see Installing-and-implementing-the-SNAPSHOT-UPGRADE-FEATURE-product.
• Verifying your RUV installation, see Using-the-installation-verification-procedure.
• Using rule sets on Using-rule-sets.