Ten Ways to Reduce Your Mainframe Software Licensing Costs
What is the biggest cost you have as a Mainframe manager? Software License Fees: The regular costs required to run the software and to obtain support in the event of an outage. This article provides ten ways to reduce these costs down to earth.
Check that you really need it.
Do not laugh. It sounds obvious, but it’s all too easy for software that you no longer have to go through the cracks. For example, you may have software that was originally required for CICS applications that have since been moved elsewhere.
You may also have licensed software for all z / OS images, but used on only one.
Check if you really use it.
As the mainframe workload changes over time, it is all too easy for the use of a software product to quietly decline without mainframe managers noticing. You could be paying thousands of dollars for a product that only a couple of people are actually using.
You should regularly review your software usage and plan to remove any software you no longer need.
Check that you don’t have two products that do the same thing.
You can use all of your software, but you have two software products that perform the same or a similar function. You need to fully understand your software inventory and exactly how each product is used.
Investigate the prices of secondary capacities.
Most software licensing costs are based on the size of each LPAR running that software – the MSU classification. You can find this value from the IBM website or from a program to call IBM’s IWMQVS service.
A few years ago IBM introduced another option: Sub-Capacity Pricing. This is where software licensing costs are based on CPU usage, not LPAR size. So software running on a less used LPAR will be cheaper. It also makes upgrades easier to justify as you don’t get hit by higher software costs with the larger processor.
IBM is not the only vendor offering partial capacity pricing. Other suppliers such as BMC and CA are also jumping on the bandwagon.
Reorganize your LPARs.
Many sites now run at least one “limited” LPAR, which means that available CPU resources are artificially limited using Workload Manager (WLM). Software charged under the MSU rating runs in this limited LPAR, reducing costs. อัตราต่อรองบอล
Partial capacity pricing users may consider doing the opposite: consolidate LPARs. This reduces CPU consumption by reducing the overhead of running a z / OS image.
Look into similar products.
Compare the price of competing products and consider switching to cheaper products. For example, SAS users may consider World Programming’s SAS WPS replacement product.
It is true that switching to different products can be very difficult and expensive in some cases. This is not necessarily the case, however, and many vendors offer migration tools to alleviate this problem.
Optimize your systems.
Optimizing systems reduces CPU usage (useful for low-capacity users) and delays upgrades to larger processors.
Step away from the mainframe.
Mainframe CPU resources are expensive compared to other platforms. So it might be worth considering migrating some of the workload. For example:
Software products such as Tachyon Assembler Workbench and Microfocus Mainframe Express allow you to perform Mainframe software development on Windows and UNIX platforms.
Some products such as Websphere Enterprise Service Bus and the CICS Transaction Gateway daemon run on both z / OS and other platforms.
Some workloads can easily be moved to other platforms. SOA and related services now make it easier to access mainframe data and services from other platforms.