① Journal · Renewal Playbook
Control-M for z/OS is a BMC workload automation product, typically priced on MSU capacity rather than on the jobs it runs, and it is one of the stickiest products on the mainframe. The footprint, the AMI portfolio bundle, the zCL model, and the cost of switching are the levers. Here is what actually moves the number.
Control-M is the hardest product on the mainframe to leave. Which is precisely why it is priced with confidence.
Control-M for z/OS is BMC's mainframe workload automation and job scheduling product, the engine that runs the batch schedule, manages calendars and dependencies, and recovers failed work across the estate. Like most of the BMC mainframe portfolio it is typically licensed on capacity, measured in MSU, so the number tracks the MSU of the LPARs Control-M is entitled across rather than the count of jobs or tasks it runs. What makes Control-M distinctive at renewal is not its metric but its grip: an enterprise scheduler accumulates thousands of job definitions, calendars, and dependencies over years, and that accumulated configuration is exactly what makes the product hard to leave and easy for the vendor to price.
That grip is the vendor's lever, and it is real. But it cuts both ways. Because Control-M is mission critical and embedded, it tends to escape the scrutiny that newer or more visible products attract: the licensed MSU rolls forward, the scope sits inside a wider BMC portfolio, and nobody asks whether the capacity entitled still matches the LPARs that actually run scheduled work. A Control-M renewal is the moment to interrogate that. The buyer cannot pretend the switching cost is zero, but the buyer can refuse to let the vendor assume it is infinite. Reading the renewal means working the MSU footprint, the portfolio bundle, the licensing model, and a costed view of the alternative together. This builds on our Control-M for z/OS licensing page and our BMC publisher hub.
Lever · what it moves · how to pull it
| Lever | What it moves | How to pull it |
|---|---|---|
| MSU footprint | The capacity Control-M is licensed across drives the price, not job count | Align entitled MSU to the LPARs that actually run scheduled work; remove dead scope |
| BMC portfolio bundle | Packaging with MainView and the AMI suites hides the Control-M line | Price Control-M separately; confirm what in the bundle is actually used |
| zCL vs capacity pricing | The model sets how BMC capacity is charged and trued up | Model traditional capacity against zCL consumption and choose on the numbers |
| Costed alternative | A scheduler the vendor knows you have priced changes the conversation | Scope migration to IBM Workload Scheduler or CA 7 as a credible, not literal, option |
| Fiscal year timing | Quota pressure near BMC's year end softens the number | Align the close to BMC's fiscal year end where the term allows |
Control-M is priced on the MSU it runs across, not the jobs it runs. The footprint, the bundle, and a costed alternative are where the number moves.
You will probably keep Control-M. That is not the same as accepting the first number.
The honest starting point on a Control-M renewal is that most estates keep it. The product works, the schedule depends on it, and ripping out an enterprise scheduler to save on a renewal is rarely the right trade. BMC knows this, and the price reflects it. The mistake buyers make is to conclude that because they will keep the product, they have no leverage, and to negotiate from that defeated position. The two facts are not the same. Keeping Control-M is a decision about the product; accepting an uninterrogated renewal number is a decision about money, and the second does not follow from the first.
What changes the number is preparation that the vendor can see. Three disciplines do most of the work. First, control the footprint: confirm which LPARs actually run scheduled work, align the entitled MSU to them, and strip out capacity that rolled forward from retired environments, because that footprint, not the job count, is the bill. Second, unbundle: insist Control-M carry a separately stated price rather than disappearing into a portfolio number with MainView and the AMI suites, because a price you cannot see is a price you cannot challenge. Third, cost the alternative: scope what a migration to IBM Workload Scheduler for z/OS or Broadcom CA 7 would actually take, not to threaten it, but so the vendor cannot assume the switching cost is infinite. A buyer who has done this work, early enough that the clock is not the vendor's, negotiates from a different place. Our cost optimization service finds the unused footprint, and our license negotiation service converts the costed alternative into a lower number.
Control-M is priced on capacity, not on jobs. Confirm which LPARs actually run scheduled work, align the entitled MSU to them, and remove capacity that rolled forward from retired environments before the renewal.
The bill is the footprint, not the job count.
Insist Control-M carry a separately stated price rather than disappearing into a BMC portfolio number with MainView and the AMI suites. A line you cannot see is a line you cannot cut.
An unbundled price is the only price you can challenge.
Scope what a migration to IBM Workload Scheduler for z/OS or Broadcom CA 7 would take. The aim is not to leave, it is to remove the vendor's assumption that you never could.
A costed switch is leverage even when you stay.
Model traditional capacity pricing against zCL consumption and choose on the numbers, and align the close to BMC's fiscal year end where the term allows, so the vendor negotiates against its own quota clock as well as yours.
The model and the quarter are both part of the price.
⑤ The discipline that pays
Control-M is the stickiest product on the mainframe. Keeping it is a product decision; the renewal number is a money decision, and the two are not the same.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
Control-M for z/OS is BMC's mainframe workload automation product, and like most of the BMC mainframe portfolio it is typically licensed on capacity in MSU, not on the count of jobs or tasks it runs. The number tracks the MSU of the LPARs it is entitled across. Many estates also have the option of BMC zConsumption Licensing, zCL, which charges on the prior year's actual consumption with a year end true up.
Rarely as a literal plan, but a credible alternative is still the lever. Control-M is sticky: thousands of job definitions and dependencies accumulate over years, which is why the vendor prices it with confidence. The counter is to cost the switch to IBM Workload Scheduler or Broadcom CA 7, not to threaten migration but to remove the vendor's assumption that you never could.
Controlling the MSU footprint and unbundling Control-M from the wider BMC portfolio. Aligning the entitled capacity to the LPARs that actually run scheduled work, pricing Control-M as a separate line, choosing deliberately between capacity pricing and zCL, and timing the close to BMC's fiscal year end is where the largest movement comes from.
Rationalize the MSU footprint, unbundle Control-M into a separately stated price, cost a migration to a competing scheduler as a credible option, model capacity pricing against zCL, and time the close to BMC's fiscal year end. Start early, because the stickiness that makes Control-M hard to leave is a reason to begin sooner, not to accept the first number. See our Control-M for z/OS licensing page.
Related: Control-M for z/OS licensing · BMC publisher hub · Negotiating BMC AMI suite bundles · BMC vs Broadcom · BMC roadmap moves · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →