① Journal · Syncsort (Precisely) · Audit
Syncsort MFX is among the most widely installed third party products on IBM Z, and Precisely licenses it on capacity. From the buyer side the activity clusters on the capacity tier, on the separately licensed ZPSaver feature, and on a renewal that prices a grown estate into an uplift.
A Syncsort audit is a capacity reconciliation. The ZPSaver feature is the part buyers forget.
Syncsort (Precisely) licenses Syncsort MFX, the high performance sort product that runs on a large share of IBM Z estates, on capacity, with renewals priced to the capacity tier or MSU (Million Service Units) band the product is licensed to. Around MFX sits ZPSaver, a separately licensable feature that offloads a large share of the sort workload to zIIP specialty engines, and Ironstream, the observability product that streams mainframe data to operations and security platforms. That structure tells you what a Syncsort audit tests. The capacity tier against current capacity, ZPSaver entitlement and the zIIP offload claimed, deployment scope across LPARs, and the uplift a capacity based renewal applies when the estate has grown. The common thread is capacity, and a buyer who has not validated the capacity basis is handing Precisely the reading.
The pattern we commonly observe is a reconciliation the buyer can win on its own numbers, provided those numbers are validated before the notice. The capacity tier may have been set against a configuration that has since changed. ZPSaver sits separately from the base MFX license, so it is easy to enable and easy to lose track of the entitlement. MFX and Ironstream deployment drifts across LPARs as the estate evolves. And a capacity based renewal will price the grown estate into an uplift unless the capacity basis is trued first. The buyers who come through a Syncsort audit cleanly are the ones who reconciled the MFX capacity tier, confirmed ZPSaver entitlement and offload, and inventoried deployment across LPARs before the notice arrived. Read this with Syncsort (Precisely) license negotiation and the Syncsort (Precisely) publisher hub.
Where Syncsort (Precisely) audits cluster · what we commonly observe and the buyer defense
| Focus area | What Precisely checks | Buyer defense |
|---|---|---|
| MFX capacity tier | The capacity tier or MSU band MFX is licensed to | Reconcile the tier against your current capacity |
| ZPSaver feature | Whether ZPSaver is entitled and the zIIP offload claimed is eligible | Confirm ZPSaver entitlement, keep offload evidence |
| LPAR deployment | MFX and Ironstream deployment scope against what is licensed | Inventory every LPAR and instance against entitlement |
| Capacity based renewal | A grown estate priced into a renewal uplift | True the capacity basis before the renewal prices it |
These are patterns we commonly observe across Syncsort (Precisely) audits, not statements of audit policy. Your specific entitlements, capacity tier, and ZPSaver terms govern; validate against your own capacity data and your contract before relying on any position.
MFX is licensed to a capacity tier, and that tier may have been set against a configuration that no longer matches your environment. Reconcile the licensed tier against current capacity, establish whether you sit over or under it, and bring that reading to the table rather than accepting the vendor's. A tier reconciled to your real capacity is a defensible audit position and a direct renewal lever. See our explainer on MSU and capacity metrics.
Match the tier to the capacity you actually run.
ZPSaver offloads a large share of the sort workload to zIIP, and because it is licensed separately from base MFX it is easy to enable without tracking the entitlement. Confirm that ZPSaver is entitled wherever it runs, verify the zIIP offload claimed is genuinely eligible, and keep the offload evidence. The feature is a real cost saver, but only when the entitlement matches the deployment. See our explainer on specialty engine licensing.
Track the feature license, not just the base.
MFX and Ironstream deployment drifts across LPARs as the estate evolves, and a capacity based renewal will price that drift into an uplift unless it is trued first. Inventory every LPAR and instance against entitlement, document anything decommissioned, and true the capacity basis before the renewal conversation rather than during it. A clean inventory keeps the uplift honest. See our Syncsort license negotiation service.
True the estate before the renewal prices it.
④ Where the Syncsort audit is won
A Syncsort audit reconciles capacity and a separate feature. The defense is a basis you trued first. Reconcile the tier, confirm ZPSaver, inventory the LPARs.
Mobilization on an audit notice
Mainframe spend negotiated on the buyer side
Typical renewal reduction
Four areas: the capacity tier or MSU band MFX is licensed to against current capacity, ZPSaver entitlement and the zIIP offload claimed, deployment scope across LPARs for MFX and Ironstream, and the uplift a capacity based renewal applies to a grown estate. The common thread is capacity, and a buyer who has not validated the capacity basis hands the vendor the reading.
ZPSaver is a licensable feature of MFX that offloads a large share of sort workload to zIIP. The audit questions are whether ZPSaver is entitled where it runs and whether the offload claimed is eligible. Because it sits separately from the base MFX license, it is easy to enable without tracking the entitlement, so confirm it against deployment and keep the offload evidence.
Treat it as a capacity and entitlement reconciliation. Reconcile the MFX capacity tier against current capacity before sharing anything, confirm ZPSaver entitlement and offload, inventory MFX and Ironstream deployment across LPARs, and answer each request in writing scoped to the products in question. Truing the capacity basis before a capacity based renewal keeps the uplift honest. See what good license governance looks like.
We reconcile the MFX capacity tier, confirm ZPSaver entitlement and offload, inventory deployment across LPARs, and manage the response from the buyer side so the reconciliation runs on your evidence. Our audit defense service mobilizes within 48 hours of a notice and our Syncsort license negotiation service resets the terms the audit and the next renewal build on.
Related: Syncsort (Precisely) publisher hub · IBM audit activity · BMC audit activity · Syncsort license negotiation · audit defense
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →