Home / Broadcom (CA) / CA 7 Workload Automation
① Product · Broadcom (CA)
CA 7 runs the production batch, and Broadcom (CA) licenses it on capacity, not jobs. That makes the cost move with your MSU and your renewal, not with the schedule. Know both before the quote arrives.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →CA 7 Workload Automation is Broadcom (CA)'s flagship z/OS batch scheduler, the engine that plans, triggers, and tracks the production workload that runs overnight in many of the world's largest mainframe shops. It is deeply embedded: the batch dependency map, the operations runbooks, and years of automation are all built around it, which is precisely why it is sticky and why Broadcom prices it with confidence. It sits in the same competitive set as IBM Z Workload Scheduler and BMC Control-M.
CA 7 is licensed on a capacity metric, historically MIPS and increasingly MSU as Broadcom migrates the mainframe portfolio toward its consumption model. The charge follows the capacity of the environment, not the number of jobs scheduled. It is commonly sold inside a broader Broadcom portfolio agreement rather than as a clean standalone line, and consumption based deals reconcile usage forward under a True Forward mechanism rather than crediting underuse back.
| Element | How CA 7 is treated |
|---|---|
| Metric | Capacity: MIPS, migrating to MSU |
| Model | Portfolio agreement or mainframe consumption (MCL) |
| Reconciliation | True Forward, forward only |
| Cost driver | Licensed capacity, not job count |
| Term shape | Multi year with annual escalators commonly observed |
Directional summary. Metric and term depend on the specific Broadcom agreement.
Three drivers move the CA 7 number. Capacity, because the metric tracks MIPS or MSU, so a hardware refresh or a rising peak lifts the charge with no change to the schedule. Renewal escalators, because Broadcom agreements commonly carry annual uplifts that raise the cost per unit regardless of workload. And bundling, because CA 7 is often folded into a portfolio number where its individual line cannot be benchmarked, which suits the vendor and blinds the buyer. The schedule is stable; the commercial structure is what compounds.
The recurring traps are commercial rather than technical. A MIPS to MSU conversion accepted without independent validation can quietly reset the baseline upward. Capacity growth reconciled forward under True Forward without a cap turns an uncontrolled peak into a permanent floor. And portfolio bundling hides the CA 7 line inside a larger figure where it escapes benchmarking. The defense is independent reconciliation of actual consumption against contracted capacity, done before the renewal, not after the quote.
The structural lever is displacement: IBM Z Workload Scheduler and BMC Control-M both displace CA 7, and a costed, time bound migration study resets the conversation even when the intent is to reprice. The contract levers are escalator and uplift caps, a True Forward cap so capacity growth does not become a permanent floor, and unbundling the CA 7 line so it can be benchmarked on its own. Timing matters: align the renewal away from the moment Broadcom holds maximum leverage. We build the displacement math, validate the metric conversion, and reconcile consumption independently, which is the core of our Broadcom (CA) renewal work.
CA 7 is licensed by Broadcom (CA) on a capacity metric, historically MIPS and increasingly MSU as Broadcom migrates the portfolio to its mainframe consumption model. The charge tracks the capacity of the environment it runs in rather than the number of jobs scheduled, and it is commonly sold inside a broader portfolio agreement rather than as a standalone line.
Two reasons are common. The metric is capacity based, so a hardware refresh or rising MSU lifts the charge even when the schedule is unchanged. And Broadcom renewals commonly carry annual escalators and consumption reconciliation, so the cost per unit can climb at renewal regardless of workload. Buyers who do not model both ahead of time meet the number for the first time at quote.
The credible displacers are IBM Z Workload Scheduler, formerly Tivoli Workload Scheduler for z/OS, and BMC Control-M. Migrating a scheduler is a serious project because the production batch plan depends on it, but a costed and time bound displacement study is one of the few levers that resets a Broadcom portfolio negotiation, where the incumbent advantage is otherwise strong.
The recurring traps are MIPS to MSU conversion that is not validated, capacity growth that is reconciled forward at renewal without a cap, and portfolio bundling that hides the CA 7 line inside a larger number where it cannot be benchmarked. Independent reconciliation of consumption against contracted capacity is the defense.
Publisher hub: Broadcom (CA) mainframe licensing. Related products: CA Librarian, MIM Resource Sharing, and the displacer IBM Workload Scheduler for z/OS. Put it to work: Broadcom (CA) renewal advisory.