① Publishers · Syncsort (Precisely) · License negotiation
Syncsort MFX is the most frequently installed third party product on IBM Z, which is precisely why Precisely can price it like infrastructure and renew it on autopilot. The good news for the buyer: a sort utility is one of the few mainframe products where the alternative can actually be quantified, and a credible alternative is what resets the number.
Priced like infrastructure.
Precisely acquired the Syncsort mainframe portfolio and now carries Syncsort MFX, ZPSaver, and the Ironstream observability family. MFX is a sort, copy and join utility with a long history on the platform, installed in over 85 countries and present on a large share of the world's IBM and plug compatible mainframes. That ubiquity is the commercial reality: a product this embedded gets renewed without scrutiny, and a product renewed without scrutiny drifts up.
Like most mainframe ISV products, MFX is typically licensed against capacity, MSU or MIPS tiers per machine or LPAR, with annual maintenance. So the same two levers apply that apply everywhere on the frame: the gap between contracted and consumed capacity, and the tendency for a hardware refresh to drag the tier up through MIPS creep. What makes Syncsort different from a database is that the exit is real: DFSORT ships with z/OS, alternatives exist, and switching cost on a sort utility can be measured rather than guessed.
Every Syncsort and Precisely product on the estate, MFX, ZPSaver, Ironstream and anything acquired along the way, mapped to the contracts and amendments that license them. Infrastructure products accumulate paper quietly; the first job is knowing exactly what you hold and on which terms.
What MFX actually consumes versus the contracted tier, per LPAR. Sort workload is measurable, and on estates that have shrunk or modernized in part, the licensed capacity has usually not followed the workload down. The gap is the opening position.
The DFSORT or third party migration path costed properly: conversion effort, JCL and control card differences, testing, and the realistic timeline. We do not assume you will switch. We make the switch quantified, because a vendor prices very differently against a buyer who can show the exit than against one who cannot.
ZPSaver offloads sort, copy and compression cycles to zIIP engines, lowering the general processor MSU those jobs consume and changing the broader cost picture. We value that effect alongside the license so the renewal is negotiated against the whole number, not just the Syncsort line.
A right sized tier, uplift caps for the term, true down rights so the number can fall when workload does, and clean entity and DR language. The renewal that captures the reconciliation in the contract is the one that holds; the one closed on a handshake leaks back by the next cycle.
What changes with us in the room.
Precisely is not wrong to value MFX; it is a capable product with decades of optimization behind it. But ubiquity is leverage for the seller only until the buyer brings measurement and a priced exit. Across 500+ engagements and $180M+ of negotiated mainframe spend, the pattern on infrastructure products is consistent: the renewals that move are the ones where the buyer arrived with a reconciled capacity number and a credible alternative, not a request for goodwill.
What you get
Precisely typically licenses MFX against mainframe capacity in MSU or MIPS tiers per machine or LPAR, with annual maintenance. Because MFX is one of the most widely installed third party products on IBM Z, it is often treated as infrastructure and renewed on autopilot, which is exactly the condition that lets the price drift up.
Yes, and that is the lever. DFSORT ships with z/OS and other third party sort products exist. A migration is real work and rarely the goal, but a sort utility is one of the few mainframe products where switching cost can actually be quantified, which makes the alternative credible enough to price and useful at the table.
It can. ZPSaver offloads sort, copy and compression work to zIIP engines, lowering the general processor MSU those jobs consume. That reduces IBM MLC exposure and changes the capacity picture the Syncsort renewal is priced against, so it belongs in the same analysis rather than a separate one.
It depends on how far the licensed tier has drifted from current use and how credible the alternative is. Across 500+ engagements the combination of reconciliation and negotiation typically produces 20 to 35% renewal reductions, and on infrastructure products renewed without scrutiny the gap is often wider than buyers expect.
Twelve to eighteen months out. Measure what MFX and the surrounding products consume, reconcile against the contracted tier, price the DFSORT or alternative migration, and set your walk away before Precisely controls the clock. A renewal worked under deadline pressure with no alternative priced is a renewal the vendor sets.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →