Enterprise Analyzer licensing: an analysis tool priced per user.

Rocket Enterprise Analyzer is an application understanding and intelligence platform that reads a large legacy code base, predominantly COBOL and PL/I with data access such as QSAM and VSAM, and builds a central repository describing the programs, data flows, and dependencies. From that repository it supports impact analysis, business rule extraction, and modernization planning, with newer releases adding generative assistance over the same knowledge base. It came to Rocket Software (Micro Focus) through the OpenText Application Modernization and Connectivity acquisition completed in 2024. The analysis itself runs off the mainframe, so this is analyst and developer tooling licensed by people, used to understand an estate before it is changed or migrated.

Enterprise Analyzer is typically licensed per user, by named or concurrent users who work in the tool and its repository, rather than by mainframe MSU capacity. A notable detail is that Business Rule Manager, although installed by the same Enterprise Analyzer installer, is licensed separately, so the entitlement is more than one line and easy to misread. Because the basis is users, the practical measurement is the count of analysts, developers, system integrators, and any service accounts that access the repository, against the named or concurrent entitlement held. The model is straightforward; the separate module and the shared project access are where it is misread.

Directional and pattern level. Confirm the user basis and whether Business Rule Manager is entitled in your own Rocket schedules before modeling a renewal.

The first driver is the user count, since the tool scales with the analysts and developers entitled to it, and modernization teams expand and contract over a program's life. The second is the module structure, where Business Rule Manager and any add ons are separately licensed and can be carried whether or not they are used. The third is project span, because Enterprise Analyzer is usually bought to enable a specific initiative, and the entitlement often outlives the project, drifting into open ended cost long after the analysis work that justified it has finished. The genuine question at renewal is how many people still need it and for what.

Enterprise Analyzer exposure is mostly user and module drift. Common traps we see at pattern level:

Because Enterprise Analyzer is a per user tool tied to programs of work, the levers are about counts, modules, and timing. The five that pay:

Application understanding is a contested space, and Enterprise Analyzer faces credible alternatives, including IBM Application Discovery and Delivery Intelligence for the same impact analysis role, and a range of newer code intelligence and generative analysis tools. The switching cost is lower than for a production database or transaction engine, because the repository is built from the code rather than embedded in operations, but the analysis work itself, the rules already extracted, and the team's familiarity carry over only partly. The practical approach is to right size users and confirm the modules in use first, then use a genuinely scoped alternative as a reference point in the renewal. Where the tool was bought for a project that has ended, the strongest lever is simply not renewing what is no longer needed.