Broadcom z/OS

CA ASM2 Modernization Guide

ArchiveBackup and RestoreFiles and DatasetsAutomation

CA ASM2 is a archive product by Broadcom. Explore technical details, modernization strategies, and migration paths below.

Product Overview

CA ASM2 automates dataset management on z/OS systems, handling backup, archive, and recovery.

For example, a JCL job might include: ```jcl //BACKUPDS JOB ... //STEP1 EXEC PGM=ASM2UTIL //SYSTSIN DD * BACKUP DATASET('your.dataset.name') - OUTDATASET('backup.dataset') /* ``` Security integrates with z/OS security systems like RACF.

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 the primary function of CA ASM2?

CA ASM2 automates dataset backup, archive, and recovery on z/OS systems. It manages storage hierarchies and automates migration between storage tiers.

How is CA ASM2 configured and managed?

CA ASM2 uses control datasets to store configuration information. The primary interface is through JCL (Job Control Language) and batch processing.

What are the main system components of CA ASM2?

The main components include the ASM2 address space, control datasets, and associated utilities for data movement and management.

How does CA ASM2 integrate with z/OS security?

CA ASM2 supports standard z/OS security mechanisms, including RACF, ACF2, and Top Secret, for controlling access to datasets and functions.

Technical

What are the most common commands in CA ASM2?

Common commands include BACKUP to create backups, RESTORE to recover datasets, ARCHIVE to migrate data to archive storage, and RECALL to bring archived data back online. These commands are typically invoked through JCL.

What is the syntax for basic operations like backup?

Basic syntax involves specifying the command (e.g., BACKUP), dataset names, and options within a JCL job step. For example: //BACKUPDS JOB ... //STEP1 EXEC PGM=ASM2UTIL //SYSTSIN DD * BACKUP DATASET(‘your.dataset.name’) - OUTDATASET(‘backup.dataset’) /*

Does CA ASM2 have APIs for integration?

CA ASM2 does not expose REST or SOAP APIs. Integration is typically achieved through JCL and batch processing, or through custom programs that interact with CA ASM2 control datasets.

What are the key architectural components?

The main components are the ASM2 address space, which manages the archiving and backup processes; control datasets, which store configuration and metadata; and utility programs, which perform the actual data movement.

Business Value

How does CA ASM2 provide business value?

CA ASM2 helps reduce storage costs by automatically migrating infrequently accessed data to lower-cost storage tiers. It also improves data availability through automated backup and recovery processes.

How does CA ASM2 improve operational efficiency?

By automating data management tasks, CA ASM2 reduces the need for manual intervention, freeing up IT staff to focus on other priorities.

How does CA ASM2 support business continuity?

CA ASM2 ensures data is protected and recoverable, minimizing the impact of data loss events and supporting business continuity.

Security

What security features does CA ASM2 offer?

CA ASM2 leverages z/OS security features, including RACF, ACF2, and Top Secret, to control access to datasets and functions. It supports granular access control based on user roles and permissions.

How does CA ASM2 handle authentication?

CA ASM2 integrates with z/OS security systems to authenticate users and authorize access to datasets and functions. It supports multi-factor authentication methods supported by the underlying z/OS security system.

Does CA ASM2 provide audit logging?

CA ASM2 provides audit trails of all data management activities, including backups, archives, and restores. These logs can be used for security monitoring and compliance reporting.

Operations

How is CA ASM2 administered?

CA ASM2 is administered through JCL and batch processing. Configuration parameters are stored in control datasets, which can be updated using standard z/OS utilities.

What monitoring capabilities does CA ASM2 have?

CA ASM2 provides monitoring capabilities through SMF (System Management Facilities) records and log files. These records can be used to track system performance and identify potential issues.

What are the regular maintenance tasks for CA ASM2?

Regular maintenance tasks include reviewing log files, monitoring storage utilization, and updating configuration parameters as needed. It is also important to ensure that the control datasets are backed up regularly.

How do you troubleshoot CA ASM2 issues?

Troubleshooting involves reviewing log files and SMF records to identify the root cause of issues. Common problems include insufficient storage space, incorrect configuration parameters, and security violations.

Ready to Start Your Migration?

Download our comprehensive migration guide for CA ASM2 or calculate your ROI.

Calculate ROI