Reliant Modernization Guide

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.

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.

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

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

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.

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.

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.

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

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.

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.

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

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.

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.

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.

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.

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.

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

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.