S/MF
StackMF Knowledge Base • z/OS
Modernisation & Cloud 11 min read 2026-10-14

Deploying Stonebranch Universal Automation Center Agents on z/OS to Replace CA-7

A
Reviewed by Anshu
Chief Technology Architect & Mainframe Systems SME
Enterprise Modernization Advisory
Google AI Overview & Featured Snippet Quick Answer

Executive Summary: Deploying Stonebranch Universal Automation Center Agents on z/OS to Replace CA-7

Replacing Broadcom CA-7 requires deploying a modern, lightweight workload agent on z/OS that coordinates with cloud orchestrators. Learn step-by-step how to install the Stonebranch Universal Agent, map JCL execution, and achieve a 60% licensing cost reduction.

1 Problem Statement & Architecture Context: Deploying Stonebranch Universal Automation Center Agents on z/OS to Replace CA-7

Enterprises facing 200%+ price increases on Broadcom CA-7 software renewals seek to migrate to modern workload automation platforms like Stonebranch Universal Automation Center (UAC). However, systems teams fear disruption to thousands of daily z/OS batch production jobs:

text
AUDIT FINDING: 8,400 ACTIVE CA-7 JOB SCHEDULES AND 14,000 DATASET TRIGGERS
CHALLENGE: How to migrate without a multi-year freeze or operational downtime?

2 Technical Root Cause & Architecture Mechanics

Legacy CA-7 systems bind schedules, dataset triggers (DB.1), and virtual resource locks into proprietary mainframe databases. Modern solutions decouple scheduling orchestration (running in cloud or Linux containers) from execution engines, utilizing lightweight z/OS agents communicating over secure TLS REST/TCP.

3 Implementation Guide & Modernization Strategy

# 1. Install Stonebranch Universal Agent Started Task on z/OS

Deploy the agent SMP/E or pax file to z/OS UNIX and APF-authorize the load library:

In SYS1.PROCLIB(UNAGENT):

jcl
//UNAGENT  PROC
//STEP01   EXEC PGM=UNAGENT,REGION=0M,
// PARM='CONFIG=/etc/stonebranch/agent.conf'
//STEPLIB  DD DSN=STONE.AUTM.LOADLIB,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*

# 2. Configure Agent Communication and Security

In /etc/stonebranch/agent.conf:

properties
CONTROLLER_HOST=uac.enterprise.cloud
CONTROLLER_PORT=7878
SSL_ENABLED=YES
SECURITY_MODEL=RACF
JES_INTERFACE=SUBSYSTEM

The agent executes jobs under the submitting user's native RACF / ACF2 / Top Secret credentials, preserving full security auditing!

# 3. Convert CA-7 Schedules to Stonebranch Workflows

Using StackMF's automated conversion parser:

1. Export CA-7 database via BTI batch terminal interface.

2. Translate calendar schedules, trigger dependencies, and VRM resource locks into Stonebranch JSON workflow definitions.

3. Run parallel dual-run execution for 2 weeks to verify completion return codes (RC=0000).

4. Decommission CA-7 and terminate the license!

Technical Specifications Matrix

Attribute Specification
Target Environment IBM z/OS • Modernisation & Cloud
Key Technologies Stonebranch, UAC, CA-7
Delivery SLA Accelerated Sprint Delivery via StackMF Pods
Technical Reviewer Anshu, Chief Technology Architect • StackMF Architecture Pod

Production Readiness & Verification Checklist

? Frequently Asked Questions

What is the root cause of Deploying Stonebranch Universal Automation Center Agents on z/OS to Replace CA-7? ↓
Legacy CA-7 systems bind schedules, dataset triggers (DB.1), and virtual resource locks into proprietary mainframe databases. Modern solutions decouple scheduling orchestration (running in cloud or Linux containers) from execution engines, utilizing lightweight z/OS agents communicating over secure TLS REST/TCP.
How do you resolve Deploying Stonebranch Universal Automation Center Agents on z/OS to Replace CA-7 in production? ↓
Replacing Broadcom CA-7 requires deploying a modern, lightweight workload agent on z/OS that coordinates with cloud orchestrators. Learn step-by-step how to install the Stonebranch Universal Agent, map JCL execution, and achieve a 60% licensing cost reduction.
How can teams prevent Deploying Stonebranch Universal Automation Center Agents on z/OS to Replace CA-7 in enterprise pipelines? ↓
Perform automated syntax validation of all converted JCL prior to production cutover.

Recommended Technical Runbooks

Authoritative Reference Documentation

Official IBM manuals, Redbooks, and vendor technical advisories:

Related Topics: StonebranchUACCA-7Workload Automationz/OS AgentBroadcom Replacement
Diagnostic Runbook Notice & Nominative Fair Use Disclaimer

This diagnostic runbook is published by StackMF Technologies LLP for educational and architectural reference only. All code snippets, JCL, and procedures are provided "AS IS" without warranty of any kind. Always test changes thoroughly in non-production sysplex environments prior to production rollout.

IBM, z/OS, CICS, Db2, IMS, RACF, and IDz are registered trademarks of International Business Machines Corporation. Broadcom, CA-7, and Endevor are trademarks of Broadcom Inc. All other trademarks belong to their respective owners and are referenced under the Nominative Fair Use Doctrine (US Lanham Act 15 U.S.C. ยง 1125 / Section 30 of the Indian Trade Marks Act, 1999) solely for technology compatibility and diagnostic identification. StackMF Technologies LLP is an independent consulting entity not affiliated with or endorsed by these vendors. View Full Legal & IP Policy →

Enterprise Advisory

Struggling with Critical Mainframe Incidents or Vendor Renewal Pressure?

StackMF deploys certified Senior Mainframe Engineers fluent in both z/OS legacy internals (COBOL, DB2, CICS, VSAM, CA-7, Endevor) and modern cloud stacks (React, Kafka, AWS, Git). Onboard dedicated pods in 48 hours or cut Broadcom licensing by 60%.