What were the common commands and syntax used in Recovery Plus for VSAM?

The product's command structure would have included commands to start and stop journaling, define datasets for journaling, and initiate the recovery process. Specific syntax details are unavailable due to the product's status.

What were the main system components of Recovery Plus for VSAM?

The architecture likely included components for intercepting VSAM I/O, writing to the journal, and reading from the journal during recovery. Specific component names are unavailable.

What types of APIs and integration methods were supported?

The product would have used native interfaces for integration with z/OS systems. Specific API details are unavailable due to the product's status.

What was the business value of using Recovery Plus for VSAM?

Recovery Plus for VSAM provided a means to protect VSAM datasets accessed by batch applications. This allowed for point-in-time recovery, minimizing data loss and downtime.

How did Recovery Plus for VSAM contribute to business continuity?

By enabling forward recovery, Recovery Plus for VSAM helped organizations maintain data integrity and availability. This was crucial for business continuity.

How did Recovery Plus for VSAM minimize the risk of data loss?

The product's ability to recover data from a specific point in time reduced the impact of data corruption or accidental deletion, minimizing the risk of data loss.

What security features were included in Recovery Plus for VSAM?

Specific security features are unavailable. However, the product likely integrated with z/OS security features for access control.

What authentication, access control, and encryption methods were used?

Details on authentication methods, access control models, and encryption are unavailable due to the product's status.

What audit and logging capabilities were available?

Audit and logging capabilities would have been present to track journaling and recovery operations. Specific details are unavailable.

What administrative interfaces were available?

Administrative interfaces would have included options for starting and stopping journaling, managing journal datasets, and initiating recovery processes. Specific details are unavailable.

How was user management handled?

User management would have been handled through z/OS security mechanisms. Specific details are unavailable.

What were the main configuration parameters?

Configuration parameters would have included dataset definitions, journal file locations, and recovery options. Specific details are unavailable.

What monitoring capabilities existed?

Monitoring capabilities would have included the ability to track journaling activity and the status of journal datasets. Specific details are unavailable.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Recovery Plus for VSAM

BMC Not Supported z/OS

Files and Datasets (VSAM) Backup and Restore

Vendor

BMC

Product Overview

Recovery Plus for VSAM, formerly DRS/Batch, provided a journaling solution for VSAM datasets accessed by batch applications. The architecture likely included the following components: a VSAM I/O interceptor, a journaling component, and a recovery component. The VSAM I/O interceptor would have captured changes to VSAM datasets.

The journaling component would have written these changes to journal datasets. The recovery component would have read the journal datasets and applied the changes to restore the VSAM datasets. Configuration files would have been used to define the datasets to be journaled, the location of the journal files, and other operational parameters.

The product is no longer supported. When migrating, consider the architecture of the new solution to ensure compatibility with your existing z/OS environment. Evaluate the features and capabilities of each solution to meet your specific needs.

Consider the API and integration methods of the new solution to ensure compatibility with existing applications. Ensure that the new solution integrates seamlessly with your existing z/OS environment.

Frequently Asked Questions

What is the primary function of Recovery Plus for VSAM?

Recovery Plus for VSAM was designed to journal VSAM datasets for batch applications. This journaling enabled forward recovery of datasets. The product was originally developed by Integrity Solutions as DRS/Batch, and later acquired by BMC.

How did Recovery Plus for VSAM facilitate data recovery?

Recovery Plus for VSAM provided a mechanism to capture changes made to VSAM datasets. These changes were written to a journal, which could then be used to restore the datasets to a point in time. This process is known as forward recovery.

What is the history of Recovery Plus for VSAM?

The product was initially known as DRS/Batch, developed by Integrity Solutions. BMC acquired Integrity Solutions in 1990 and renamed the product Recovery Plus for VSAM. Eventually, it was merged into Recovery Plus for CICS/VSAM.

What types of applications did Recovery Plus for VSAM support?

Recovery Plus for VSAM was designed to work with batch applications accessing VSAM datasets. It provided a way to protect and recover data used by these applications.

Related Products

View Details →

Application Restart Control for VSAM

Supported

by BMC

z/OS

Alternatives available

Application Restart Control for VSAM enhances batch processing by enabling checkpointing and restart capabilities for applications accessing VSAM datasets. The Checkpoint Manager, VSAM Interceptor, and...

Files and Datasets (VSAM) Problem Analysis and Recovery