How are DFSORT and Syncsort MFX licensed?

IBM DFSORT is IBM's sort product, tied to the z/OS environment and priced within IBM's licensing framework, so its cost is effectively bound into the IBM stack rather than negotiated as a separate third party line. Syncsort (Precisely) MFX is a third party sort licensed on MSU capacity as its own product, with a licensable feature, Syncsort ZPSaver, that can offload a large share of the sort workload to zIIP specialty engines. Because zIIP cycles do not carry general processor software charges, that offload is the licensing story: MFX is priced as an added product, but it can reduce IBM Monthly License Charge by moving sort cycles off the general purpose processors that drive MLC.

Does Syncsort MFX actually save money over DFSORT?

It can, but only when the arithmetic works for your estate. MFX is an additional licensed product, so it adds its own cost, and the saving comes from offloading sort cycles to zIIP and from sort efficiency that lowers the general processor consumption feeding your IBM MLC peak. Whether the MLC reduction exceeds the MFX license cost depends on how sort heavy your workload is, how much of your four hour rolling average peak is driven by sort, and how much spare zIIP capacity you have. For sort intensive shops the case can be strong; for light sort users DFSORT inside the IBM stack is usually the lower total cost. It is a measurement exercise, not a slogan.

What actually decides DFSORT vs Syncsort MFX?

The MLC arithmetic decides it, not raw sort speed, which is close enough for most workloads. The questions that matter are how much of your general processor consumption and your R4HA peak is sort, how much of that MFX could move to zIIP through ZPSaver, what zIIP headroom you have, and how the MFX license cost compares to the resulting MLC reduction. The sort tool is one of the few mainframe products where the third party alternative has a direct cost reduction mechanism against IBM charges, so the decision is a sub-capacity and zIIP modeling exercise tied to your actual SCRT data.

DFSORT vs Syncsort MFX: The Sort Decision

DFSORT vs Syncsort MFX: the zIIP question, not the speed sheet.

IBM DFSORT sits inside the IBM stack. Syncsort (Precisely) MFX is a third party sort licensed on MSU, with a ZPSaver feature that can offload most sort cycles to zIIP. Because zIIP cycles do not carry general processor software charges, the real decision is whether moving sort off the general processors cuts your IBM MLC by more than MFX costs. That is arithmetic, not a slogan.

Decide it on the MLC arithmetic. DFSORT and MFX both sort well, so performance rarely settles it. MFX is an additional licensed product, but its ZPSaver feature can move a large share of sort cycles to zIIP, and zIIP work does not drive general processor software charges. For a sort intensive estate, the reduction in your IBM Monthly License Charge peak can exceed the MFX license cost, and the case is real. For a light sort user, DFSORT inside the IBM stack is usually the lower total cost. The right answer comes from modeling your own SCRT and zIIP data, not from either vendor's benchmark.

DFSORT vs Syncsort MFX, the licensing levers compared
Dimension	IBM DFSORT	Syncsort (Precisely) MFX
Vendor	IBM	Precisely
Delivery	IBM sort within the z/OS environment	Third party sort, separately licensed
Licensing basis	Priced inside the IBM stack framework	MSU capacity, own product line
zIIP offload	Runs on general processors, drives MLC	ZPSaver can offload most sort to zIIP
Effect on IBM MLC	Sort cycles count toward the MLC peak	Can lower the MLC peak by moving sort to zIIP
Added license cost	None beyond the IBM stack	Yes, MFX is an additional product

DFSORT vs Syncsort MFX, the licensing levers compared

Dimension

IBM DFSORT

Syncsort (Precisely) MFX

Vendor

IBM

Precisely

Delivery

IBM sort within the z/OS environment

Third party sort, separately licensed

Licensing basis

Priced inside the IBM stack framework

MSU capacity, own product line

zIIP offload

Runs on general processors, drives MLC

ZPSaver can offload most sort to zIIP

Effect on IBM MLC

Sort cycles count toward the MLC peak

Can lower the MLC peak by moving sort to zIIP

Added license cost

None beyond the IBM stack

Yes, MFX is an additional product

This is one of the few mainframe tool decisions where the third party product has a direct mechanism to cut IBM cost. Use it this way:

Lean toward Syncsort MFX if

Your batch is sort heavy and sort is a meaningful part of your general processor consumption
Sort visibly contributes to your four hour rolling average MLC peak
You have zIIP headroom for ZPSaver to use, and the modeled MLC reduction clears the MFX license cost

Stay with DFSORT if

Your sort volume is light and adds little to the MLC peak
You have little spare zIIP capacity for offload to land on
The MFX license cost would exceed the MLC saving your data actually supports

Either way, the decision is a sub-capacity modeling exercise: measure the sort share of your peak, the offloadable portion, and the zIIP headroom, then compare the MLC reduction to the MFX cost. Hold MFX as leverage in the IBM conversation even if you stay on DFSORT.

How are they licensed?DFSORT is priced inside the IBM stack. MFX is a third party product on MSU capacity, with a ZPSaver feature that offloads sort to zIIP to reduce IBM MLC.

Does MFX save money?It can, when the MLC reduction from zIIP offload exceeds the MFX license cost. That depends on how sort heavy your workload and MLC peak are, and on zIIP headroom.

What decides it?The MLC arithmetic, not raw speed. Model the sort share of your R4HA peak, the offloadable portion, the zIIP headroom, and the MFX cost.

What is the first step?Pull your SCRT and zIIP data and measure how much of the MLC peak is sort. The answer is workload specific, so the data decides it.

One of the few tools that can cut the IBM bill. Prove it with your own data.

Explainers: Workload License Charges history and variants and IBM Tailored Fit Pricing explained. Other comparisons: Tailored Fit Pricing vs sub-capacity and MainView vs SYSVIEW. Hubs and commercial: the Syncsort (Precisely) buyer side guide, the IBM buyer side guide, and MSU optimization.

DFSORT vs Syncsort MFX: the zIIP question, not the speed sheet.

The verdict

Head to head

Who should pick which

Frequently asked

A sort tool that moves the IBM peak. We model whether it pays.