CA Repository for z/OS Modernization Guide
CA Repository for z/OS is a infrastructure and computing assets product by Broadcom. Explore technical details, modernization strategies, and migration paths below.
Product Overview
CA Repository for z/OS is a system designed to manage and report on IT assets within a z/OS mainframe environment.
The system offers an API for application access, allowing other applications to interact with the repository.
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 does CA Repository for z/OS do?
CA Repository for z/OS is a software solution designed to record and report on IT assets. It captures metadata about programs, data structures, business rules, and models, storing this information in Db2 databases for analysis and reporting.
Is this a system, application, or tool?
CA Repository for z/OS is a system designed for managing and reporting on IT assets. It provides a centralized repository for metadata and offers tools for analysis and reporting.
What types of organizations use this?
Organizations that need to manage and understand their IT assets, including programs, data structures, and business rules, find CA Repository for z/OS valuable. This includes enterprises with complex IT environments and a need for comprehensive reporting.
When should we consider CA Repository for z/OS?
A company should consider CA Repository for z/OS when it needs to gain better visibility into its IT assets, improve compliance, and streamline application development and maintenance. It is particularly useful when dealing with complex mainframe environments.
What are the alternatives to CA Repository for z/OS?
Alternatives to CA Repository for z/OS include Enterprise Meta Environment, Tivoli Application Dependency Discovery Manager (TADDM), and other mainframe discovery tools. These products offer similar capabilities for managing and reporting on IT assets.
Technical
What infrastructure is required?
CA Repository for z/OS runs on the z/OS platform and requires Db2 for storing metadata. It typically runs in an LPAR and may require specific z/OS subsystems to be active.
For mainframe products: Does this run in an LPAR?
Yes, CA Repository for z/OS runs on z/OS within an LPAR. It is dependent on the z/OS operating system and requires specific subsystems to be available.
What databases are used by CA Repository for z/OS?
CA Repository for z/OS stores metadata in Db2 databases. The specific database schema and tables used are part of the product's implementation and are used for analysis and reporting.
Does CA Repository for z/OS have an API?
CA Repository for z/OS provides an API for application access. The API allows applications to interact with the repository to retrieve and update metadata. The specific API details depend on the product's configuration.
Business Value
What is the business value of CA Repository for z/OS?
CA Repository for z/OS provides business value by improving IT asset management, enhancing compliance, and streamlining application development. It enables organizations to understand their IT landscape better and make informed decisions.
How does CA Repository for z/OS reduce business risk?
By providing a centralized repository for IT asset metadata, CA Repository for z/OS helps reduce the risks associated with outdated or inaccurate information. It also supports compliance efforts by providing a clear view of IT assets.
How does CA Repository for z/OS integrate with enterprise ecosystems?
CA Repository for z/OS integrates with enterprise ecosystems by providing an API for application access and supporting standard protocols for data exchange. This allows it to be integrated with other IT management tools and systems.
Security
What authentication methods are supported?
CA Repository for z/OS supports authentication methods such as RACF, ACF2, or Top Secret, depending on the z/OS security environment. It uses an access control model to manage user permissions and access to metadata.
What access control model is used?
CA Repository for z/OS uses an access control model to manage user permissions and access to metadata. The specific model used depends on the product's configuration and the z/OS security environment.
What audit/logging capabilities exist?
CA Repository for z/OS provides audit and logging capabilities to track user activity and changes to metadata. These logs can be used for security monitoring and compliance reporting.
Operations
What level of technical expertise is required to implement it?
Implementing CA Repository for z/OS requires technical expertise in z/OS, Db2, and IT asset management. Ongoing operational requirements include monitoring the system, performing maintenance, and managing user access.
What ongoing operational requirements exist?
Ongoing operational requirements for CA Repository for z/OS include monitoring the system for performance and availability, performing regular maintenance tasks, and managing user access and permissions.
What are common implementation challenges?
Common implementation challenges for CA Repository for z/OS include integrating it with existing systems, configuring it to meet specific business requirements, and ensuring that the metadata is accurate and up-to-date.
Ready to Start Your Migration?
Download our comprehensive migration guide for CA Repository for z/OS or calculate your ROI.