BMC AMI mainframe licensing is the way BMC Software licenses its mainframe software on IBM Z. The same measures apply to other BMC mainframe products, such as the mainframe components of Control-M. It is licensed by the computing capacity of the machines it runs on or serves. BMC’s unit-of-measure page defines this capacity in several ways: millions of service units (MSU), millions of instructions per second (MIPS), MIPS of a logical partition (LPAR), general-purpose engines, LPAR connections or whole sysplexes.[1] The Order fixes which measure applies and the Licensed Capacity. The TSMA and EULA prohibit use in excess of it.[2][3] BMC’s mainframe measures are defined by BMC. They are related to, but separate from, the IBM sub-capacity pricing described in IBM sub-capacity licensing and ILMT.
Editions
BMC’s documentation names mainframe products in its licence restrictions rather than publishing an edition matrix. The named products include BMC AMI Storage IAM, BMC AMI DevX Code Pipeline, BMC Capacity Management for Mainframes (with the related Performance Analyzer, Predictor and Perceiver products), and BMC Subsystem Optimizer for DB2 and for IMS.[1] The same unit-of-measure page is published in each product’s documentation space, for example BMC AMI Apptune for Db2. Each product’s Order selects from its measures.[1] BMC publishes no price list for these products.
Metrics
| BMC unit of measure | Catalog row | What BMC counts |
|---|---|---|
| per MSU | per MSU | Total aggregate MSUs of each Computer, including all Computers coupled in a parallel Sysplex, on which the Product is installed or which it manages or monitors[1] |
| per MIPS | per MIPS | The same scope, measured in MIPS[1] |
| per MIPS (LPAR) | per MIPS (LPAR) | MIPS of each LPAR, including LPARs coupled in a parallel Sysplex[1] |
| per engine | per engine | Each general-purpose engine on the server the Product is installed on or manages[1] |
| per LPAR | per LPAR | Each LPAR connection to the Server on which the Product is installed[1] |
| per sysplex | per sysplex | Each group of IBM computers or systems that forms a system complex[1] |
The page also defines per Linux engine, covering all engines of a mainframe running Linux and classified by Linux Group. It defines per session, one licence per mainframe console device connection. A variant of per MIPS counts MIPS “for each Computer as defined in the Statement of Capacity Information”.[1] Control-M’s mainframe products use the same per MIPS wording.[6] Discovery for z/OS, an add-on to BMC Helix Discovery, “is licensed based on the MIPS capacity of the z/OS environments being discovered”.[7]
Counting / floors
Ratings (as retrieved 2026-09-27). MSU Rating is “the aggregate computing power (expressed in millions of service units) of a Computer, using the MSU rating set forth in the then current Gartner Group Rating Guide”. MIPS Rating is defined the same way in millions of instructions per second. Computer-specific passwords are issued for the Product.[1] For licences based on the power of a computer, the customer agrees to use BMC’s then current computer classification scheme.[1] BMC defines a mainframe Computer as “an individual mainframe computer having single or multiple processors or engines”.[1] Catalog proof: MSU and MIPS licences include every computer coupled in a parallel Sysplex; Power-based licences use BMC's computer classification scheme.
MSU to MIPS ratio. BMC’s General Definitions state that the parties use the IBM MSU unit “in order to closely align to the mainframe platform licensing model, associated baselines and to simplify reporting”. BMC’s per MSU (consumption) model converts at “an 8.2 MIPS to 1 MSU ratio based on the mainframe models in use at the time of this Order”.[1] The ratio is the Gartner MIPS rating of the mainframe model divided by its IBM MSU rating, averaged across models where there are several. No further conversion applies during the Term. The parties agree to renegotiate in good faith for extensions or future orders if new IBM models deviate substantially.[1] For example, under this definition a 4,100 MIPS entitlement converts to 500 MSU. Catalog proof: BMC converts MIPS to MSU at 8.2 to 1 for the Order term.
Managed, not only installed. The MSU, MIPS and engine measures count Computers “upon which the Product is installed, or which is managed or monitored by the Product”.[1] BMC Capacity Management for Mainframes goes further. It must be licensed for every Computer for which it processes data or runs functionality, “regardless of whether the Product or one of its components is specifically installed on that Computer”. It may be installed on or moved to any Computer in the licensed environment.[1] Catalog proof: BMC Capacity Management for Mainframes covers every computer it processes data for.
Inclusions and bundled components. BMC AMI DevX Code Pipeline includes one LPAR; additional LPARs must be licensed separately.[1] BMC Subsystem Optimizer for DB2 and for IMS ship with BMC Application Restart Control and MainView Batch Optimizer. Those components may be used only within the Subsystem Optimizer implementation unless licensed separately.[1] Catalog proof: BMC AMI DevX Code Pipeline includes one LPAR.
Floors. No minimum MSU or MIPS quantity is published. The Licensed Capacity is whatever the Order states.[2]
Virtualization & partitioning
The mainframe equivalent of a partitioning policy lies in the Sysplex wording and in product-specific restrictions:
- Sysplex aggregation. The per MSU and per MIPS measures include “all Computers coupled in a parallel Sysplex environment”. A Product used in a Sysplex is therefore sized on the coupled machines, not only the machine where it is installed.[1]
- LPAR measures. Where a Product is sold per MIPS (LPAR), the count is the MIPS of each logical partition. Computer and LPAR specific passwords are issued. Unlike the per MIPS measure, which counts the whole Computer, it licenses the capacity of individual partitions.[1]
- Data sharing. For BMC AMI Storage IAM, the customer may not use IBM PR/SM Sysplex or Datasharing capabilities to derive benefit on an unlicensed Computer. For example, a Product licensed on Computer “A” cannot act on data derived from an unlicensed Computer in the Sysplex. Additional Capacity must be licensed before any such use.[1] Catalog proof: BMC AMI Storage IAM may not extend benefit to unlicensed Sysplex members.
For the cross-vendor background, see virtualization and partitioning.
Cloud / BYOL
The retrieved BMC documents contain no cloud or BYOL provisions for mainframe products. The unit-of-measure page defines Cloud Environment and Cloud Service Provider terms, but applies them to service-provider measures such as per development site, not to MSU or MIPS licensing.[1]
Programs
- On Premises Subscriptions. BMC mainframe software bought under the TSMA is a term licence up to the Licensed Capacity for internal business operations. Outsourcing or service-bureau use on behalf of non-Affiliates is prohibited.[2] Under the EULA, a licence is perpetual only if the Order provides it.[3]
- Statement of Capacity. BMC’s License Compliance Office runs a Statement of Capacity program “for customers and products covered by Enterprise Agreements”.[5]
- IBM Tailored Fit Pricing. BMC’s FAQ explains IBM’s Tailored Fit Pricing solutions and notes that customers may stay on IBM’s monthly licence charge model.[4] On what happens to a BMC contract if the customer moves to Tailored Fit Pricing, it says: “This will be discussed on a case by case basis”.[4] Catalog proof: Moving to IBM Tailored Fit Pricing does not change a BMC contract automatically.
Audits and compliance
BMC’s audit clause names mainframe reporting explicitly. At most once a year, BMC may request the prior 12 months of “third party usage reports related to the On Premises Subscriptions (e.g., SCRT reports)”, delivered within 30 days. The request also covers product-generated usage reports, and written reports where a product generates none.[2] The EULA contains the same clause.[3] SCRT output is therefore part of the evidence BMC can ask for. Any excess over the Licensed Capacity is quoted through the end of the Order term.[2] Catalog proof: BMC may request 12 months of usage reports once a year; Excess capacity found in an audit is quoted to the end of the Order term. See BMC Software agreements, audit and compliance.
Out of scope
IBM’s own mainframe software licensing (MLC, sub-capacity and Tailored Fit Pricing contracts with IBM) is outside this page; see IBM sub-capacity licensing and ILMT. Mainframe hardware capacity and BMC AMI cost-optimization features are not licence terms and are not covered here. Neither are the terms of negotiated BMC Enterprise Agreements, which are not published.[5]