① Journal · Vendor negotiation
A Syncsort renewal turns on one question: how much zIIP offload does the sort actually deliver against free DFSORT. Five levers move the number, and the first is measuring that saving on your own workload. Here is where the leverage really sits.
The Syncsort deal turns on the sort cost it actually saves.
Negotiating with Syncsort (now part of Precisely) on the mainframe is mostly a negotiation about sort. The mainframe sort product and the Elevate optimization line, including ZPSaver, are sold on the premise that offloading sort and compression work to the zIIP specialty engine reduces the general purpose MSU that drives IBM software charges. That value is genuine on some workloads. But IBM ships DFSORT with z/OS at no additional license cost, so the third party sort has to justify itself against a free baseline, and the only number that matters is the offload it delivers on your workload.
That reframes the exercise. The buyers who win a Syncsort renewal arrive having measured the actual zIIP offload and MSU saving, right sized the capacity scope, and made the DFSORT alternative credible on at least part of the workload. The five levers below run in roughly that order, the sort cost case first, scope and terms next, displacement and timing alongside. Read this with our Syncsort (Precisely) publisher hub and our Syncsort contract review page.
What each lever moves · the measured sort saving sets the value the rest then prices
| Lever | What it moves | When it pays most |
|---|---|---|
| The sort cost case | What the zIIP offload is actually worth on your workload | Before the renewal, measured against free DFSORT |
| Capacity scope | The capacity tier and machines you commit to | Where the product runs narrower than it is licensed |
| Uplift caps | How fast the capacity charge grows each year | In the contract language, not the price line |
| Displacement | Whether the third party sort survives at all | Where DFSORT is credible on part of the workload |
| Timing and the term | The leverage window and the multi year price hold | At the term boundary, before auto renewal |
Product names and packaging change; verify the current ones on your own order. The order is the durable part: the measured saving sets the value, and scope, terms, and displacement price what is left.
Everything else follows the number. Measure the actual zIIP offload and the general purpose MSU reduction the sort delivers on your workload, not the vendor projection. On some workloads the saving is substantial; on others it is small. That measured value, against free DFSORT, is what the product is worth to you and the anchor for the whole negotiation.
Your measured offload is the only number that counts.
The sort and Elevate products are commonly licensed by mainframe capacity, scoped to machines or a capacity tier. Where the product runs on fewer systems or less capacity than it is licensed for, the scope is overstated. Align the entitlement to where the workload actually runs before the renewal prices it.
License the capacity you use, not the estate.
The annual uplift on the capacity charge is the number that compounds across the term, and it is rarely tied to new value. Negotiate a hard cap on the yearly increase in the contract itself rather than accepting a percentage by assurance. The clause is the price.
The escalator is the deal, not the footnote.
DFSORT is included with z/OS at no additional license cost, so a costed plan to move sort workload back to it sets a hard ceiling on what the third party sort is worth. The migration takes effort and some shops depend on specific features, but a credible DFSORT alternative on part of the workload turns the renewal competitive.
A free alternative caps the premium.
Leverage exists in a window before the term ends and before auto renewal narrows your options. Start early enough to measure the saving and scope the alternative, and negotiate the multi year price hold as part of the same event. Run out of runway and the renewal happens on the vendor's calendar.
Start before the clock favors the vendor.
④ The order that wins
The vendor prices the saving it projects. Your measurement decides the saving that is real. Measure the offload first, then negotiate what is left.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
The measured sort cost saving. The product is sold on zIIP offload that reduces general purpose MSU, but IBM ships DFSORT at no extra license cost. Measuring the actual offload on your workload sets what the third party sort is worth and anchors the whole negotiation.
The sort and Elevate products are commonly licensed by mainframe capacity, scoped to machines or a capacity tier rather than metered continuously. The number that moves is the capacity tier and the annual uplift, so right size the scope and cap the uplift. Confirm the metric on your own order.
On workloads where the measured offload saving is small, yes. DFSORT is included with z/OS, so a costed plan to move sort workload back to it sets a hard ceiling on the third party premium. A credible alternative on part of the workload turns the renewal competitive.
Early enough to measure the offload and scope the DFSORT alternative before the term boundary, usually months ahead. The measurement takes time to make credible, and the commercial levers are worth more once it is done. See our Syncsort contract review and Syncsort MFX sort cost lever.
Related: Syncsort (Precisely) publisher hub · Syncsort MFX sort cost lever · specialty engines explained · negotiating with IBM
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →