Home / Syncsort (Precisely) / Syncsort Optimize Licensing
① Product · Syncsort (Precisely)
Syncsort sort optimization is delivered through MFX and its ZPSaver zIIP option, licensed on capacity. The lever that makes it interesting is the IBM MSU it can avoid. Here is the metric and what to pull at renewal, buyer side.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →Syncsort sort optimization is Precisely's mainframe sort offering, delivered through Syncsort MFX, the high performance sort, copy, and join engine that is one of the most widely installed third party products on IBM Z. The optimization story has two parts: MFX itself, which reduces the billable and elapsed time of sort jobs, and ZPSaver, a licensable MFX feature that transparently offloads eligible sort, copy, and compression work to zIIP specialty engines. There is no separate SKU literally named Syncsort Optimize; what a buyer licenses when they buy sort optimization is Syncsort MFX plus the ZPSaver feature.
Syncsort MFX is a third party z/OS product licensed on mainframe capacity, commonly in an MSU or MIPS tier band, with an annual maintenance stream as the renewable part. It is not an IBM Monthly License Charge product and is not billed on the rolling four hour average. ZPSaver is licensed as a feature of MFX. Its commercial point is indirect: by moving eligible work to zIIP, it can lower general purpose CP usage and the IBM MSU charges that track it, so the feature is judged against the IBM cost it avoids, not its own price alone.
| Element | How it is treated |
|---|---|
| Charge model | License plus annual maintenance, third party z/OS tool |
| Metric | Mainframe capacity tier (MSU or MIPS band) |
| ZPSaver | Licensable MFX feature, zIIP offload |
| Value basis | IBM CP and MSU charges avoided by zIIP offload |
| Renewable element | Annual maintenance and support |
Directional summary. Your capacity band, feature entitlements, and zIIP eligibility depend on your Precisely order and your workload.
Three drivers set the number. The licensed capacity band, because MFX is priced against the MSU or MIPS tier of the machines it runs on, so a refresh that lifts the band lifts the cost regardless of how much sorting you do. The feature set, because ZPSaver and other options are entitled separately and add to the bill. And the workload economics on the other side of the ledger, because the value of the whole line depends on how much sort work is zIIP eligible and how much IBM CP and MSU charge that offload actually removes. A sort estate that has shrunk, or one where most work is already eligible, changes the math at renewal.
The recurring traps are structural. Capacity band creep after a hardware refresh that is never rebaselined, so the entitlement tracks the box rather than the sort workload. LPAR scope, where MFX is installed or active on more LPARs than the license tier covers. And feature scope, where ZPSaver or other options are enabled beyond entitlement. Because the metric is a stated capacity band rather than a metered peak, a consolidated estate often keeps paying for a tier larger than the sort workload now needs, and only a reconciliation of where MFX actually runs surfaces it.
The structural lever is the capacity band: rebaseline it against the LPARs MFX actually runs on today. The economic lever is the zIIP value case: quantify the IBM CP and MSU charges ZPSaver avoids so the feature pays for itself in your own numbers rather than the vendor's. The contract lever is a cap on the annual maintenance uplift. And the strategic lever is the credible alternative: IBM DFSORT ships with z/OS at no separate license charge, so a real evaluation of moving sort workload to DFSORT is leverage at the MFX renewal even when you intend to stay on MFX for its performance. This is the buyer side work we do on the Syncsort MFX renewal and the sort cost lever.
Syncsort sort optimization is Precisely's mainframe sort offering, delivered through Syncsort MFX, the high performance sort, copy, and join engine, with ZPSaver as a licensable option that offloads sort, copy, and compression work to zIIP processors. There is no separate SKU literally named Syncsort Optimize; on order forms the entitlement is Syncsort MFX plus the ZPSaver feature, which is what buyers actually license when they buy sort optimization.
Syncsort MFX is a third party z/OS product licensed on mainframe capacity, commonly in an MSU or MIPS tier band, with an annual maintenance stream that is the renewable part. It is not an IBM Monthly License Charge product and is not billed on the rolling four hour average. ZPSaver is a licensable feature of MFX that requires no JCL changes and offloads eligible work to zIIP, which can reduce general purpose CP consumption and the MSU charges tied to it.
The common traps are capacity band creep after a hardware refresh that is never rebaselined, MFX installed or active on more LPARs than the license tier covers, and the ZPSaver feature enabled beyond its entitlement. Because the metric is a stated capacity band rather than a metered peak, a consolidated estate often keeps paying for a tier larger than the sort workload now requires.
Rebaseline the capacity band against the LPARs MFX actually runs on, value the ZPSaver zIIP offload against the IBM MSU it avoids so the feature pays for itself in your numbers, cap the annual maintenance uplift, and remember the credible alternative: IBM DFSORT ships with z/OS, so a real evaluation of moving sort workload back to DFSORT is leverage at the MFX renewal even when you intend to stay.
Publisher hub: Syncsort (Precisely) mainframe licensing. Related products: Ironstream licensing and IBM DFSORT licensing. Related metric: MSU explained. Put it to work: Syncsort MFX renewal: the sort cost lever.