Explainer · Sysplex Pricing

Aggregation cuts the rate, until the catch bites.

Combining machines in a qualifying Parallel Sysplex prices their MSUs as one larger figure, and because rates are regressive, that lowers the effective per MSU cost. But the 50 percent workload rule and full capacity metrics can quietly reverse the gain. This is a model, not a default.

№ 01

Why aggregation lowers the rate

Regressive bandsAggregation

Mainframe software pricing is regressive. The per MSU rate falls as the MSU total rises through successive bands, so the same workload is cheaper per unit at a higher aggregate level. Sysplex aggregation exploits this by letting you combine the eligible MSU capacity of multiple machines in a qualifying Parallel Sysplex and price the total as one larger figure rather than several smaller standalone figures. The combined total reaches deeper into the regressive schedule, and the effective rate across the estate drops.

Standalone is the opposite position. Each machine is priced on its own MSU figure, so two boxes of 300 MSU are each rated in the lower MSU bands at the higher per unit rate, instead of one 600 MSU figure rated partly in the cheaper bands. For multi machine estates, that difference compounds across every Monthly License Charge product on the floor.

№ 02

The rate effect, worked

Worked examplePer MSU

Take two machines of 300 MSU each. Standalone, each is priced from the top of a regressive schedule on its own. Aggregated, the 600 MSU total runs further down the same schedule, so more of the capacity is priced in the cheaper bands. The table uses an illustrative regressive schedule to show the effect on the blended per MSU rate.

Worked example · two 300 MSU machines, standalone vs aggregated (illustrative rates)
BasisMSU pricedBlended rate indexRelative cost
Machine A standalone300100300 units
Machine B standalone300100300 units
Standalone total600100600 units
Aggregated 600 MSU60086516 units

Aggregating the same 600 MSU into one priced figure pulls the blended rate index from 100 to 86 in this illustration, roughly a 14 percent reduction on the combined MLC, because more of the capacity falls into the cheaper bands of the regressive schedule. The real number depends on your bands and metric. The mechanic, deeper bands at a lower rate, is the point.

№ 03

Sysplex vs standalone at a glance

Comparison
The trade between the two positions
DimensionAggregated sysplexStandalone
Per MSU rateLower, reaches deeper bandsHigher, each box priced alone
Capacity basisSome metrics full capacity (PSLC)Sub-capacity WLC available
Qualifying conditionsCoupling links, shared CF, workload shareNone to maintain
Workload variability fitWeaker if full capacity pricedStronger under sub-capacity
Eligibility riskConfig change can break itStable, no threshold to hold
Best forSteady, high MSU estatesVariable or smaller estates
№ 04

Where it bites, and how to optimize

50% ruleFull capacity

Two catches recur. First, qualification must hold continuously. A common requirement is that the sysplex LPARs running the systems enablement function represent at least 50 percent of the workload on each machine, alongside coupling links to a shared Coupling Facility. A configuration change can quietly drop you below the threshold and collapse the aggregation. Second, some aggregation metrics, notably Parallel Sysplex License Charges (PSLC), price at full capacity rather than the Rolling 4-Hour Average, so a lower headline rate can be offset by losing sub-capacity billing on variable workloads.

Buyer side levers

  • Model both positions against twelve months of real workload data before choosing, never default to one
  • Confirm the qualifying conditions hold continuously, and set a check so a configuration change cannot silently break eligibility
  • Compare full capacity aggregation against sub-capacity standalone on your actual variability, not on the headline rate alone
  • Verify the current aggregation rules with IBM for your exact machines and metrics, since the conditions are configuration specific
  • Re-test the decision at every hardware refresh, because new MSU ratings and metric eligibility can flip the answer
№ 05

Frequently asked

FAQ
Q1
What is sysplex aggregation?Combining the eligible MSU capacity of multiple machines in a qualifying Parallel Sysplex so it is priced as one larger figure. Because rates are regressive, the higher total lowers the effective per MSU rate.
Q2
What are the qualifying rules?Commonly at least two machines on coupling links to a shared Coupling Facility, with sysplex LPARs representing a substantial workload share per machine, often cited as 50 percent. Verify the current rules with IBM.
Q3
Is sysplex always cheaper?No. Aggregation lowers the rate, but some metrics like PSLC are full capacity, so for variable workloads a sub-capacity standalone position can sometimes win. It depends on band, variability, and metric.
Q4
What is the catch?Eligibility must hold continuously and a config change can break it, and full capacity metrics can offset the rate cut by losing sub-capacity billing. Both are reasons to model before committing.

Model it. Do not default to it.

Audit notice or renewal under 18 months out? We mobilize within 48 hours.

The rate cut can reverse. We will model both ways.

Get expert help