What configuration files are used by Reliant?

The primary configuration file is the Reliant control file, which defines journaling parameters, dataset associations, and recovery options. This file is read during initialization and recovery processes.

How does Reliant capture VSAM dataset changes?

Reliant intercepts VSAM I/O requests using VSAM intercept routines. These routines capture changes before and after they are applied to the VSAM dataset, writing the information to the journal.

How does the recovery process work?

The recovery process uses the backup copy of the VSAM dataset and the journal file. The recovery utility applies the journal records to the backup, restoring the dataset to the desired point in time. The JRNLSCAN utility can be used to examine the journal contents.

What utilities are provided for managing and recovering VSAM datasets?

Reliant provides utilities such as JRNLSCAN to examine the journal contents and VRR to perform VSAM dataset recovery.

What business value does Reliant provide?

Reliant ensures data consistency and integrity in VSAM datasets, reducing the risk of data loss due to application errors or system failures. This leads to improved business continuity and reduced downtime.

How does Reliant improve recovery times?

By providing point-in-time recovery, Reliant minimizes data loss and reduces the time required to restore VSAM datasets. This ensures that critical business applications remain available.

How does Reliant integrate with existing backup processes?

Reliant integrates with existing backup and recovery procedures, minimizing disruption to existing operations. This allows organizations to leverage their existing investments in backup infrastructure.

How does Reliant integrate with z/OS security systems?

Reliant integrates with z/OS security systems such as RACF, ACF2, and Top Secret to control access to VSAM datasets and journal files. This ensures that only authorized users can access sensitive data.

What access control models are supported by Reliant?

Reliant supports standard z/OS security features, including access control lists (ACLs) and role-based access control (RBAC), to restrict access to VSAM datasets and journal files.

What audit logging capabilities exist?

Reliant provides audit logging capabilities to track access to VSAM datasets and journal files. These logs can be used to monitor security events and identify potential security breaches.

What administrative interfaces are available?

Reliant provides a command-line interface (CLI) for administrative tasks such as configuring journaling parameters, managing journal files, and performing recovery operations. The control file is the primary interface for configuration.

What monitoring and logging capabilities exist?

Reliant integrates with z/OS system management facilities (SMF) to provide monitoring and logging information. This allows organizations to monitor the performance and health of Reliant.

What utilities are used for backup and recovery?

Reliant uses standard z/OS utilities for backup and recovery, such as DFSMSdss. This allows organizations to leverage their existing backup infrastructure.

What are the storage requirements for Reliant?

Reliant requires sufficient disk space for journal files and backup copies of VSAM datasets. The amount of disk space required depends on the size of the VSAM datasets and the frequency of updates.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Reliant

Name: Reliant
Availability: InStock

CSI International Active z/OS zVSE/VSEn

Files and Datasets (VSAM) Backup and Restore

Vendor

CSI International

Product Overview

Reliant provides VSAM journaling capabilities for z/OS and z/VSE, enabling point-in-time recovery. It captures VSAM file updates in a journal, allowing restoration to any point using backups and journals. Key features include support for VSAM ESDS, KSDS, and RRDS datasets, integration with z/OS security systems (RACF, ACF2, Top Secret), and utilities for managing and recovering VSAM datasets.

Reliant's architecture includes the Journaling Subsystem, VSAM intercept routines, and recovery utilities. VSAM I/O requests are intercepted using VSAM intercept routines, which capture changes before and after they are applied to the VSAM dataset, writing the information to the journal. The Journaling Subsystem manages the journal files and ensures that journal records are written in the correct sequence.

The recovery utilities use the backup copy of the VSAM dataset and the journal file to restore the dataset to the desired point in time. The Reliant control file is used to configure journaling parameters and dataset associations. The JRNLSCAN utility allows examination of journal contents, and the VRR utility performs VSAM dataset recovery.

Reliant integrates with existing backup and recovery procedures and z/OS system management facilities (SMF) for monitoring and logging. Competing products include CA Datacom.

Frequently Asked Questions

What is the core functionality of Reliant?

Reliant journals VSAM file updates, enabling point-in-time recovery. Backups combined with journals allow restoration to a specific point. It supports batch and online transaction processing (OLTP) environments.

How does Reliant achieve point-in-time recovery?

Reliant uses a journal file to record changes to VSAM datasets. During recovery, these journal records are applied to a backup copy of the VSAM dataset to restore it to a specific point in time.

What types of VSAM datasets are supported?

Reliant supports VSAM ESDS, KSDS, and RRDS datasets. It integrates with existing backup and recovery procedures.

What are the main architectural components of Reliant?

Reliant's architecture includes the Journaling Subsystem, VSAM intercept routines, and recovery utilities. These components work together to capture changes and restore VSAM datasets.

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

View Details →

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience