Seven Mistakes to Avoid in IBM Mainframe  

In the fifth blog of this series we look at the mistakes that can be avoided by performing frequent checks such as: Not meeting criteria for Sysplex and not performing cleaning.

In the fourth blog of this series, we learned about different reports that can be leveraged to check for compliance of mainframe products. 

In this fifth blog of this series, we look at the mistakes that can be avoided by performing frequent checks as listed below: 

  1. Not utilizing sub-capacity benefit 
  1. z/OS features showing up as enabled, which are not in use 
  1. MLC and IPLA variants of the same product being reported in the SCRT 
  1. Installing the products that are not listed in the zNALC certification form 
  1. Not meeting criteria for Sysplex 
  1. Bundling check when upgrading to a higher version of the product 
  1. Not performing cleaning. 

Not utilizing sub-capacity benefit

We’ve seen cases where the client is on full capacity where the measurement involves a set monthly fee determined by the MSU rating of the physical mainframe. This pricing remains constant, irrespective of actual usage. However, if the client moves to sub-capacity, the measurement is based on the peak usage recorded during the month as per the SCRT report rather than the mainframe’s physical capacity, which will reduce the software costs. 

Benefits of sub-capacity 

z/OS features showing up as enabled, which are not in use 

z/OS is made up of essential components and optional features. The essential components or base elements provide key operating system functions. When you purchase z/OS, you receive all of these essential components. The optional features enhance the operating system and can be ordered alongside z/OS. Optional features can be classified as either unpriced or priced. You can refer to the link for both base elements and optional features. 

Unpriced z/OS features 

Unpriced features are included only if requested during your order. Suppose you intend to utilize any unpriced features. In that case, including them with your base components at your initial order is advisable rather than waiting for a subsequent release. Once the base components from a release are no longer available for order, the associated unpriced features will also become unavailable. To simplify the ordering process, consolidation over time has minimized the number of unpriced features. Currently, there are two unpriced features: Communications Server Security Level 3 and z/OS Security Level 3. 

Priced z/OS features 

Priced features are always included with your shipment. When IBM processes your order, they enable the priced features you’ve selected. These features will be ready for use after you install and customize z/OS. Any priced features not ordered will be disabled, meaning they cannot be used even though they are installed on your system. If you decide to activate them later, you can dynamically update the parmlib member IFAPRDxx and inform your IBM representative. 

We have seen cases where the client has used the product in the past, and hence, the z/OS feature is enabled. Later, when the product is not being used, it is still reported as enabled in the IBM mainframe reports, which will cause compliance issues. So, one should make sure to disable a feature if they decide to discontinue using the product to stay compliant. 

MLC and IPLA variants of the same product being reported in the SCRT 

When a client migrates from a product’s MLC variant to the product’s IPLA Value Unit Edition variant, both products get reported in the SCRT report. However, after migration, both products are reported in some cases, which raises compliance issues. Hence, after the migration, one must ensure that only the IPLA Value Unit Edition variant is reported in the SCRT report. 

For example, if the client was using the MLC variant, Db2, for z/OS and has decided to migrate to the IPLA variant, DB2, for z/OS Value Unit Edition. Then, during the migration period, if both the MLC and IPLA variants are reported, no compliance issues will be caused. You can inform IBM of this, and you should be good. However, once the migration is done, one must ensure that only the IPLA Value Unit Edition is reported in the SCRT report. 

Installing the products which are not listed in the zNALC certification form 

IBM offers a pricing option for LPARs that run z/OS at a lower cost if certain ‘qualified applications’ are being run. This pricing option is zNALC and applies to the z/OS base and its features. For z/OS to qualify for zNALC pricing, it must be running on an LPAR dedicated to running a ‘qualified application,’ the only other products allowed on this LPAR are those supporting the ‘qualified application.’ The LPAR should be used only for the ‘qualified application’ and its supporting programs and nothing else. IBM will decide if a specific program meets the criteria for being a qualified application. Some examples of qualified applications are DB2 for z/OS in support of PeopleSoft from Oracle and DB2 for z/OS in support of Siebel from Oracle. 

The machine name, LPAR of that machine name, zNALC LPAR, and qualified applications that can be run on the zNALC LPARs are listed in the zNALC certification form signed between the client and IBM. Suppose the client runs applications other than those listed as qualified applications as per the zNALC certification form on the zNALC LPARs. In that case, the client will be non-compliant, and the z/OS base and features charges will not be discounted. Hence, keeping track of zNALC LPARs and the applications running on them is always a good practice to get the z/OS base and its features at a lower price. 

Not meeting criteria for Sysplex

Sysplex is a technique for consolidating several physical mainframe machines into a single larger system, which helps reduce the price per Value Unit. To qualify for the sysplex benefit, specific criteria must be met. Machines must satisfy the requirements in four key categories: hardware, software, operation, and verification. Machines that fulfill all these criteria are designated as ‘actively coupled.’ 

Hardware Criteria

You must have at least two eligible mainframes physically connected through coupling links to a shared Coupling Facility. 

Software Criteria

At least one common system enablement function must be there on each LPAR in the sysplex and should be activated to utilize the coupling facility. 

Operation Criteria

To qualify, the LPARs in the sysplex and running the appropriate systems enablement function must represent at least 50% of the total workload on each mainframe machine within the Parallel Sysplex. Each mainframe can only be part of one Parallel Sysplex for aggregation. 

Verification Criteria

You must inform IBM when establishing a new Parallel Sysplex that qualifies for aggregated pricing. If all terms and conditions are satisfied, the aggregated Parallel Sysplex pricing will be applied upon receiving the notification. 

Similarly, if you add an additional mainframe machine to an existing qualified Parallel Sysplex, you must inform IBM. Aggregated Parallel Sysplex pricing will be applied if all terms and conditions are met upon receipt of this notification. 

If you do not meet the criteria for “actively coupled” machines, you will not be eligible for the benefits of Parallel Sysplex pricing. 

To summarize parallel sysplex in layperson’s terms concerning compliance, if you have two machines, 1 and 2, let us assume a product is seen as used on both machines. In a typical scenario, the entitlements of the product on machine one would be compared to the product on machine 2, and the product on machine 2 would be compared to the product on machine 2. If these two machines are in sysplex, then the combined entitlements of the product on machines 1 and 2 would be compared to the combined usage of machines 1 and 2. Hence, the workload is distributed across this logical sysplex machine to take advantage of reduced workload pricing, and as the size of the machine grows, the price per MSU reduces. 

If you fail to meet any of the above criteria, you will not receive Sysplex benefits, i.e., the machines listed under Sysplex will not be considered. 

Bundling check when upgrading to a higher version of a product 

Certain products come bundled with the main product, typically at no additional cost. The number of licenses needed for the main product may match the number required for each supporting program or a specific ratio may be outlined in the License Information document. However, please note that bundling can be version-specific in some cases.  

For instance, let’s say ProductA v1 bundles ProductB v2, which means that ProductB v1 and v2 are bundled with ProductA v1. However, for the same ProductA but v2 bundles, only ProductB v1 is available. If you upgrade from Product A v1 to v2, you will not get Product B v2 at no cost. Hence, it is important to check for bundling when upgrading to a higher product version to keep compliance in check. 

Not performing cleaning 

You should understand that IBM licensing is as per installation and not usage. That means if you are not using a product, but it is installed in your environment, you should have enough licenses for that product to stay compliant. 

That is why if you have used a product in the past and decided to discontinue using the product now, you should clean all the instances of the product from your environment. Otherwise, the product will appear in the mainframe installation reports and cause compliance issues.  

Still have questions or need further assistance? Don’t hesitate to reach out to our team of experts. We’re here to help you navigate the IBM Mainframe licensing world and unlock this powerful solution’s full potential. 

FAQs 

What is the difference between full-capacity-based licensing and sub-capacity-based licensing?

Under full-capacity-based licensing, IBM bills the products on the machine’s rated capacity. Under sub-capacity-based licensing, IBM bills the products based on the peak Rolling 4-Hour Average MSUs reported as in use as per the SCRT report for a month. 

Are all the IBM mainframe products eligible for sub-capacity?

There are a few metrics under MLC are available only at full capacity. For example, Parallel Sysplex License Charges (PSLC) and z Entry License Charges (zELC). Flat Workload License Charge products have a monthly fee independent of the machine’s capacity; hence, they are not eligible for sub-capacity. There are a few IPLA products whose sub-capacity eligibility is listed as ‘Not Eligible’ by IBM. These products can only be charged at full capacity.

What will happen if I am not using a z/OS feature but it is reported as enabled in the IBM mainframe report?

Even though you are not using the feature, since it is enabled, this feature will be counted towards deployment, which might result in non-compliance. 

Why do MLC and IPLA Value Unit Edition variants of the same product sometimes get reported in the SCRT report?

This happens when a migration from the MLC variant to the IPLA Value Unit Edition variant occurs.

What is z New Application License Charges (zNALC)?

z New Application License Charges (zNALC) is a reduced pricing option for the z/OS base product and its priced feature. To be eligible for this zNALC benefit, specific criteria should be met. One of the main conditions is that the LPARs that are zNALC LPARS should run only qualified applications. 

What happens if I don’t qualify for the z New Application License Charges (zNALC) benefit?

If you fail to meet the terms and conditions set for zNALC, you will be charged a regular price for the z/OS base and its features. You will not get a discount for the z/OS base and its features. 

What will happen if I don’t check for bundling while migrating to a higher product version?

You might pay for an extra product bundled with a lower version of the main product but not a higher version

Further Reading

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

ILMT Upgrade

LicenseHawk’s ILMT Upgrade Success in Banking

Discover how a top financial institution partnered with LicenseHawk to mitigate IBM license compliance risks, modernize ILMT and BigFix, and achieve major cost savings and SAM improvements.

IBM mainframe licensing basics guide cover image

An Introduction to IBM Mainframe Licensing

IBM mainframe licensing is its own world. This introduction covers the terminology, processor types, operating systems, MSUs and MIPS, and the contracts (CRA, ICA, IPLA) that govern how IBM mainframe products are licensed and priced.

License Tip: Beware the IBM license stealth audit