IPLA: pay once, then pay every year after.

IPLA stands for International Program License Agreement, IBM's one time charge framework for mainframe software. You pay an upfront One Time Charge (OTC) for a perpetual license, then an annual Subscription and Support (S&S) fee that funds updates and support. It is the counterpart to the Monthly License Charge (MLC) model, which bills the core operating environment recurringly each month.

Many tools and utilities are IPLA programs: OMEGAMON and other monitoring, the Db2, CICS, and IMS tool sets, and a wide range of utilities. The platform programs that anchor the estate, z/OS, CICS Transaction Server, Db2 for z/OS, IMS, and MQ, are typically MLC. Classification varies by program, so always confirm which model a given product sits under.

IPLA programs are not priced directly in MSUs. You convert your machine or sub-capacity MSU figure into Value Units (VUs) using the program's Value Unit Exhibit. The conversion is regressive: each higher band of MSUs converts at fewer Value Units per MSU, so the cost of incremental capacity falls as the estate grows. The table below shows the mechanic on a representative schedule and a 200 MSU sub-capacity position.

The same 200 MSU estate licensed at a flat 10 VU per MSU would convert to 2,000 VUs. The regressive schedule yields 877, less than half, which is the entire point: at scale, the per MSU cost of an IPLA program drops sharply. Exact band breakpoints and rates come from each program's published Value Unit Exhibit and differ by program; the figures above illustrate the mechanic, not any one product's schedule.

The trap in IPLA is treating the OTC as the cost. It is not. The OTC is sunk on the day you pay it; the money that compounds is the annual S&S, charged every year for as long as you hold the license, and commonly subject to uplift. Over a typical platform lifetime the S&S can far exceed the original charge. That is the stream to manage.