① Journal · Syncsort (Precisely)
Precisely prices Syncsort MFX on capacity MSU, so a hardware refresh resets the baseline, and it upsells ZPSaver as a saving that quietly adds a license. Here are five recurring Syncsort price patterns, and the buyer counter to each.
The sort workload is flat. The capacity figure and the ZPSaver upsell are what move the bill.
Syncsort (Precisely) sells MFX, the high performance sort, copy, and join utility, along with Ironstream for machine data integration. MFX is commonly licensed on mainframe capacity measured in MSU, which is where the first pattern lives. Because the price tracks licensed capacity rather than actual sort volume, a hardware refresh or a workload growth elsewhere on the box can raise the capacity figure and reset the baseline the renewal builds on, even when the sort work itself has not grown. The buyer pays for the size of the machine, not the size of the job.
The second pattern is the ZPSaver upsell. ZPSaver offloads eligible sort, copy, and compression work to the zIIP specialty engine, which genuinely reduces general purpose MSU and the MLC bill that depends on it, but it is a separately licensable feature, so the net is a software license added against an MLC reduction. Pitched on the gross saving, it can look better than it nets. Ironstream adds a model choice between MSU based and ingestion based pricing, and DFSORT, which ships with z/OS, is the credible alternative that gives the whole negotiation leverage. Countering Syncsort is about right sizing the licensed capacity, netting the ZPSaver math, choosing the Ironstream model on data, and holding the DFSORT switch as a costed option. Read this with our MFX licensing page and the Syncsort (Precisely) publisher hub.
What we commonly observe · the pattern and the buyer counter
| Price pattern | What it looks like | Buyer counter |
|---|---|---|
| Capacity MSU reset | A hardware refresh raises the licensed capacity figure | Right size capacity to the machine MFX runs on |
| ZPSaver upsell | Offload pitched on gross MLC saving, license cost omitted | Model the net: MLC reduction minus the added license |
| Ironstream model choice | MSU based versus ingestion based pricing, framed by vendor | Choose the model on your real data volume, not the pitch |
| DFSORT displacement counter | Bundled z/OS sort ignored in the renewal framing | Hold a costed DFSORT switch as leverage |
| Annual capacity uplift | Compounding increase written into the term | Cap the annual increase and fix the list reference |
Patterns are what we commonly observe across buyer side engagements, not statements of Precisely policy, and may change. Your licensed capacity, sort profile, and contract govern the real number.
MFX prices on licensed capacity, so a number tied to the full machine charges you for cores the sort never touches. Establish the capacity MFX genuinely needs, license to that, and protect the figure against a hardware refresh that would otherwise reset it upward. The job size, not the box size, is what you should be paying for, and the gap between them is the saving.
Pay for the sort, not the server it sits on.
The zIIP offload reduces general purpose MSU and the MLC that depends on it, but ZPSaver is a separate license, so the only number that matters is the MLC reduction minus the ZPSaver cost across the term, on your real sort profile. Model that net before adopting, not the gross saving on the slide. Where the net is positive, take it; where it is thin, the offload is a cost dressed as a saving.
Judge the offload on the net, not the headline.
DFSORT ships with z/OS, so the estate already owns a sort utility, and the cost of switching from MFX is conversion effort rather than a new license. Scope that switch honestly, including JCL, parameters, and any MFX specific features, and carry it as a costed alternative into the renewal. The credible option moves the Syncsort number even when MFX stays for operational reasons.
The bundled alternative is leverage whether or not you use it.
④ Where the Syncsort number is countered
The sort job is flat. The capacity, the upsell, the model are the ones that count. Right size capacity, net the offload, hold DFSORT.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
MFX is commonly licensed on mainframe capacity measured in MSU, so the price moves with licensed capacity. A hardware refresh or workload growth that raises the capacity figure resets the baseline even when sort volume is flat. Right size the capacity to the machine MFX runs on. See MFX licensing.
ZPSaver offloads eligible work to the zIIP engine, reducing general purpose MSU and the MLC bill, but it is a separately licensable feature, so the net is a license added against an MLC reduction. Model the net over the term on your real sort profile. See how zIIP and offload affect MLC.
DFSORT ships with z/OS, so the estate already owns a sort utility without a separate Syncsort license. Switching carries conversion effort, but the bundled alternative is real leverage. Scope the DFSORT switch honestly and hold it as a costed option. See the Syncsort (Precisely) publisher hub.
Right size the licensed capacity, net the ZPSaver math, choose the Ironstream model on real data volume, and hold the DFSORT switch as a costed option with the annual uplift capped. Our cost optimization right sizes the capacity and our license negotiation service sets the caps. See also IBM price increase patterns.
Related: Syncsort (Precisely) publisher hub · MFX licensing · Syncsort renewal advisory · IBM price increase patterns · cost optimization
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →