IBM Mainframe MLC and IPLA (OTC + ASC) Entitlements

This blog discusses IBM Mainframe MLC, IPLA entitlements, zNALC, and Parallel Sysplex, as well as a series of frequently asked questions.

IBM Mainframe MLC and IPLA

IBM charges for mainframe software in two ways, and which one applies to a product determines how you’re billed, how your usage is measured, and how much room you have to reduce costs. IBM mainframe MLC and IPLA entitlements operate under different rules and use different identifiers, so a cost-reduction plan built around one won’t work for the other. Organizations that haven’t separated the two often find out which is which during a compliance review. The sections below cover how each model is charged, the metrics available under MLC, the reduced price options on z/OS, what Parallel Sysplex aggregation requires, how IPLA products convert from MSUs to Value Units, and the entitlement errors that persist for years without anyone querying them.

How IBM Mainframe MLC and IPLA Entitlements Differ

Mainframe products fall into one of two groups. Monthly License Charge products are billed every month, with IBM support and maintenance included in the charge. International Program License Agreement products are bought once through a One-Time Charge, with an Annual Support and Subscription Charge paid separately for updates and support.

The two models also respond differently when your usage moves. Under MLC metrics that support sub-capacity pricing, charges follow measured capacity, so reducing peak usage lowers the bill. That measurement comes from the Sub-Capacity Reporting Tool, which calculates your usage and submits it to IBM monthly, so the accuracy of your SCRT output decides what you’re billed.

Some MLC metrics are full capacity only, including Parallel Sysplex License Charges and z Entry License Charges, and reducing usage on those changes nothing. With an IPLA product you already own a perpetual license, so the annual support charge is where a reduction has to come from.

How IBM Mainframe MLC Products Are Charged

MLC products are available under several metrics, and the metric determines both the price and whether sub-capacity pricing is available to you. Learn the significant ones by name, because IBM won’t always explain which applies to your machine.

Advanced Entry Workload License Charge applies to smaller hardware, while Advanced Workload License Charge covers more substantial systems, typically those running z/OS or z/TPF. New Application License Charge applies to environments running qualified applications, and the reduced pricing option available on z/OS base is covered below.

Tiered Workload License Charge applies a flat rate based on server capacity using a tiered structure, and Flat Workload License Charge applies a single fee per product per eligible machine regardless of the machine’s capacity. Country Multiplex License Charge allows you to combine MSU requirements across eligible machines within a country, subject to IBM-set eligibility requirements.

Most MLC products are measured in MSUs, with a few exceptions including Flat Workload License Charge. If you’re modeling a reduction in peak capacity and one of your larger products is on a flat metric, the savings you projected won’t materialize, so confirm the metric for each product before you build the case.

For ways to bring monthly MLC charges down, see our tips for managing and minimizing IBM MLC monthly run rates.

Product IDs and versions

Each MLC product carries a unique product ID in the format xxxx-xxx. Different versions of the same product have different product IDs, whereas a base product and its priced features share the same product ID. As an example, 5650-ZOS is the product ID for z/OS V2 base and also covers features such as z/OS DFSORT V2, z/OS HCM V2, z/OS Bulk Data Transfer SNA NJE V2, and z/OS High Level Assembler Toolkit V2.

MLC products don’t have a separate support ID, because support is included in the monthly charge. When you’re reconciling an entitlement list, a mainframe product with no support ID is almost certainly MLC, which is a quick way to split an entitlement list into the two models.

Reducing z/OS Cost with zNALC

The z/OS base operating system falls under MLC pricing, and IBM offers it at regular price plus two lower priced options. Those are zNALC (z New Application License Charge) and z Solution Edition. Both carry their own eligibility conditions, and zNALC is the one covered below.

zNALC applies to the z/OS base and its features where the LPAR is dedicated to running a qualified application. The LPAR must run only the qualified application and the products that support it, with nothing else on it. IBM decides what counts as a qualified application, and published examples include Db2 for z/OS supporting PeopleSoft from Oracle and Db2 for z/OS supporting Siebel from Oracle.

If your application isn’t on the qualified list, you can submit additional information for assessment, and IBM will confirm the outcome and the resulting z/OS pricing. zNALC itself is available in two forms, and which one applies determines whether a capacity reduction helps. Full Capacity zNALC charges on the total capacity of the machine the zNALC product runs on, while Sub-Capacity zNALC charges on the usage of the specific LPAR or LPARs where it runs.

Failing any of the zNALC conditions means paying the regular price for z/OS base and its priced features. Workload can drift onto a zNALC LPAR over time without anyone treating it as a licensing decision, and the reduced pricing is lost without anyone having chosen to give it up. A scheduled review of the qualification catches that before a bill does.

Parallel Sysplex Aggregation and What Qualifying Takes

Parallel Sysplex consolidates several physical mainframes into a single, larger system for pricing purposes, thereby reducing the price per Value Unit. Aggregation and sub-capacity pricing are easy to conflate, but they do different things. Aggregation combines the capacity of multiple machines to achieve a better unit price, while sub-capacity measures how much of a single machine a product uses, which is why a full-capacity metric can still benefit from aggregation. Four sets of criteria must be satisfied before aggregated pricing applies: hardware, software, operation, and verification. Machines that meet all four are designated as actively coupled.

Hardware criteria

You need at least two eligible mainframes physically connected through coupling links to a shared Coupling Facility. Where a Coupling Facility is partitioned into multiple LPARs, every mainframe has to be connected to the same Coupling Facility LPAR.

Software criteria

All LPARs in the Parallel Sysplex have to run an eligible operating system. Each LPAR in the sysplex also needs at least one common system enablement function present and activated to use the coupling facility. Eligible functions include WebSphere MQ shared message queues, HSM common recall queues, enhanced catalog sharing, GRS Star implementation, JES2 checkpoint in the coupling facility, RACF database caching, SmartBatch multisystem processing, VTAM Generic Resources, VTAM MULTINODE persistent sessions, and the system logger for SYSLOG, LOGREC and Resource Recovery Services.

Operation criteria

The LPARs in the sysplex that run the appropriate system enablement function must represent at least 50% of the total workload on each mainframe in the Parallel Sysplex. Each machine can only be part of one Parallel Sysplex for aggregation purposes. Internal Coupling Facility engines and Integrated Facility for Linux engines are excluded from the calculation, since neither runs z/OS.

Verification criteria

You have to tell IBM when you establish a new Parallel Sysplex that qualifies for aggregated pricing. IBM’s own documentation states that aggregated pricing is applied upon receipt of that notification once the terms and conditions are satisfied. The same requirement applies when you add a machine to an existing qualified sysplex.

Because the wording ties the benefit to the date of notification, an addition you never told IBM about has most likely been priced without aggregation ever since. Verify that against your own contract terms rather than taking it as read, because IBM won’t raise it unprompted. If you fall out of the criteria altogether, each machine reverts to standalone treatment, with entitlements and usage assessed separately.

Aggregation interacts with metric selection and machine configuration, which is why we look at all three together in our IBM mainframe negotiation work.

How IPLA Products Are Licensed

An IPLA product carries two product IDs, one for the license and one for support, both in the xxxx-xxx format. Different versions of the same product have different license IDs but share a support ID, so a common support ID tells you two entries on an entitlement list belong to the same product family, whether as different versions or as features of the same base product. A base product and its features share the same IDs. As an example, 5741-A09 is the product ID for z/VM V7 and covers features including Performance Toolkit for z/VM V7 and RACF Security Server for z/VM V7, with 5741-SNS as the support ID across all versions.

IPLA support runs on an all-or-nothing basis. Every product license is maintained under support, or none of them are, which is similar to how support works on the distributed side of IBM’s portfolio. Dropping support on the licenses you no longer use while keeping it on the rest isn’t an option, so any reduction has to be decided at the product level. That makes it worth modeling before a renewal, since the decision covers every license for the product rather than a single line.

Converting MSUs to Value Units

IPLA products are measured in Value Units, while machine capacity is measured in MSUs. Checking compliance therefore means converting one to the other, and IBM publishes Value Unit Exhibits for the purpose, identified by a three-digit number in the form VUExxx.

Conversions from MSUs to Value Units use exhibits 001, 007 and 020. Other metrics, such as simultaneous instances or users converting, are shown in exhibits 002, 021, 023, 027, 028, 030, 031, 033, 034, 035, 036, 037, 038, 039 and 040. The exhibit applicable to a given product is listed in its License Information document, which you can search by product ID.

Using the wrong exhibit misstates your position, and the error costs you whichever way it runs. Understating your entitlement leaves you exposed to paying for it at a review. Overstating it means you bought Value Units you didn’t need, and IBM has no reason to raise it with you.

