CA Faver Modernization Guide
CA Faver is a files and datasets (vsam) product by Broadcom. Explore technical details, modernization strategies, and migration paths below.
Product Overview
CA Faver is a high-speed VSAM dataset backup and restore utility for z/OS and zVSE/VSEn environments.
For example, `FAVER BACKUP DATASET(input.dataset) OUTDATASET(backup.dataset)` creates a backup.
Modernization Strategies
Rehost
- Timeline:
- 6-12 months
Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.
Refactor (Recommended)
- Timeline:
- 18-24 months
Optimize application architecture for cloud while preserving business logic. Best ROI long-term.
Replatform
- Timeline:
- 3-5 years
Complete rewrite to cloud-native architecture with microservices and modern tech stack.
Frequently Asked Questions
General
What is CA Faver and what problem does it solve?
CA Faver is a high-speed backup and restore utility specifically designed for VSAM datasets on z/OS and zVSE/VSEn platforms. It focuses on efficient data transfer and includes features for automatic IDCAMS statement generation to simplify dataset recreation after restoration.
How does CA Faver compare to standard IDCAMS utilities for VSAM data management?
While both products handle VSAM data, CA Faver specializes in high-speed backup and restore, often outperforming standard IDCAMS utilities in terms of speed and resource utilization. It also automates IDCAMS statement generation, reducing manual effort.
How do I interact with CA Faver?
CA Faver primarily uses its own command-line interface (CLI) for operation. Configuration files are used to define parameters for backup and restore jobs, including dataset names, storage attributes, and IDCAMS generation options.
Technical
What are the most common tasks performed with CA Faver?
Common operations include backing up VSAM datasets (using a command like `FAVER BACKUP`), restoring VSAM datasets (`FAVER RESTORE`), and generating IDCAMS control statements for dataset recreation (`FAVER IDCAMS`).
What is the basic syntax for backup and restore operations?
A basic backup operation uses the syntax: `FAVER BACKUP DATASET(input.dataset.name) OUTDATASET(output.backup.name)`. A restore operation uses: `FAVER RESTORE DATASET(output.backup.name) OUTDATASET(target.dataset.name)`.
Does CA Faver have an API for integration with other systems?
CA Faver does not typically expose APIs like REST or SOAP. Integration is usually achieved through batch jobs and JCL, invoking the FAVER commands directly. Some sites might develop custom REXX scripts to automate tasks.
What are the main components of the CA Faver architecture?
The main components include the FAVER executable itself, configuration files defining job parameters, and the IDCAMS utility (invoked for dataset creation).
Business Value
What is the business value of using CA Faver?
CA Faver reduces the time required for VSAM dataset backup and restore, minimizing downtime. The automatic IDCAMS generation feature simplifies dataset recreation, reducing manual effort and potential errors.
How does CA Faver help with disaster recovery planning?
By providing faster backup and restore capabilities, CA Faver helps organizations meet their recovery time objectives (RTOs) and recovery point objectives (RPOs) for critical VSAM datasets.
Security
How does CA Faver handle security?
CA Faver leverages the security features of the z/OS and zVSE/VSEn operating systems. Access to datasets and the ability to execute FAVER commands are controlled through standard RACF or similar security systems.
What authentication methods are supported?
CA Faver integrates with existing z/OS security systems like RACF for authentication and authorization. It does not implement its own user management system.
What access control model is used?
CA Faver relies on the underlying operating system's access control mechanisms (e.g., RACF ACLs on z/OS) to control access to datasets and the FAVER utility itself.
Operations
What monitoring and logging capabilities exist?
CA Faver provides logging capabilities to track backup and restore operations. These logs can be used for auditing and troubleshooting. The logs typically record dataset names, timestamps, and completion status.
What administrative interfaces are available?
Administration is primarily performed through the command-line interface (CLI) and configuration files. There is no dedicated GUI or web console.
What are the main configuration parameters?
Key configuration parameters include dataset names for backup and restore operations, storage attributes for restored datasets, and options for IDCAMS statement generation.
Ready to Start Your Migration?
Download our comprehensive migration guide for CA Faver or calculate your ROI.