Home / IBM / Tivoli Workload Scheduler for z/OS
① Product · IBM
Now marketed as IBM Z Workload Scheduler, the platform's batch controller is IPLA priced in MSU value units. The schedule rarely changes, but the capacity it is metered against does, and that is where the cost moves.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →IBM Tivoli Workload Scheduler for z/OS is the enterprise batch scheduler that began life as OPC, Operations Planning and Control, and is now marketed as IBM Z Workload Scheduler within the IBM Workload Automation family. It plans, submits, and tracks the production batch that runs the business overnight, with a controller on z/OS coordinating trackers and distributed agents. Many estates still hold and renew it under the Tivoli name, so both labels turn up on live contracts. It competes head to head with Broadcom (CA) CA 7 and BMC Control-M.
Workload Scheduler for z/OS is an IPLA program: a one time charge with annual Subscription and Support, measured in MSU based value units rather than the monthly peak that drives the MLC stack. Under sub-capacity terms the value unit count follows the MSU of the partitions where the controller and agents run, reported through the standard sub-capacity process. There is no separate per job meter; the number tracks capacity, which is why sub-capacity reporting discipline matters here too.
| Element | How IWS for z/OS is treated |
|---|---|
| Charge model | IPLA one time charge plus annual S&S |
| Metric | MSU based value units |
| Capacity basis | Sub-capacity where reported, else full capacity |
| Recurring cost | Annual Subscription and Support |
| Current name | IBM Z Workload Scheduler |
Directional summary. Value unit conversion and tiers depend on machine model and contract vehicle.
Three drivers set the number. Capacity, because the value unit count follows the MSU of the partitions in scope, so a hardware refresh or a growing peak lifts the bill even when the batch plan is unchanged. The annual Subscription and Support stream, which is the recurring cost that actually shows up year on year and the figure that compounds under uplift. And agent sprawl, because distributed and tracker agents spread quietly across systems and each footprint addition can widen the licensed basis. The schedule feels static; the capacity it sits on does not.
The recurring traps cluster around scope and reporting. Value unit miscounting when the controller or tracker agents land on partitions that were never licensed. Sub-capacity reports that lapse and force a more expensive full capacity reading. And distributed agents counted under the wrong entitlement, a classic in mixed estates. Because the metric follows MSU, ordinary capacity growth lifts exposure without anyone touching the schedule, so the audit position needs to be reconciled against actual deployment, not the original order.
The strongest lever is competitive displacement. Broadcom (CA) CA 7 and BMC Control-M both displace IBM scheduling, and a costed, time bound migration study is real leverage even when the intent is to reprice rather than move, because the scheduler is sticky and IBM knows it. Alongside that, the contract levers are Subscription and Support caps, value unit protections against capacity growth, and timing the renewal against hardware refresh so a machine upgrade does not silently reprice the program. Where support has lapsed, reinstatement terms are themselves negotiable. We build the displacement math and the capacity model before the renewal date controls the conversation, the core of our IBM work.
The product line that began as OPC and became Tivoli Workload Scheduler for z/OS is now marketed as IBM Z Workload Scheduler, part of the wider IBM Workload Automation family. Many enterprises still run and contract for it under the Tivoli Workload Scheduler name, so both labels appear on real agreements. The licensing mechanics are the same product either way.
It is an IPLA program, licensed on a one time charge with annual Subscription and Support, and measured in MSU based value units. On sub-capacity terms the value unit count follows the MSU of the partitions where the controller and agents run, reported through the standard sub-capacity process, rather than a separate per job or per agent meter.
The two credible displacers are Broadcom (CA) CA 7 Workload Automation and BMC Control-M. None of the three is free, and a scheduler migration is a serious project because the whole batch plan depends on it, but a costed displacement study is real leverage at renewal. The point is usually to reprice the incumbent, not necessarily to move.
The recurring traps are value unit miscounting when the controller or tracker agents spread onto partitions that were never licensed, sub-capacity reports that lapse and force a full capacity reading, and distributed agents counted under the wrong entitlement. Because the metric follows MSU, capacity growth lifts the bill even when the schedule itself has not changed.
Publisher hub: IBM mainframe licensing. Related products: z/OS licensing, RACF licensing, and the displacer CA 7 Workload Automation. Put it to work: IBM mainframe audit defense.