① Explainer · IBM EWLC
Entry Workload License Charges are IBM's sub-capacity Monthly License Charge metric for smaller z/OS machines. You pay on the Rolling 4-Hour Average, not on full capacity, which on a small box means a single daily peak can drive every product on the system.
EWLC stands for Entry Workload License Charges, the entry tier of IBM's Workload License Charges (WLC) family. It is a Monthly License Charge (MLC) metric, so it bills recurringly every month rather than as a one time charge, and it is sub-capacity, so the charge tracks measured consumption rather than the full rated capacity of the machine. It applies to the smaller z/OS machines, historically the lower capacity business class models, where the larger Variable Workload License Charges (VWLC) tier did not fit.
The mechanic is the same one that governs the rest of the WLC family: each month the Sub-Capacity Reporting Tool (SCRT) measures the Rolling 4-Hour Average (R4HA) of utilization for each eligible product, and you are billed against that peak. A product peak can never exceed the z/OS peak. To stay eligible you must run in 64-bit z/Architecture mode and submit the monthly sub-capacity report to IBM.
On an entry machine the Rolling 4-Hour Average is volatile because the box is small: a single batch window, a heavy report run, or a month end cycle can lift the four hour average well above the daytime online baseline. The bill is set by the single highest R4HA point in the month. The table below shows how one overnight batch peak resets the billable MSU figure for a representative 50 MSU entry box.
| Window | Workload | R4HA MSU | Billable? |
|---|---|---|---|
| Daytime online | CICS and Db2 transactions | 28 | No |
| Evening reporting | Batch reports | 34 | No |
| Overnight batch | Month end posting | 47 | Yes, monthly peak |
| Weekend idle | Maintenance only | 9 | No |
| Billed R4HA | Highest point | 47 | Sets all products |
The estate runs near 28 MSU most of the day, yet the bill is struck at 47 MSU because of one overnight batch peak, and that 47 MSU figure caps the billable peak for every sub-capacity product on the machine. On a small box the gap between the daily baseline and the single monthly peak is the whole game. Figures illustrate the mechanic, not any published rate.
| Metric | Tier | Capacity basis | Typical fit |
|---|---|---|---|
| EWLC | Entry, legacy | Sub-capacity, R4HA | Older smaller z/OS machines |
| AEWLC | Entry, advanced | Sub-capacity, R4HA | Newer entry machines |
| VWLC | Variable, legacy | Sub-capacity, R4HA | Larger machines, pre z196 |
| AWLC | Variable, advanced | Sub-capacity, R4HA | Larger machines, z196 onward |
| PSLC | Parallel Sysplex | Full capacity | Aggregated sysplex estates |
AEWLC is the advanced successor to EWLC, the entry counterpart to the VWLC to AWLC move on larger machines. The advanced metrics carry the technology dividend of the newer hardware, so the per MSU schedule differs even though the sub-capacity mechanic is identical. The common buyer mistake is staying on a legacy entry metric after a hardware refresh that entitles you to the advanced schedule.
The pressure point on entry machines is the sensitivity of the R4HA. Because the box is small, the distance between the online baseline and the single monthly peak is proportionally large, and one mistimed workload can lift the bill for every product. That same sensitivity is the opportunity: small, deliberate moves to the peak produce outsized savings.
Buyer side levers
On an entry box, the peak is the bill.
Related explainers: the MIPS to MSU conversion question, batch window tuning to cut R4HA peaks, sysplex vs standalone pricing differences, and the IPLA one time charge model for the tools that sit beside your MLC stack. Long tail product: CICS Transaction Server licensing. Hub and commercial: the IBM buyer side guide and IBM renewal advisory.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.