>
Journal · Sub-Capacity

The ILMT sub capacity trap that triggers full capacity charges.

Sub capacity licensing is the single largest saving on most IBM estates, and the easiest to lose. Miss one ILMT requirement and IBM stops charging for the cores you use and starts charging for the whole host. On one server that can turn 480 PVU into 3,840 PVU.

What sub capacity is worth

Sub capacity licensing lets you license only the virtual cores running IBM software instead of the entire physical host. Take WebSphere using four of the 32 cores on a host. Sub capacity licenses that at 480 PVU. Full capacity licenses all 32 cores at 3,840 PVU. Same deployment, eight times the cost, decided entirely by whether your ILMT posture holds.

The four conditions you have to meet

To claim sub capacity, IBM requires all of the following, not some of them:

Fail any one of these for a period and IBM defaults that period to full capacity charging. The conditions are joined by AND, not OR, which is the heart of the trap.

How the trap springs in an audit

It rarely springs because someone ignored ILMT. It springs because an agent quietly stopped reporting, a new cluster was never added, the quarterly reports were not kept, or VPC metered products moved under sub capacity reporting after Passport Advantage v11 and the process did not follow. Each gap is small. The charge is not, because the lookback can run 2 to 5 years at full capacity rates.

Closing the trap before an auditor finds it

The defensible posture is provable, not assumed. That means agents reporting on every eligible host, quarterly reports archived, and the configuration corrected for the installs ILMT miscategorizes by default. Validate it on your own schedule and the sub capacity claim holds when IBM tests it, which is the difference between 480 PVU and 3,840 PVU on every host in scope.

What this means under audit

Sub capacity is not a setting you switch on once, it is a posture you have to keep provable every quarter. ILMT deployed, running, reporting and retained, on eligible virtualization, all at the same time. Miss one condition for one period and the whole host is charged at full capacity for the entire lookback.

What triggers full capacity charging under ILMT?
Failing any sub capacity condition for a period: ILMT not deployed within 90 days, agents not reporting, quarterly reports not retained for two years, or ineligible virtualization. IBM then charges the full physical host for that period.
How far back can full capacity charges reach?
The audit lookback can run 2 to 5 years. Any period where the sub capacity conditions were not met can be recharged at full capacity rates for the whole host.

ILMT posture in doubt?

Our ILMT Remediation engagement corrects the configuration, restores missing agents, and rebuilds a defensible sub capacity record before an auditor reads it. We mobilize within 48 hours of your audit notice.

See ILMT Remediation →
Related reading

The IBM Audit Brief

Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.

IBM Audit

Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.

Services
Audit DefenseAudit NegotiationILMT RemediationSub-Capacity Defense
Products
WebSphereDb2CognosCloud Pak
Company
AboutContactJournalWhite Papers
Independent. Not affiliated with IBM Corporation.Buyer Side · Est. 2019