Where Mainframe Entitlement Errors Cost Money

Four patterns recur in the mainframe estates we review. An invoice won’t flag any of them, because in each case you’re being charged correctly for the position you’re in.

The first is a capacity-reduction program that includes products on flat metrics, where the projected savings never materialize because the charge doesn’t move with capacity. The second is a zNALC LPAR that has acquired additional workload over time and lost its reduced pricing as a result.

The third is a machine added to a sysplex about which IBM was never notified, which continues at unaggregated prices. The fourth is IPLA support renewing on licenses that stopped being deployed years ago, where the all-or-nothing rule makes the decision look like it isn’t one.

Finding any of them means reconciling your entitlements against your current configuration instead of against last year’s invoice, which is the basis of our mainframe contract advisory work.

Useful Mainframe References

Conclusion

The cost levers available under MLC and IPLA are different enough that a single plan covering both will misfire on one of them. Establishing which model applies to each product, and which metric applies within it, is what tells you whether a reduction is available before you spend time modeling one.

Most of the money on a mainframe estate goes missing in the same few places, and none of them announces itself. Reduced pricing options lapse, sysplex additions go unnotified, and support keeps renewing on products nobody runs. Checking those against your current configuration is work you can start without waiting for a renewal or a review to force it.

FAQs

What’s the difference between MLC and IPLA mainframe licensing?

MLC products are billed monthly with IBM support included in the charge, and usage is generally measured in MSUs. IPLA products are bought once through a One Time Charge, giving you a perpetual license, with an Annual Support and Subscription Charge paid separately. MLC typically applies to core z/OS software, while IPLA covers a wider range of mainframe and distributed products.

Do Monthly License Charge products have an S&S ID?

No. MLC products carry a license ID only, because the monthly charge already covers support and maintenance. IPLA products carry two, one for the license and one for support, so the presence of a support ID is a reliable way to tell the two models apart.

Are all Monthly License Charge products sold on MSUs?

Most are, including Advanced Entry Workload License Charge, Advanced Workload License Charge and Country Multiplex License Charge. Flat Workload License Charge isn’t, which is worth checking before you model any savings based on reducing capacity.

What is z New Application License Charges (zNALC)?

zNALC is a reduced pricing option for the z/OS base product and its priced features. Qualifying requires the LPAR to run only a qualified application and its supporting products, with IBM determining what counts as qualified.

What happens if you don’t qualify for zNALC?

You pay regular price for z/OS base and its priced features. Because workload can drift onto an LPAR over time, the qualification is worth rechecking periodically rather than assuming it still holds.

What happens if you don’t meet the Parallel Sysplex criteria?

Failing any one of the hardware, software, operation or verification conditions means aggregated pricing doesn’t apply. Your capacity is then priced machine by machine rather than across the sysplex, which removes the unit-price benefit that aggregation provided.

How do you find the VUE level of an IPLA product?

Search IBM’s License Information documents using the product ID in the xxxx-xxx format. Each document identifies the applicable exhibit and sets out the conversion for that product, so the VUE level is per product rather than something you can assume across a portfolio

About author
Shriya Reddy
Shriya Reddy
IBM License Expert
Shriya's expertise lies in Software License Compliance and Asset Management, specifically the licensing of vendors IBM (distributed and mainframe), Red Hat and Broadcom (mainframe). She has conducted audits on behalf of the vendors and helped them with significant revenue recovery, and has helped clients in license management, regular audits, cost optimisation, risk management and process improvements.

Read Next

Extra CBUs Are a Mainframe Negotiation Lever IBM Doesn’t Mention

LicenseHawk IBM audit defense case study showing a protective shield over the London city skyline with text reading $840,000+ compliance risk cleared with zero settlement.

IBM Audit Defense: $840,000+ Compliance Risk Cleared with Zero Settlement

Facing an IBM audit with six-figure liabilities, a global enterprise software provider turned to LicenseHawk. Through strategic scope negotiation and a tool-driven compliance defense, we completely eliminated a looming $840,000+ group risk. The result? IBM confirmed zero findings and formally closed the audit with zero financial settlement. Read the full case study.

IBM License Audit – Initial Response

IBM License Audit – Initial Response

This blog looks at the stages of an IBM License Audit, the activities involved, and common mistakes made. See the stages here.