Contents
Key takeawaysHow middleware is measuredSub capacity and ILMTCloud Pak or standalone PVUNon production environmentsVersion consolidationUsing unused entitlementsWhat we saw in 2024 and 2025What to do nextFAQIBM middleware costs follow the core count, and the core count follows your evidence. Keep ILMT current, license test servers on test terms, and convert to a Cloud Pak only when your workloads will change.
- Cores times rating. IBM middleware is licensed in Processor Value Units, where each core carries a PVU rating set by its processor family and socket count.
- Sub capacity must be proven. Sub capacity pricing depends on ILMT with quarterly reports kept for two years, and without that evidence IBM counts full capacity.
- The bundle often loses. In most Cloud Pak conversions we modelled, standalone PVU cost less for customers whose middleware was static.
- Model before converting. A conversion to a VPC pool is hard to reverse, so price both paths across the full term while both still exist.
- Test servers overpay. Roughly 20 of 30 customers licensed development, test or disaster recovery at production terms when cheaper parts applied.
- Fewer versions cost less. Consolidating WebSphere and MQ versions cuts both the cores you license and the support you pay for old releases.
How is IBM middleware licensing measured?
IBM middleware such as WebSphere Application Server and MQ is licensed in Processor Value Units (PVUs) under Passport Advantage. Every processor core carries a PVU rating set by its processor family, and the number of PVUs you need is the cores multiplied by that rating.
The rating depends on the chip and the server's socket count. Current Intel Xeon cores rate 70 PVUs on servers with up to 2 sockets, 100 on servers with up to 4 sockets and 120 above that. IBM Power9 and Power10 cores rate 70 to 120 by server model. The full list is in our PVU table for 2026.
Which cores does IBM count?
IBM counts cores in one of three ways, and the choice between them usually matters more than the discount on the order.
| Mode | What it counts | Condition | Effect |
|---|---|---|---|
| Full capacity | Every core on every host the software could run on | The default | Routinely double the sub capacity number on virtualized servers |
| Sub capacity | Only the virtual cores available to the software | Requires ILMT with quarterly report retention | Cuts PVU exposure 30 to 45 percent |
| Cloud Pak VPC | Virtual processor cores against a bundle | Conversion from PVU entitlement | Flexibility bundled at a premium paid regardless |
Why the hardware refresh changes the bill
Because the count follows cores, a hardware refresh can raise your IBM requirement with no change in workload. Moving from 2 socket to 4 socket servers lifts the PVU rating and the core count at once. Check the PVU effect of any server purchase before infrastructure signs the order. Our PVU licensing guide covers processor families in more detail.
When does sub capacity licensing cut the PVU count?
Sub capacity cuts the count whenever the software runs on virtual machines that use only part of a host, and you can prove it with ILMT reports. In the middleware reviews we ran, the saving held only where ILMT evidence supported the claim.
The discount is granted in the contract on conditions, so you cannot negotiate it and you cannot assume it. IBM's virtualization capacity rules ask for three things:
- Install ILMT. The IBM License Metric Tool must be in place within 90 days of your first sub capacity deployment.
- Report every quarter. Generate complete audit reports of license use at least once a quarter.
- Keep the reports. Retain them for two years and hand them to IBM or its auditors on request.
Miss any of these and IBM charges full capacity: every physical core activated on every host the software could run on. On a modern virtualized server that is routinely double the sub capacity figure for exactly the same deployment. The entitlement you bought is identical in both cases. What differs is whether you can show the evidence.
A worked example on three VMware hosts
Say you run WebSphere Application Server Network Deployment on virtual machines spread across three VMware hosts. Each host is a 2 socket Intel Xeon server with 16 cores per socket, so 32 cores rated at 70 PVUs each. The numbers below are hypothetical.
| Host | Physical cores | Full capacity PVUs | Peak virtual cores for WebSphere | Sub capacity PVUs |
|---|---|---|---|---|
| Host 1 | 32 | 2,240 | 20 | 1,400 |
| Host 2 | 32 | 2,240 | 16 | 1,120 |
| Host 3 | 32 | 2,240 | 12 | 840 |
| Total | 96 | 6,720 | 48 | 3,360 |
With current ILMT reports you license 3,360 PVUs. Without them IBM can claim 6,720, twice the figure, whatever support rate you pay per PVU. IBM caps each host at its physical capacity, so a host whose virtual machines add up to more than 32 cores still counts at 32 cores.
The peak matters too. ILMT records the highest number of virtual cores available to the program in the period, so a virtual machine that migrates between hosts can add to the count on more than one host. Pinning middleware virtual machines to a defined group of hosts keeps the peak close to what you actually run.
How to check your own sub capacity position
- ILMT audit snapshot. Export the last full quarter and confirm that every host running IBM middleware appears with a complete data collection.
- Report archive. Check that eight quarters of signed reports exist and that someone owns the task of signing them each quarter.
- Entitlement records. Download your PVU entitlements from Passport Advantage and set them next to the snapshot, product by product.
- Virtualization inventory. Compare the hosts in vCenter with the hosts in ILMT. A host missing from ILMT is a host IBM can count at full capacity.
The rules, the common reporting gaps and the audit consequences are covered in our guide to sub capacity and ILMT.
IBM licensing and audit defense guide
PVU and VPC rules, ILMT obligations and the renewal sequence, set out for IBM customers.
Get the white paper →Should you convert standalone PVU licenses to a Cloud Pak?
Only if your middleware use is going to change over the term. In 12 of 20 Cloud Pak conversions we modelled, staying on standalone PVU licensing cost less than the bundle for customers whose middleware was static. IBM had not priced those offers badly. The bundle simply sold flexibility those customers would not use.
A Cloud Pak such as Cloud Pak for Integration is a pool of virtual processor cores (VPCs) that can run any bundled program, including MQ, App Connect Enterprise and API Connect. If you run the same WebSphere and MQ versions you ran three years ago, that flexibility is worth close to zero, while the premium is charged every year.
Why the conversion is hard to reverse
Once PVU entitlements are converted into a VPC pool, unwinding back to standalone PVU is a route IBM does not make easy or attractive. In practice the conversion runs one way. The modeling therefore has to happen before you convert, while both options still exist, and not after the first renewal reveals the premium.
For a static environment the comparison usually takes an afternoon: the same workloads, the same servers, priced both ways across the full term. The PVU to VPC transition guide shows how IBM converts each product line.
A worked comparison over five years
The figures below are round numbers chosen for illustration, not IBM prices. Say your WebSphere and MQ PVUs cost $250,000 a year in support, and IBM offers a Cloud Pak subscription covering the same workloads at $300,000 a year.
| Scenario | Standalone PVU, 5 years | Cloud Pak, 5 years | Lower cost option |
|---|---|---|---|
| Static: same programs and servers for 5 years | $1,250,000 | $1,500,000 | Standalone, by $250,000 |
| Changing: App Connect Enterprise added in year 2, fitting inside the Cloud Pak pool | $1,570,000 | $1,500,000 | Cloud Pak, by $70,000 |
In the second row, the standalone path buys App Connect licenses for $200,000 including the first year of support, then pays $40,000 a year in support for years 3 to 5. The bundle wins only because a new program arrived and fit inside capacity already paid for. Without that project, the extra $50,000 a year buys capacity you never use.
Why "Cloud Pak is the modern choice" is the wrong test
IBM presents conversion as modernization, and many advisors repeat that framing. We think it asks the wrong question. The product version and the container platform you run have nothing to do with the license metric you pay under. Standalone PVU licenses stay supported for as long as IBM supports the product.
The test we apply is whether you will deploy new bundled programs, or shift capacity between them, during the term. For a customer consolidating, modernizing applications or adopting new integration capability, the bundle is often right. For a steady WebSphere and MQ footprint, pay for the flexibility only when you have a plan to use it.
What the IBM account team will say, and how to reply
- "Cloud Pak is where IBM is investing, so standalone parts will fall behind." Ask for the announced end of support dates for your PVU parts in writing. If none are announced, the parts remain supported and the claim does not affect the price.
- "The conversion credit is only available this quarter." Ask for the offer in writing with the conversion ratio for each product, then run the five year comparison before the deadline. A credit that saves less than the premium costs is a loss.
- "Your ILMT reports have gaps, so we have to count full capacity." Produce the retained quarterly reports, identify exactly which periods and hosts are affected, and ask IBM to limit any claim to those.
- "Test servers need the same license as production." Point to the non production parts IBM publishes for products such as MQ, and ask which clause in the License Information document supports the claim.
- Conversion ratio in the order. Fix the PVU to VPC ratio for each product for the whole term, so a later true up cannot use a different rate.
- Reduction right at renewal. The right to cut VPC or PVU quantities at the anniversary without repricing the lines you keep.
- Support price hold. A cap on the annual uplift for PVU lines you keep, so staying standalone does not become the expensive option by default.
- Non production confirmation. Written agreement on which named environments qualify for non production or high availability replica parts.
Where do non production environments waste IBM middleware spend?
Development, test and disaster recovery servers are the most common source of overspend we find. Most customers we reviewed paid production grade licenses for those environments when they qualified for cheaper terms. The servers are built by teams solving delivery problems, and no step in a renewal cycle asks how they are licensed.
Which cheaper IBM parts apply?
IBM publishes cheaper parts for some of these uses. MQ has IBM MQ for Non-Production Environment and IBM MQ Advanced for Non-Production Environment for internal development and test, plus High Availability Replica parts, formerly Idle Standby, for a copy that stays idle unless the active queue manager fails over. Our MQ licensing guide covers those parts.
Backup servers follow their own rules. IBM's licensing tools guidance says warm and cold backups can usually be excluded from PVU counts, while a hot backup doing work needs a license. Rules vary by product, so read each License Information document and put ILMT agents on backup servers so the exclusion shows in your reports.
Common mistakes with non production licensing
- Buying one part number for everything. Ordering production PVUs for every server because it is simpler. The cost is the price difference on every test and development core for as long as support runs.
- Letting test become production. A server bought on a non production part that starts serving live traffic needs a production license, and an auditor will find it in the ILMT history.
- Leaving backups out of ILMT. Without agents on the disaster recovery hosts, you cannot show that those installs were idle, so the exclusion is hard to claim.
- Assuming free developer editions cover shared test. Developer editions such as IBM MQ Advanced for Developers come with their own limits on use, and a shared integration test environment can fall outside them.
- Never revisiting the classification. Environments change role over time, so review the list at every renewal.
How does version consolidation cut WebSphere and MQ costs?
It reduces cost in two places at once. Running fewer WebSphere and MQ versions shrinks the license position, because each version stream tends to need its own servers and cores. It also shrinks the support exposure, because a version past IBM's end of support can only stay covered through separately priced extended support, or through an upgrade project.
Neither saving shows up until someone counts. Sprawl builds when each application team upgrades on its own schedule, leaving several releases of one product side by side on separate virtual machines.
How to find the sprawl
- Export the software inventory from ILMT, which reports the product version for each install.
- Group installs by product and version, and list the hosts and virtual cores behind each group.
- Mark every version with its IBM end of support date.
- Estimate the cores that would be freed if the smaller version groups moved onto the servers of the main one.
For WebSphere editions and their licensing differences, see our WebSphere licensing guide. Our work on middleware rationalization covers the consolidation project itself.
Sub capacity is a discount you prove every quarter. Stop producing the evidence and IBM can count every core you own.
How do you use unused entitlements in the next IBM negotiation?
Recovered entitlements are the cheapest currency you have in an IBM deal. Licenses freed by sub capacity, reclassified test servers or version consolidation can cover new demand without new spend, or come off the support renewal. Reclamation belongs before the negotiation starts, when the numbers can still shape the proposal.
- Partial renewals. Dropping support on some PVU lines can prompt IBM to reprice the lines you keep, so ask how a partial renewal will be priced before you give notice.
- Reinstatement. Support you drop is expensive to reinstate later, so drop only licenses you are confident you will not need again.
The wider method for finding and using unused IBM licenses is in our shelfware reduction guide, and the full library is in the IBM knowledge hub.
What have we seen in IBM middleware reviews in 2024 and 2025?
Across roughly 20 to 30 IBM middleware reviews in 2024 and 2025, the gap between what customers deployed and what they were entitled to ran in both directions at once. Some programs were overlicensed while others carried audit risk. Three patterns came up again and again.
- The bundle lost on static workloads. In 12 of 20 Cloud Pak conversions we modelled, staying on standalone PVU licensing beat the bundle for a static environment.
- Sub capacity paid when the evidence existed. Where ILMT reports supported the claim, sub capacity cut PVU exposure by 30 to 45 percent against the full capacity default.
- Non production carried production prices. Roughly 20 of 30 customers licensed development, test or disaster recovery at production terms when cheaper terms applied.
Where ILMT had lapsed, the same customers faced the full capacity count on every host the software could reach. That is why we treat ILMT as an operational control with a direct price attached, owned by someone who signs the reports every quarter.
What to do next
- This month. Confirm ILMT is running on every host with IBM middleware, and that eight quarters of signed reports exist.
- Before any Cloud Pak offer. Price your environment both ways across the full term, on the workloads you actually run and the projects you have approved.
- Next quarter. Audit development, test and disaster recovery servers and move qualifying ones onto non production or high availability replica parts.
- Six months before renewal. Group WebSphere and MQ installs by version and plan consolidation of the smaller groups.
- Three months before renewal. Decide which recovered entitlements to redeploy and which to drop, and ask IBM how partial renewal will be priced.
- At signature. Get the conversion ratio, reduction rights and support price hold written into the order. Our IBM practice can model both paths with you.
Frequently asked questions
How is IBM middleware licensing measured?
In Processor Value Units under Passport Advantage. Multiply the cores available to the software by the processor's PVU rating, which is 70 per core on a 2 socket Intel Xeon server. Under sub capacity, only the virtual cores assigned to the software count, capped at the physical host.
Is converting to a Cloud Pak always the right choice?
No. For static workloads, standalone PVU licensing usually cost less in our modelling. The ability to swap capacity between bundled programs has value only if you plan to deploy new programs or shift capacity during the term.
Why model a Cloud Pak conversion before converting rather than after?
Once PVU entitlements sit in a VPC pool, IBM does not make a return to standalone licenses easy or attractive. Run the comparison while you can still choose, before you accept any conversion credit or deadline.
How much does sub capacity licensing save?
Between 30 and 45 percent of PVU exposure against full capacity in our reviews, where ILMT evidence supported the claim. Small virtual machines on large hosts save the most.
What happens if ILMT is not running or reports are missing?
IBM can charge full capacity for the affected period: every physical core activated on every host where the software could run. Keep the archive complete, because a single missing quarter can be enough to open that claim.
Which IBM middleware environments are most often overlicensed?
Development, test and disaster recovery servers. MQ, for example, has separate non production parts and High Availability Replica parts for idle standby copies, and warm or cold backups can often be excluded from the count.
Does consolidating WebSphere and MQ versions reduce cost?
Yes. Fewer versions usually means fewer servers and cores to license, and fewer releases past end of support means less spent on extended support. Start from the ILMT inventory, which shows the version of every install.
What are unused IBM licenses worth in a negotiation?
They cover new demand without new spend, or reduce the support renewal. Check first how IBM will price a partial renewal, and remember that lapsed support is costly to reinstate.
When is a Cloud Pak bundle the right purchase?
When your middleware use is changing: you are consolidating platforms, modernizing applications or adding programs such as App Connect or API Connect during the term. The premium pays only when you use the right to shift capacity.
Is ILMT a compliance task or a commercial one?
Mostly commercial. The quarterly reports are the evidence that keeps you on sub capacity pricing, so their value is the difference between the two counts. Give one named owner the job of signing and archiving them.