A four socket sixty four core server licensed at full capacity costs eight times what the same server licensed at sub capacity costs. The 8x ratio compounds across every virtualized host. ILMT compliance is the operational discipline that makes the ratio real.
IBM sub capacity licensing rewards buyers who keep ILMT deployed and reporting, and exposes those who virtualize PVU products without it to full capacity charges that can run many times the real consumption.
Key takeaways
For PVU based products, sub capacity lets you license the virtual cores a product actually uses rather than the whole physical server. That is the whole saving.
The right to license sub capacity is conditional. It applies only when you meet the terms in the IBM sub capacity licensing terms.
Full capacity is the fallback when the sub capacity conditions are not met. The host is licensed as if the product could use every physical core, which is where the large multiple comes from.
Sub capacity eligibility requires the IBM License Metric Tool deployed, scanning all relevant hosts, and producing quarterly reports you retain. Anything less risks full capacity.
The tool requirements and supported environments are set out in the IBM License Metric Tool documentation.
Sub capacity versus full capacity, illustrative PVU exposure
| Condition | ILMT status | Licensed basis | Cost effect |
|---|---|---|---|
| Compliant sub capacity | Deployed and reporting | Virtual cores used | Lowest, matches use |
| Partial coverage | Some hosts unscanned | Full capacity on gaps | Multiplied on the gaps |
| No ILMT | Missing | Full physical capacity | 4 to 8 times typical |
The standard assumption is that sub capacity savings are automatic once you virtualize PVU products, so teams focus on the architecture and treat ILMT as a formality. We disagree. In roughly 1 of 3 IBM estates we reviewed in 2024 and 2025, ILMT was present but not scanning every host, or its quarterly reports were not retained, which under the terms reverts the gaps to full capacity at 4 to 8 times the real use. The buyer side move is to treat ILMT operation as the license itself. Verify complete host coverage, confirm the quarterly reports generate and are retained, and audit the trail before IBM does.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Sub capacity savings are not automatic. ILMT operation is the license. Treat it that way.
The risk is not the virtualization design, it is the evidence. An audit asks for the ILMT reports, and gaps in coverage or retention convert directly into full capacity charges.
Partial coverage is the quiet trap. One unscanned host running a PVU product can carry a full capacity charge while the rest of the estate is compliant.
Installing ILMT late stops future exposure but does not erase the period it was missing. The ninety day window is a forward condition, not a retroactive cure.
Run ILMT as a controlled service, not a background install. The reports are the asset.
ILMT must scan every virtualization technology running a PVU product, including the supported hypervisors listed in the IBM License Metric Tool release documentation. An unsupported environment can break the sub capacity claim.
Get the buyer side framework our advisors use on live IBM audits. The PVU math, the ILMT remediation steps, and the sub capacity sequence.
Download the Audit Defense KitSub capacity licensing lets you license PVU based IBM products to the virtual cores a product actually uses rather than the full physical server. It can cut PVU consumption substantially, but only when the sub capacity conditions are met.
The IBM License Metric Tool is the condition for sub capacity eligibility. It must be deployed, scanning all relevant hosts, and producing retained quarterly reports. Without it, IBM licenses the product at full physical capacity instead.
Full capacity is the fallback basis when the sub capacity conditions are not met. The host is licensed as if the product could use every physical core, which in practice often runs 4 to 8 times the real virtualized consumption.
ILMT must be deployed within ninety days of the first sub capacity deployment of a PVU product. The window is a forward condition for eligibility, not a retroactive cure for a period when the tool was missing.
ILMT must generate quarterly sub capacity reports covering every host running a PVU product, and those reports must be retained, typically for at least two years, to form the audit trail that supports the sub capacity claim.
Partial coverage. ILMT is deployed but not scanning every relevant host, or its reports are generated but not retained. Either gap reverts the affected hosts to full capacity, which is the single most expensive avoidable IBM audit finding.
No. Installing ILMT late stops future full capacity exposure but does not erase the period it was missing. That is why complete coverage and retention from the start matter more than remediation after the fact.
Treat ILMT operation as the license itself: inventory every PVU host, verify complete scanning, confirm the quarterly reports generate and are retained, and self audit the trail before IBM does, so gaps are closed before they become findings.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
