Journal · Renewal negotiation

TWS for z/OS renewal: what moves the number.

The scheduler that runs the batch is an IPLA program priced on MSU and renewed through support. Five factors move the number, and the biggest is one many buyers never check: whether they are paying full capacity for a product that qualifies for sub-capacity.

The scheduler is priced on MSU, and on whether you elected sub-capacity.

IBM Z Workload Scheduler, the product long sold by IBM (International Business Machines) as Tivoli Workload Scheduler for z/OS and earlier as OPC, runs the batch schedule for much of the estate. It is a zSeries International Program License Agreement program, typically carrying a one time charge plus annual subscription and support, with required license capacity measured in MSUs and priced through tiered Value Units. The renewal that focuses only on a discount misses the structure: the charge is built on the MSU the scheduler is licensed against, whether that MSU is full machine capacity or sub-capacity, and the support basis that recurs every year.

That reframes the exercise. The buyers who win arrive having confirmed the sub-capacity election, read where their MSU lands on the Value Unit tier curve, validated the support basis, and built a costed view of the alternative on a product that, unlike a security manager, can actually be displaced. The five factors below run roughly in order of how much they move, the sub-capacity election and the tiers first, the alternative and timing last. Read this with our IBM publisher hub and our explainer on cost per MSU benchmarks and drivers.

What moves the number, in order of impact

Each factor and which direction it moves the scheduler bill

FactorWhat it movesWhen it pays most
Sub-capacity election Whether MSU is charged at full machine or sub-capacity On a partitioned estate not yet electing sub-capacity
Value Unit tiers The per MSU rate as licensed capacity crosses tier breaks Where the MSU sits near a tier boundary
Support basis (S&S) The recurring annual charge on a one time charge product Every renewal, since the renewal is largely the S&S
A credible alternative Whether the vendor prices a permanent product or a movable one When a costed Control-M or CA 7 view is built early
Timing and the term The leverage window and the support escalator caps At the term boundary, before auto renewal

Program names, Value Unit exhibits, and tier breakpoints change between versions; verify the current ones on your own agreement at the time of negotiation. The order is the durable part: the election and the tiers set the floor, and the support basis, the alternative, and timing price what is left.

The five factors in depth

№ 01

Confirm the sub-capacity election

Select zSeries IPLA programs can be charged at sub-capacity rather than full machine capacity where the estate implements and complies with sub-capacity WLC or EWLC. On a partitioned estate that gap is often the largest single number in the conversation. Confirm whether the scheduler is licensed at sub-capacity and exactly which MSU it captures, because a product paid at full capacity on a sub-capacity estate is overpaying before any discount is discussed.

Full capacity on a sub-capacity estate is money left on the table.

№ 02

Read the Value Unit tiers

IPLA capacity is priced through tiered Value Units, where the per MSU rate falls as licensed capacity climbs through the tiers. Where your MSU sits near a tier boundary, a small change in licensed capacity changes the effective rate. Read the curve before the renewal so the licensed quantity reflects what you run, not an inherited figure that strands you on an expensive tier.

The tier you sit on sets the rate you pay.

№ 03

Validate the support basis

For a one time charge product, the renewal is largely a subscription and support renewal, and support quietly compounding is the most common form of waste we find. Validate the S&S basis against the one time charge already paid, confirm what the escalator does over the term, and decide whether every entitlement under support is still in use.

The renewal you sign is mostly the support you keep.

№ 04

Build a credible alternative

Unlike a security manager, a scheduler can be displaced with planning. BMC Control-M and Broadcom (CA) CA 7 are the established alternatives, and converting a schedule is real but bounded work. A costed migration view built early, including the genuine conversion effort and the operational risk, removes the assumption that the scheduler is permanent and changes how the renewal is priced.

A scheduler you can move is a scheduler you can price.

№ 05

Time it and cap the escalators

Leverage exists in a window before the term ends and before auto renewal narrows the options. Start early enough to confirm the election, read the tiers, and build the alternative, then write support escalator caps and entitlement true down rights into the close so a flat estate does not pay a compounding charge for standing still.

Start before the clock favors the vendor.

The order that wins

The scheduler is priced on MSU and renewed on support. Check the election first, then the tiers. Confirm sub-capacity, read the curve, and price what is left.

20 to 35%

Typical reduction negotiated on renewal spend

$180M+

Mainframe spend negotiated on the buyer side

500+

Engagements delivered since 2019

Frequently asked questions

Q1

What drives scheduler cost?

The licensed MSU and whether it is charged at sub-capacity. IBM Z Workload Scheduler is a zSeries IPLA program, a one time charge plus annual support, priced on MSU through tiered Value Units. Confirming the sub-capacity election and reading the tier curve, not chasing a headline discount, is where the recoverable cost sits.

Q2

Why does sub-capacity matter so much?

Because the gap between full machine capacity and sub-capacity can be large on a partitioned estate. Select IPLA programs qualify for sub-capacity where you implement sub-capacity WLC or EWLC. A scheduler paid at full capacity on a sub-capacity estate is overpaying before any negotiation begins.

Q3

Can the scheduler be displaced?

Yes, with planning. BMC Control-M and Broadcom (CA) CA 7 are the established alternatives, and converting a schedule is real but bounded work. A costed migration view built early changes how the renewal is priced because it removes the assumption that the scheduler is permanent.

Q4

When should we start?

Early enough to confirm the election, read the tiers, and build the alternative before the term boundary. See our IBM mainframe cost optimization and MSU optimization service.

Related: IBM publisher hub · CA 7 renewal · Control-M renewals · RACF renewal

Audit notice or renewal under 18 months out? We mobilize within 48 hours.

Get expert help

Scheduler renewal on the horizon? Check the election before you price it.

Get expert help