ThruPut Manager licensing: a batch tool that cuts MLC, priced on capacity.

ThruPut Manager is a rules based, policy driven batch automation product for the JES2 environment on z/OS, now carried in BMC's portfolio as BMC AMI Ops Automation for Batch ThruPut. It automates the heavy lifting of batch management: it balances workload through dynamic initiators, reorders and prioritizes the batch queue against defined service goals, reports on batch service levels, and constrains low priority batch so the rolling four hour average stays under the capping limit that drives IBM Monthly License Charges. In doing so it positions itself as much as a cost control tool as an operations tool, because shaving the peak four hour average directly reduces the MLC bill. The product came to BMC through the acquisition of Compuware, which had itself acquired it from MVS Solutions, so on older contracts it appears under several names across that ownership chain.

ThruPut Manager is licensed on mainframe capacity, measured in MSU or MIPS, scaled to the LPARs where it manages batch, rather than by job count, initiator count, or batch volume. It uses the Compuware License Management System, and a valid license together with LMS are required for the product to run, with a licensing check performed when the started task initializes and a further check carried out daily. As part of BMC's mainframe portfolio it can be taken under a traditional capacity license or under BMC's consumption oriented model depending on the agreement, and the basis remains the capacity of the systems it runs on. The notable tension a buyer should hold onto is that a tool whose central pitch is reducing capacity driven MLC cost is itself priced on capacity, so its own cost must be netted against the savings it delivers.

Directional and pattern level. Confirm the capacity metric, the LMS terms, and how ThruPut Manager sits within your BMC AMI Ops schedules before modeling a renewal.

The first driver is licensed capacity, the MSU or MIPS of the LPARs where ThruPut Manager runs, the headline on any capacity priced tool. The second is LPAR scope, because the product is sized to the systems it manages, and as batch spreads across production, development, test, and disaster recovery the capacity basis grows with it. The third is the portfolio framing, since ThruPut Manager is increasingly sold inside the wider BMC AMI Ops family, and a bundled deal can obscure what this one tool costs and whether its price is justified by the MLC it removes. The fourth is naming drift across the MVS Solutions, Compuware, and BMC ownership chain, which can blur what the current entitlement grants against older paperwork. The decisive number, though, is the net: the product cost set against the verified MLC savings, because a batch automation tool that does not clear its own license fee in reduced charges is not earning its place.

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

Because ThruPut Manager is a capacity priced tool whose whole pitch is cost reduction, the levers center on capacity, the savings case, and the bundle. The five that pay:

Batch automation and MLC peak control are contested, with native z/OS Workload Manager capabilities, IBM capping and defined capacity controls, and competing third party batch and capacity tools all able to address parts of what ThruPut Manager does. That makes a credible alternative real, though rarely a like for like swap, because the product blends queue management, service level automation, and MLC shaping in a way that no single native control fully replaces, and the rules and policies built up over years carry operational knowledge that has to be rebuilt elsewhere. The sharper lever here is not displacement but the savings case itself: because ThruPut Manager is sold on the MLC it removes, a buyer can hold the vendor to that arithmetic, demanding the product justify its own license fee in verified reductions. The practical approach is to validate the capacity, test the net savings, and negotiate the bundle first, keeping a costed move to native controls or a competitor as the leverage that disciplines the renewal.