① Explainer · Licensing concept
Aggregation pools your MSU across machines so you pay the base charge once and price the combined total further down the tiered curve. Done right it cuts MLC materially. The rules are precise, the saving is real, and the trap is assuming you qualify. Here it is, worked.
The same total MSU, priced once across a sysplex instead of separately on each machine, is cheaper. That is the whole idea, and it is worth real money.
Sysplex aggregation is the IBM pricing rule that lets you combine the MSU of a sub-capacity eligible product across all the machines in one Parallel Sysplex when its charge is calculated. You pay the per product base charge once for the sysplex, and the MSU across the qualifying machines is summed and priced together. Because MLC pricing is tiered, with the cost per MSU falling as volume rises, summing pushes the combined total further into cheaper tiers than pricing each machine standalone from the top of the curve.
The qualifying bar is technical and exact. The machines must be actively coupled, physically attached by coupling links to a common Coupling Facility and synchronized for sysplex operation, per IBM's stated criteria. A machine can belong to only one Parallel Sysplex for pricing purposes, and IBM can require verification through measurement reports. The common, expensive mistake is to assume aggregation applies and price a renewal on it without confirming the configuration actually qualifies. The worked comparison below shows the size of the prize and why the rules matter.
One product running on three machines. Pricing uses a simplified tiered curve where the cost per MSU falls as cumulative MSU rises. Standalone, each machine starts at the top of the curve and pays its own base. Aggregated, the base is paid once and the 600 combined MSU is priced down the curve. Index figures, not quotes.
| Machine | Peak MSU | Standalone cost index | Role in aggregate |
|---|---|---|---|
| Machine A | 300 | 300 | Pays base, top tier MSU |
| Machine B | 200 | 210 | Pays base again standalone |
| Machine C | 100 | 115 | Pays base a third time |
| Standalone total | 600 | 625 | Three bases, three top tiers |
| Aggregated total | 600 | 470 | One base, 600 MSU down the curve |
Standalone, the three machines cost a combined index of 625 because each pays its own base charge and each starts at the expensive top of the tiered curve. Aggregated, the single base and the 600 MSU priced together down the curve land at 470, a 25 percent reduction on this illustrative model, with no change to workload. The actual saving depends on the product, the tier structure, and whether the sysplex qualifies.
Aggregation is one of the larger structural levers in MLC pricing, but it lives behind a precise technical gate. The rules below are where buyers either capture the saving or lose it, usually by assuming eligibility that the configuration does not support, or by leaving a qualifying sysplex priced as standalone machines because nobody checked. Each rule is a question to answer against the real estate before the number goes into a renewal.
| Rule | What it requires | Where it bites |
|---|---|---|
| Actively coupled | Coupling links to a common Coupling Facility, sysplex synchronized | Loosely coupled machines do not qualify |
| One sysplex per machine | A machine prices in only one Parallel Sysplex | Cannot aggregate the same box twice |
| Verification | IBM can require RMF or sysplex calculator data | Claims must survive measurement |
| Base charge once | Per product base paid once for the sysplex | Standalone pricing duplicates the base |
Aggregation eligibility and benefit depend on your machine topology, coupling configuration, and IBM's current terms. These are the criteria as IBM commonly states them; confirm against the actual configuration before relying on them.
Aggregation is where the SCRT peaks and the R4HA across machines are pooled into one charge, and it sits in the lineage traced in IBM Z software pricing history from PSLC to TFP, where Parallel Sysplex License Charges first introduced the rule. It interacts directly with sub-capacity versus full capacity eligibility and feeds your cost per MSU. Confirming eligibility and capturing the saving is the work on mainframe cost optimization and license negotiation.
Audit notice or renewal under 18 months out? We mobilize within 48 hours. Want to know whether your sysplex qualifies before you price the renewal on it? Start here.
Sysplex aggregation is the IBM pricing rule that lets you combine the MSU of a sub-capacity eligible product across all the machines in one Parallel Sysplex when calculating its charge. You pay the per product base charge once for the sysplex, and the MSU across the qualifying machines is summed and priced together, which usually lands in a more favorable position on the tiered price curve than pricing each machine standalone.
The machines must be actively coupled: physically attached by coupling links to a common Coupling Facility and synchronized for sysplex operation, per IBM's stated criteria. A machine can be in only one Parallel Sysplex for pricing purposes. IBM can require verification through measurement reports such as RMF or its sysplex calculator. The technical qualification is precise, which is why aggregation eligibility should be confirmed against the actual configuration before it is claimed or assumed in a renewal.
Two effects. First, you pay the per product base charge once for the sysplex instead of once per machine, removing duplicated base charges. Second, MLC pricing is tiered so that the cost per MSU falls as volume rises. Summing MSU across machines pushes the combined total further up the curve into cheaper tiers, so the same total MSU is priced lower aggregated than split across several standalone machines each starting at the top of the curve.
Rarely on its own, but the configuration around it matters. Restructuring a sysplex to qualify or to add machines has operational and resilience implications that can outweigh the licensing saving, and a machine forced into one sysplex for pricing cannot aggregate into another. The licensing benefit should be modeled alongside the architectural cost, not in isolation. Aggregation is a strong lever, but it is a configuration decision first and a pricing decision second.