Broadcom z/VM

CA VM:Schedule Modernization Guide

BatchAutomation

CA VM:Schedule is a batch product by Broadcom. Explore technical details, modernization strategies, and migration paths below.

Product Overview

CA VM:Schedule automates batch job scheduling and workload management on z/VM systems.

Security is managed through LDAP authentication and role-based access control (RBAC).

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 VM:Schedule and what does it do?

CA VM:Schedule automates job scheduling and workload management on z/VM systems. It allows users to define, schedule, and monitor batch jobs, ensuring efficient resource utilization and timely completion of tasks.

How does CA VM:Schedule manage job schedules and resource allocations?

CA VM:Schedule uses configuration files to define job schedules, resource allocations, and dependencies. These files specify when jobs should run, which resources they require, and how they relate to other jobs in the system.

What are the main components of CA VM:Schedule?

The main components include the Scheduler, which manages job execution; the Event Manager, which handles event-based scheduling; and the Monitor, which provides real-time status updates. These components work together to ensure jobs are executed according to defined schedules and dependencies.

How does CA VM:Schedule handle security and access control?

CA VM:Schedule supports various authentication methods, including LDAP and integration with z/VM security systems. Access control is managed through a role-based access control (RBAC) model, allowing administrators to define roles and assign permissions to users based on their responsibilities.

Technical

What are some common commands and their syntax?

Common commands include DEFINE JOB to create a new job, SCHEDULE JOB to set a job's schedule, and MONITOR JOB to track its progress. The syntax for defining a job involves specifying its name, execution parameters, and dependencies.

What types of APIs does CA VM:Schedule expose?

CA VM:Schedule exposes APIs for integration with other systems, allowing programmatic control over job scheduling and monitoring. These APIs typically use protocols like TCP/IP for communication.

How do the system components communicate with each other?

The system components communicate through internal messaging and shared storage. The Scheduler relies on the Event Manager to trigger jobs based on defined events, and the Monitor provides real-time status updates by querying the Scheduler's internal state.

What databases or storage mechanisms are used?

CA VM:Schedule uses VSAM datasets to store job definitions, schedules, and historical data. These datasets are critical for maintaining the system's state and ensuring jobs are executed according to defined parameters.

Business Value

How does CA VM:Schedule improve operational efficiency?

By automating job scheduling, CA VM:Schedule reduces manual effort, minimizes errors, and ensures timely completion of critical tasks. This leads to improved operational efficiency and better resource utilization.

How does CA VM:Schedule help organizations meet SLAs?

CA VM:Schedule helps organizations meet SLAs by ensuring that jobs are executed according to defined schedules and priorities. This reduces the risk of delays and ensures that critical tasks are completed on time.

What monitoring and reporting capabilities are available?

The product provides real-time monitoring and reporting capabilities, allowing users to track job progress, identify potential issues, and take corrective actions. This ensures that jobs are executed smoothly and efficiently.

Security

What authentication methods are supported?

CA VM:Schedule supports authentication via LDAP, allowing integration with existing directory services. It also supports integration with z/VM security systems for authentication.

What access control model is used?

The product uses a role-based access control (RBAC) model, allowing administrators to define roles and assign permissions to users based on their responsibilities. This ensures that users only have access to the resources and functions they need.

What audit/logging capabilities exist?

CA VM:Schedule provides audit logging capabilities, allowing administrators to track user activity and system events. This helps organizations meet compliance requirements and identify potential security breaches.

Operations

What administrative interfaces are available?

The administrative interface is primarily command-line based, allowing administrators to manage job schedules, user access, and system configuration. There may also be a web-based console for monitoring and reporting.

How is user management handled?

User management is handled through the command-line interface, allowing administrators to create, modify, and delete user accounts. Access control is managed through the RBAC model.

What monitoring/logging capabilities exist?

Monitoring and logging capabilities include real-time status updates, historical data analysis, and audit logging. These features help administrators track system performance, identify potential issues, and ensure compliance with security policies.

Ready to Start Your Migration?

Download our comprehensive migration guide for CA VM:Schedule or calculate your ROI.

Calculate ROI