① Guide · Control-M renewal
A BMC Control-M renewal turns on what it measures: job and task volume on one side, mainframe capacity on the other, and increasingly a consumption baseline that fixes both. Knowing which meter you are on, and cleaning it before BMC reads it, is what moves the number. Here are the levers.
48 hour mobilization Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →BMC Control-M is not licensed one way. Traditional mainframe deployments are commonly tied to capacity, broader and cloud deployments are frequently priced on job or task volume, and BMC has been steering customers toward consumption based models, including its zConsumption Licensing approach tied to measured MSU utilization. Before any renewal conversation, the first job is to establish precisely which meter your agreement runs on, because the levers that move a job count number do nothing to a capacity number, and a consumption baseline rewards a different preparation entirely.
The mistake we see most often is a buyer negotiating discount percentage on a meter they never examined. The discount is the smaller lever. The meter, and what it is allowed to measure, is the larger one.
Match the lever to the meter
| Meter | What inflates it | The lever |
|---|---|---|
| Job and task volume | Cloned folders, decommissioned and test workflows never removed | Inventory and retire dead definitions before BMC counts |
| Mainframe capacity | Tool rated on full sysplex rather than the LPARs it runs on | Confine scope; validate the capacity figure against your data |
| Consumption baseline | A baseline measured during a busy period | Validate the measurement window; contest the baseline year |
| Support and add ons | Modules carried forward unexamined | Unbundle and challenge each line |
The job count cleanup, in order
Workload automation is a competitive market. IBM and Broadcom (CA) both ship scheduling tools, and a documented, costed alternative is the lever that converts a captive Control-M renewal into a contested one, whether or not you intend to migrate. The displacement math has the same shape as any mainframe tool swap: the steady state saving has to repay the transition year. But even when you stay on Control-M, a credible priced alternative is what keeps BMC honest on the meter you have cleaned. This is the discipline behind our BMC license negotiation work.
On more than one basis. Traditional mainframe deployments are commonly capacity tied, broader deployments are frequently job or task priced, and BMC has been moving customers toward consumption models including zConsumption Licensing on measured MSU. Establish your meter first.
Definitions accumulate. Folders get cloned and decommissioned workflows are rarely removed, so the daily count drifts above the work the business depends on. Where the license is job priced, that is shelfware you pay for. A cleanup before renewal is a reliable lever.
It depends on workload shape and who carries measurement risk. A consumption model can suit a volatile estate but makes the baseline year decisive. We model it against existing terms first and never let the vendor set the baseline unchallenged.
A validated job and task inventory, a capacity figure reconciled against your data, and a credible costed alternative. Scheduling has real competitors, and a documented alternative converts a captive renewal into a contested one. See the BMC playbook.
The AMI and Control-M portfolio and how BMC prices it.
The displacement math that disciplines any tool renewal.