Home / Compuware / File-AID Licensing
① Product · Compuware (BMC)
File-AID is Compuware (BMC) test data management, licensed on MSU capacity and renewed inside the wider BMC relationship. Here is how the metric works and what to pull at renewal, from the buyer side.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →File-AID is Compuware's mainframe data and test data management suite, now sold under BMC as part of the BMC AMI DevX family following BMC's acquisition of Compuware in 2020. It lets developers browse, edit, compare, extract, and subset data across Db2, IMS, VSAM, and sequential files, and build right sized test data without cloning full production volumes. The suite spans several variants, including File-AID for MVS, File-AID for Db2, and File-AID for IMS, sharing a common files component. Buyers still search it as File-AID and Compuware File-AID; on current order forms it appears as BMC AMI DevX File-AID.
File-AID is licensed on mainframe capacity measured in MSU, consistent with BMC's mainframe model. BMC's published documentation has historically used a MIPS to MSU conversion in the order of 8.2 MIPS to 1 MSU, and the product commonly must be licensed for the environment in which it processes data, not just the single LPAR where the load library sits. The annual maintenance stream is the renewable part, and it is usually folded into the broader BMC and Compuware relationship.
| Element | How File-AID is treated |
|---|---|
| Charge model | License plus annual maintenance, BMC mainframe model |
| Metric | Capacity in MSU |
| Conversion reference | Historically ~8.2 MIPS to 1 MSU in BMC docs |
| Licensed scope | The environment where File-AID processes data, not only the install LPAR |
| Renewable element | Annual maintenance and support |
Directional summary. Your contract metric, conversion, and licensed environment definition govern over any published figure.
Three drivers set the File-AID number. The licensed MSU capacity, because the charge tracks the size of the environment File-AID is entitled against rather than the tool's own footprint, so a refresh that grows the box grows the bill. The variant set, because File-AID for MVS, for Db2, and for IMS are entitled separately and scope creep across them lifts the cost quietly. And the licensed environment definition, because BMC mainframe entitlements often cover every machine that processes data in scope, which is wider than the single LPAR teams assume. The annual maintenance stream then compounds on top of all three.
The recurring traps are structural. Capacity growth from a hardware refresh that is never rebaselined, so the entitlement inflates with the machine. Environment scope, where File-AID processes data on LPARs beyond the licensed set, which the broad BMC environment definition makes easy to trip over. And variant sprawl, where File-AID for Db2 or for IMS gets switched on beyond the entitled components. Because the metric is a stated MSU figure rather than a metered monthly peak, an estate that has consolidated or shed capacity often keeps paying for MSU it no longer uses, and only a reconciliation surfaces it.
The structural lever is the capacity basis: rebaseline the licensed MSU against the environment File-AID actually processes on today, and challenge any environment definition that sweeps in capacity the tool never touches. The scope lever is component consolidation, paying only for the File-AID variants in genuine use. The contract levers are a cap on the annual maintenance uplift and negotiating File-AID inside the wider BMC and Compuware relationship, since post acquisition BMC commonly renews the Compuware tools as part of a broader AMI conversation, which is leverage if you control the timing. A credible alternative test data management tool named at the table is itself leverage even when migration is not the plan. This is the buyer side work we do on Compuware renewals under BMC ownership.
File-AID is Compuware's mainframe data and test data management suite, now sold under BMC as part of the BMC AMI DevX family after BMC acquired Compuware in 2020. It lets developers browse, edit, compare, extract, and subset data across Db2, IMS, VSAM, and sequential files, and build right sized test data without copying full production volumes. Buyers still search it as File-AID and Compuware File-AID, and it appears on order forms under the BMC AMI DevX File-AID name.
File-AID is licensed on mainframe capacity measured in MSU, consistent with BMC's mainframe model. BMC's documentation has historically applied a MIPS to MSU conversion in the order of 8.2 MIPS to 1 MSU, and the product must commonly be licensed for the environment in which it processes data, not only the LPAR where it is installed. It carries an annual maintenance stream that is the part you renew.
The common traps are capacity growth from a hardware refresh that is never rebaselined, environment scope where File-AID processes data on LPARs beyond the licensed set, and component sprawl across the File-AID variants for MVS, Db2, IMS, and the common files that get entitled and switched on separately. Because the metric is stated MSU rather than a metered peak, a consolidated estate often keeps paying for capacity it has shed.
Rebaseline the licensed MSU against the capacity File-AID actually processes on today, consolidate to the components genuinely in use, cap the annual maintenance uplift, and negotiate File-AID inside the wider BMC and Compuware relationship rather than as an isolated line, since post acquisition BMC commonly renews the Compuware tools as part of a broader AMI conversation. A credible alternative test data tool named at the table is leverage even when migration is not the plan.
Publisher hub: Compuware (BMC) mainframe licensing. Related products: Abend-AID licensing and Xpediter licensing. Related metric: MSU explained. Put it to work: Compuware renewals under BMC ownership.