Broadcom z/OS

CA Solve:Central Modernization Guide

Change ManagementInfrastructure and Computing AssetsAdministrationData Management

CA Solve:Central is a change management product by Broadcom. Explore technical details, modernization strategies, and migration paths below.

Product Overview

CA Solve:Central is a comprehensive systems management solution designed for z/OS mainframe environments.

The product integrates with existing security systems such as RACF, ACF2, and Top Secret.

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 Solve:Central do?

CA Solve:Central is a z/OS-based systems management solution that consolidates asset, problem, configuration, and change management functionalities. It provides a centralized platform for managing and maintaining z/OS environments, offering both 3270 and web-based access.

Is this a system, application, or tool?

CA Solve:Central is a comprehensive systems management toolset designed for z/OS environments. It integrates multiple functionalities into a single platform, providing a holistic view of the mainframe environment.

What types of organizations use this?

Organizations that rely on z/OS mainframe environments, particularly those in industries like banking, finance, insurance, and government, commonly use CA Solve:Central. These organizations require robust systems management capabilities to maintain stability, security, and compliance.

When should we consider CA Solve:Central?

A company should consider CA Solve:Central when it needs a centralized and integrated solution for managing its z/OS environment. This includes scenarios where asset tracking, problem resolution, configuration control, and change management are critical for maintaining operational efficiency and minimizing downtime.

What are the alternatives to CA Solve:Central?

Alternatives to CA Solve:Central include other mainframe systems management solutions such as IBM Z System Automation, BMC AMI Ops, and Compuware Topaz. These products offer similar capabilities for managing and automating z/OS environments.

Technical

What infrastructure is required?

CA Solve:Central requires a z/OS environment to operate. It typically runs within an LPAR and may depend on specific z/OS subsystems for certain functionalities. The product integrates with existing mainframe infrastructure components.

For mainframe products: Does this run in an LPAR?

Yes, CA Solve:Central is z/OS dependent and designed to run within a z/OS environment. It leverages z/OS services and subsystems for its core functionalities.

How does CA Solve:Central integrate its components?

CA Solve:Central integrates asset, problem, configuration, and change management into a unified solution. It leverages a common repository and shared services to provide a consistent and coordinated approach to systems management.

What interfaces are available for accessing CA Solve:Central?

CA Solve:Central provides both 3270 and web-based interfaces for accessing its functionalities. The 3270 interface is a traditional mainframe interface, while the web interface offers a more modern and user-friendly experience.

Business Value

How does CA Solve:Central provide business value?

CA Solve:Central helps organizations reduce operational costs by automating systems management tasks, improving problem resolution times, and optimizing resource utilization. It also enhances compliance by providing detailed audit trails and configuration tracking.

How does CA Solve:Central improve decision-making?

By providing a centralized view of the z/OS environment, CA Solve:Central enables organizations to make more informed decisions about resource allocation, capacity planning, and change management. This leads to improved efficiency and reduced risk.

What happens if an organization does not use CA Solve:Central?

Without CA Solve:Central, organizations may face challenges in effectively managing their z/OS environments. This can lead to increased downtime, higher operational costs, and greater risk of compliance violations. Manual processes and fragmented tools can also hinder problem resolution and change management efforts.

Security

What authentication methods are supported?

CA Solve:Central supports various authentication methods, including standard z/OS security mechanisms like RACF, ACF2, and Top Secret. It integrates with these security systems to control access to resources and functionalities.

What access control model is used?

CA Solve:Central uses an access control model based on roles and permissions. Users are assigned roles that define their access privileges to specific resources and functionalities. This ensures that only authorized personnel can perform sensitive operations.

What audit/logging capabilities exist?

CA Solve:Central provides comprehensive audit logging capabilities to track user activities and system events. These logs can be used to monitor security breaches, identify unauthorized access attempts, and ensure compliance with regulatory requirements.

Operations

What level of technical expertise is required to implement CA Solve:Central?

Implementing CA Solve:Central requires expertise in z/OS systems management and mainframe technologies. It involves configuring the product to integrate with existing security systems, defining user roles and permissions, and customizing workflows to meet specific business requirements.

What ongoing operational requirements exist?

Ongoing operational requirements for CA Solve:Central include monitoring system performance, maintaining the product's configuration, and applying updates and patches. Regular backups and disaster recovery planning are also essential to ensure business continuity.

What are common implementation challenges?

Common implementation challenges include integrating CA Solve:Central with existing security systems, customizing workflows to meet specific business requirements, and ensuring that the product is properly configured to monitor and manage the z/OS environment effectively.

Ready to Start Your Migration?

Download our comprehensive migration guide for CA Solve:Central or calculate your ROI.

Calculate ROI