① Syncsort (Precisely) · Contract review
Syncsort (Precisely) MFX is commonly licensed against mainframe capacity, and capacity drifts upward with every hardware refresh. Add auto renewal clauses and a paid product sitting on top of the free IBM DFSORT baseline, and the contract is where the money is won or lost.
What the renewal hinges on before any feature is discussed.
The patterns we commonly observe on Syncsort (Precisely) agreements: capacity bands set to an older machine that a refresh has since outgrown, auto renewal language that locks an uplift unless notice lands by a date nobody is tracking, and the ZPSaver zIIP offload feature priced as a separate meter on top of the base sort license. The single largest lever sits underneath all of it: IBM DFSORT ships with z/OS at no additional license charge, so every dollar of a paid sort product rests on performance and features above that free baseline. The full calculation lives in our sort cost lever guide.
None of this is misconduct. It is a capacity based contract doing exactly what it was written to do. The counter is a review that reads every clause before the notice window closes: the capacity basis, the renewal mechanics, the offload you actually realize, and the credible fallback to DFSORT that gives the whole conversation a floor. For the product specifics, see our Precisely Elevate licensing page.
The contracted MIPS or MSU figure checked against the current machine. Where a hardware refresh has pushed you into a higher band, the entitlement is reconciled before the vendor reprices to it.
Capacity drift is the silent uplift.
Auto renewal dates, notice windows, and the uplift that triggers if the window closes uncontested. The clauses that remove your leverage get surfaced while there is still time to use it.
The calendar is part of the price.
A costed plan to move some or all sort workloads to IBM DFSORT, the free z/OS baseline, with the performance and offload trade offs made explicit. This is the floor that makes the paid product justify its premium.
A free baseline is real leverage.
The zIIP offload you pay for measured against the offload you actually realize, and its effect on your IBM Monthly License Charges modeled on your numbers. The feature gets priced on its own merits, not bundled past scrutiny.
A second meter is a second lever.
Capacity caps, notice windows you control, the right to track machine growth without automatic repricing, and offload protections that hold across the term. The contract stops renewing against you.
Terms that survive the next refresh.
③ What changes with us in the room
A capacity contract drifts upward quietly. A free baseline sits underneath it. We read both.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Mobilization on an audit notice or renewal
The capacity basis and the renewal mechanics. Whether the contracted MIPS or MSU still matches your machine, whether a refresh pushed you into a higher band, and whether the deal auto renews at an uplift unless you give notice. Those three clauses decide most of the bill.
Yes, it is the central lever. IBM DFSORT ships with z/OS at no additional license charge, so a paid sort product is only worth its premium above that free baseline. A costed fallback plan reopens the price. The math is in our sort cost lever guide.
ZPSaver offloads sort processing to zIIP, reducing the general purpose MSU that drives IBM Monthly License Charges. It can be a real saving, but it is a second meter and a second lever. We confirm the offload you pay for matches the offload you realize.
Before any auto renewal notice window closes, and ahead of any hardware refresh. Capacity agreements drift upward silently, and auto renewal clauses remove leverage once the date passes. A review 12 to 18 months out keeps timing in your hands.
Related: Syncsort (Precisely) licensing hub · the sort cost lever · Precisely Elevate licensing · contract review service · case studies
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →