Control-M: the scheduler that can cut its own platform's bill.

Control-M for z/OS is BMC's mainframe workload automation and job scheduling system, the engine that orchestrates when batch runs, in what order, and under what dependencies across the estate. It sits at the center of operational processing for many large shops, controlling the nightly and intraday batch that keeps the business running. Because it decides when work executes, it has a property few other products share: it can influence the consumption peak that the rest of the sub-capacity stack is billed on, which makes it both a licensed cost and a potential cost control lever.

Control-M for z/OS is licensed on capacity, typically the MSU rating of the machines or LPARs where it is authorized, carried as an entitlement under a multi year agreement rather than a charge per scheduled job. BMC also offers zConsumption Licensing (zCL), a consumption based model in which you pay against your prior year measured z/OS MSU utilization and true up any overage at year end. The two models answer different questions: the capacity entitlement fixes your cost to an authorized figure, while zCL ties it to measured consumption with a true up.

Directional, pattern level. Confirm your own metric and authorized capacity against the contract schedules before modeling either model.

The first driver is authorized capacity, since the entitlement is built on the MSU of the machines Control-M runs on rather than the number of jobs it schedules. The second is model choice: whether you sit on a fixed capacity entitlement or on zConsumption Licensing changes how your cost behaves as workload moves, and defaulting to the model you happen to hold leaves money on the table. The third driver is the surrounding BMC agreement structure and any uplift or escalator terms, which raise cost over a multi year term independent of how much scheduling you actually do.

Control-M exposure sits in the gap between the contracted figure and the running estate. Common traps we see at pattern level:

Control-M gives you a model choice and a workload tool, so the levers run on both fronts. The five that pay:

Workload automation is a competitive category, which gives Control-M genuine alternatives: IBM Z Workload Scheduler and Broadcom (CA) scheduling products such as CA 7 cover similar ground, and a shop can credibly evaluate a switch. But a scheduler is woven into thousands of job definitions, dependencies, and operational runbooks, so a migration is a substantial program rather than a quick swap, and the vendor knows it. The switching threat is most useful when it is genuinely scoped. For many estates the more reliable wins are right sizing the authorized capacity, choosing the model deliberately, and using Control-M's own optimization to cut the peak driven IBM cost.