Catalog Manager licensing: a Db2 admin tool priced on mainframe capacity.

BMC AMI Catalog Manager for Db2, formerly Catalog Manager for Db2, is a BMC tool that gives database administrators an ISPF based gateway to the Db2 for z/OS catalog. Through simple menus and panels it lets an administrator search and act on Db2 objects, browse and edit table and view data, copy data between tables, build and run SQL, issue Db2 commands, and submit utility jobs interactively, all without needing complete knowledge of Db2 internals or SQL syntax, because the product builds the statements and lets the user choose when and how to run them. It is part of BMC's AMI Data for Db2 family, the database administration and management portfolio for Db2 on the mainframe, sitting alongside tools for backup, recovery, reorganization, and performance. Catalog Manager is the day to day administrator's console into the Db2 catalog.

Catalog Manager is licensed on mainframe capacity, measured in MSU or MIPS, scaled to the LPARs where it runs against the Db2 subsystems it manages, rather than by the number of administrators using it. BMC has been moving its mainframe portfolio toward a consumption oriented model, so the contract vehicle can be a traditional capacity license or a consumption arrangement depending on the agreement, and the basis is the capacity of the systems, not the seat count. Because Catalog Manager is one tool within the broader BMC AMI Data for Db2 portfolio, it is frequently licensed alongside other Db2 tools as part of a wider deal, which means the suite framing matters as much as the single product line. What you hold is best read against the whole BMC Db2 footprint, not in isolation.

Directional and pattern level. Confirm the capacity metric, the consumption terms, and how Catalog Manager sits within your BMC AMI Data for Db2 schedules before modeling a renewal.

The first driver is licensed capacity, the MSU or MIPS of the LPARs where Catalog Manager runs against Db2, which is the headline on a capacity priced tool. The second is the Db2 estate footprint, because the tool tracks the subsystems and systems it manages, and as the Db2 estate grows across production, development, test, and disaster recovery, the capacity basis grows with it. The third is the portfolio framing, since Catalog Manager is rarely bought alone, and a bundled BMC AMI Data for Db2 deal can obscure what this one tool contributes and whether every bundled component is needed. The fourth is branding drift, where the move from Catalog Manager to BMC AMI Catalog Manager can blur what the current entitlement grants against older paperwork. The volume of catalog activity is rarely the cost; the licensed capacity and the portfolio framing are.

Catalog Manager exposure is mostly capacity attribution and portfolio scope. Common traps we see at pattern level:

Because Catalog Manager is a capacity priced Db2 tool inside a wider BMC portfolio, the levers are about capacity, scope, and the bundle. The five that pay:

Db2 administration is a crowded category, with IBM's own Db2 administration and management tools, Broadcom (CA) Db2 tooling, and other vendors all offering catalog navigation, data editing, and utility management, which makes displacement more realistic here than for sticky control plane software. But a Db2 tooling switch still carries retraining of administrators, rebuilding of saved queries and procedures, and revalidation that every administrative workflow still works, and where Catalog Manager is bundled into a wider BMC AMI Data for Db2 agreement the economics are set by the whole portfolio, not the one tool. The practical approach is to validate the capacity, scope the estate, and negotiate the portfolio first, where most of the saving sits, and to keep a credible move to IBM or alternative Db2 tooling as real leverage. Where a Db2 tooling consolidation is already underway, Catalog Manager belongs inside that wider decision.