ILMT bundling and exclusion rules.
Bundling is where ILMT counts quietly go wrong. A component that ships inside one product carries usage rights that end where that product ends. Use the bundled piece beyond its allowed scope and it becomes a separately licensable product the moment an auditor looks.
What bundling means under the license
Many IBM products include components that would otherwise be licensed on their own. A classic example is the Db2 that ships bundled inside Cognos. The bundled engine is licensed only for the use of the product it came with. The right does not extend to standing up that engine for another application, even though it is technically the same software.
ILMT detects the install. It does not know your intent. So a bundled component used outside its allowed scope looks identical to a full deployment, and that is exactly how an auditor reads it.
Where bundling turns into a finding
- Scope creep. A bundled database pointed at a second application beyond the parent product.
- Shared infrastructure. A bundled component consolidated onto a host serving other workloads.
- Silent reuse. A team reusing the bundled engine because it was already installed, with no entitlement for the new use.
Each of these converts a covered component into an unlicensed product in the auditor's reading, and the charge attaches to the cores it runs on.
Exclusions and what ILMT does not count
The reverse problem is over counting. ILMT will list installs that should be excluded or that are miscategorized by default, such as components that are part of an entitlement, non production copies, or software bundled into a properly licensed parent. Left uncorrected, these inflate the report and manufacture findings that are not real. The exclusion rules exist precisely so a bundled or entitled component is not double counted, but ILMT applies them only after the configuration is corrected by hand.
Getting the bundling line right
A defensible count needs both directions checked. Confirm that every bundled component stays inside its allowed scope, and confirm that ILMT is not counting entitled or excluded installs against you. That reconciliation, mapping each detected install to the right it actually carries, is what separates a clean sub capacity position from a report full of avoidable findings.
Bundling cuts both ways under audit. A bundled component used beyond its parent product becomes separately licensable, while ILMT will over count entitled or excluded installs until the configuration is corrected by hand. Map every install to the right it carries, in both directions, and the bundling findings disappear.
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 →The IBM Audit Brief
Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.
Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.