BMC Control-M licensing covers the terms under which BMC Software sells Control-M, its workload automation and orchestration product. Control-M comes in two forms: self-hosted, delivered as On Premises Subscriptions, and Control-M SaaS, delivered as Subscription Services. The self-hosted product is licensed by the number of jobs it schedules, which BMC calls Tasks. It can also be licensed by the number of server endpoints it manages or by mainframe MIPS. Control-M SaaS is licensed by the number of job executions.[1] The unit of measure that applies is the one named on the Order. The TSMA caps use at the Licensed Capacity for self-hosted software and at the Capacity for SaaS.[6] See BMC Software licensing for the master agreements.
Editions
BMC’s Control-M License Entitlements page lists the units of measure available for each Control-M product.[1]
| Product | Available UOMs |
|---|---|
| Control-M/Enterprise Manager | Tasks, Control-M/Server Endpoint, MIPS[1] |
| Control-M Output Management | MIPS and Tasks[1] |
| Control-M Mainframe Extension Pack | MIPS and Tasks[1] |
| Control-M JCL Verify | MIPS and Tasks[1] |
| Control-M SaaS | Per Execution - SaaS[1] |
BMC’s public pricing page shows two plans. The Starter Pack (SaaS) is “Starting at $2,400 /month” and billed annually. It is a SaaS deployment available on the AWS marketplace, with 24x7 support and automatic upgrades. The Enterprise plan is “Contact for pricing”. It offers SaaS, self-hosted or hybrid deployment, “Customizable usage models and contract options”, and availability on the AWS and Google Cloud Platform marketplaces.[3] According to BMC, the Starter Pack is not a reduced edition: “you get the full functionality. Only execution volume is capped”.[3] Catalog rows: Control-M Starter Pack (SaaS) and Control-M Enterprise.
The unit-of-measure page also names the SaaS execution packs BMC Helix Control-M Start with 500 Executions and BMC Helix Control-M Scale with 500 Executions, with non-production counterparts. It also names additional production and non-production tenants, sold per instance.[2] These are recorded as BMC Helix Control-M Start with 500 Executions, BMC Helix Control-M Scale with 500 Executions, BMC Helix Control-M Start Non-Production with 500 Executions and BMC Helix Control-M Production – additional tenant. No part numbers or prices are published for them.
Metrics
| BMC unit of measure | Catalog row | Where it applies |
|---|---|---|
| Per Task | per task | Self-hosted Control-M products and their add-ons[1] |
| Per Managed Asset – Control-M/Server Endpoint | per managed asset - Control-M server endpoint | Control-M/Enterprise Manager and priced add-ons[1] |
| Per MIPS | per MIPS | Mainframe Control-M products[1] |
| Per Execution - SaaS | per execution - SaaS | Control-M SaaS[1] |
| Per CPU, per named user | per CPU, per named user | Older or specific Control-M licences named in BMC’s usage-reporting instructions (“Tasks; Server Endpoint; CPU; MIPS; Users”)[4] |
BMC defines a Task as “interchangeable with ‘job’”. It is “an executable command containing the name of the JCL, CL, DCL, ECL, script or dummy processes that is scheduled to execute, as well as the scheduling criteria, flow control, and resource usage”.[1]
Counting / floors
Peak tasks in 24 hours (as retrieved 2026-09-27). For all Control-M Products except those that run only on the mainframe, a licence is required for the maximum number of Tasks in the Control-M Active Jobs databases in any 24-hour period, “regardless of whether the Tasks execute or not”.[2] The count spans all distributed and mainframe environments, “including but not limited to development, staging, QA, pre-production, production, and test environments”.[2] A non-production Control-M instance therefore adds to the licensed task count; it is not free. Control-M Products that run exclusively on the mainframe count only the mainframe environment’s Active Jobs database.[1] Catalog proof: Control-M tasks are counted at the 24-hour peak across all environments; Mainframe-only Control-M products count only the mainframe Active Jobs database.
What is not counted. The definition lists four exceptions:[2]
- SMART folders/tables and sub-folders/tables that contain scheduling definitions and appear as tasks in Active Jobs are not Tasks.
- A Task with time-zone settings may stay in Active Jobs for up to three consecutive days but counts once.
- A Task that runs more than once a day with the same Order ID counts once. This includes reruns and cyclic Tasks.
- Tasks covered by licences under another unit of measure, such as tier or MIPS, are not counted as Tasks.
The number of steps or scripts inside a Task does not affect the count.[2] Catalog proof: A rerun or cyclic Control-M task with the same Order ID counts once; SMART folders and time-zone tasks are not double counted.
Server endpoints. Under the server endpoint measure, a licence is required for the maximum aggregate number of Control-M Server Endpoints monitored or managed, directly or indirectly, in any 24-hour period. A Server Endpoint is any virtual or physical Computer, excluding OS/390 or zSeries mainframes, that provides a service to other networked Computers.[1]
Add-ons. Priced Control-M add-on Products need the same number of Server Endpoints as licensed for Control-M.[1] BMC’s usage-reporting instructions apply the same principle to all add-ons: they “use the same unit of measure as the base licensed product and must have a matching one-to-one license count with it”.[4] Catalog proof: Control-M add-ons follow the base Control-M licence count.
Executions (Control-M SaaS). For Control-M Subscription Services, a subscription is required for “the highest monthly average of jobs executed by the Control-M Subscription Services during a given quarter”. A job executed several times a day is counted at each execution. This is the reverse of the self-hosted rule, under which a cyclic Task with one Order ID counts once.[2] Executions bought with the Start or Scale packs may be used in an additional tenant, “provided that Customer does not exceed the Capacity of such executions purchased in all such environments”.[2] Catalog proof: Control-M SaaS is measured by the highest monthly average of executions in a quarter; Additional Control-M SaaS tenants share the purchased executions; The Control-M Starter Pack caps execution volume only.
User licences. BMC’s usage-reporting instructions name a Control-M/Full Admin User License. It is required when a user accesses the Control-M Workload Automation Client in version 8 and later, or the Enterprise Manager GUI in earlier versions. A Control-M/Web and Planning User license is required for Control-M/WebAccess or the planning functions. Control-M Output Management WebAccess is licensed per named user.[4]
Floors. No minimum task or execution quantity is published. The Starter Pack caps execution volume and no other capability.[3]
Virtualization & partitioning
Control-M’s task and execution measures do not depend on hardware, so virtualization does not change them. Under the server endpoint measure, a virtual Computer counts like a physical one.[1] CPU-licensed customers report physical CPU sockets per machine. “For virtual machines in your environment, please determine the number of physical CPU sockets associated with the physical host” of each machine.[4] Catalog proof: For Control-M CPU licences, VMs are counted by the physical host's sockets. The MIPS measure counts the aggregate MIPS of each Computer, including every Computer coupled in a parallel Sysplex, rated from the Gartner Group Rating Guide.[1] See BMC AMI mainframe licensing for mainframe measures.
Cloud / BYOL
Control-M SaaS is hosted by BMC. The Service Level Agreement commits to 99.95% monthly availability for Control-M SaaS Subscription Services and 99.9% for the Control-M Archive Service. The remedy is a Service Credit, requested within 30 days after the end of the month.[5] Catalog proof: Control-M SaaS carries a 99.95% monthly availability commitment. A self-hosted Control-M deployed on public-cloud infrastructure is counted by the task, endpoint or CPU measure on the Order. BMC publishes no separate cloud mapping for it. BMC’s pricing FAQ confirms that SaaS and on-premises deployments can be combined in hybrid architectures.[3]
Programs
- Subscription Services. Control-M SaaS Capacity is “counted in accordance with the Unit of Measure described in the Order”. BMC may monitor use and require an Order for additional Capacity.[6]
- On Premises Subscriptions. Self-hosted Control-M is a term licence up to the Licensed Capacity. It is subject to annual usage-report requests and audits.[6]
- Usage Reporting. Control-M is one of the four product lines named for BMC’s non-Enterprise usage-reporting program.[7] Customers install the Control-M Usage Reporting Tool from BMC’s download site and return the .csv files for all environments.[4]
Restrictions
Two product-specific restrictions in BMC’s documentation affect Control-M. CONTROL-M/Assist “may only be used to interface with the third party scheduler”. It may not schedule or manage batch processes outside the cross-scheduler dependencies.[2] The Control-M Self Service Mobile Integration Kit is a development tool, governed by the development licence agreement supplied with it.[2] Catalog proof: Control-M/Assist may only interface with a third-party scheduler.
Out of scope
This page does not cover Control-M managed file transfer and data-pipeline add-ons beyond the general add-on rule. It also does not cover marketplace-specific terms on AWS or Google Cloud, or professional conversion services. The retrieved documents do not give separate licence metrics for these.[3]