Reduce Peak 4HRA and Software MLC Costs

ThruPut Manager manages workload demand to reduce capacity utilization, based on the 4HRA, when sub-capacity pricing is used with or without capping. More »

Automate z/OS Batch

ThruPut Manager balances workload arrival, importance, and resource availability. More »

Make the most of scarce resources

Because money doesn’t grow on trees, let us lower your MSU consumption and MLC costs. More »

Make Way for Mobile

As mobile applications take up more CPU at unpredictable times, let ThruPut Manager take low importance batch out of the equation and make room for your high priority workload. More »

Country Multiplex Pricing is here

Use ThruPut Manager automation to lower your MSU baseline today and find software license savings, with or without capping, when you move to CMP. More »

Automate production control

Manage z/OS execution according to your CA 7 schedule and due-out times, ensuring automated on-time completion with minimal intervention that frees you for other valuable tasks. More »

Our Customers

ThruPut Manager installations range from individual corporate datacenters to global outsourcing providers in the major industry sectors, including banking, insurance, and government. More »


Tag Archives: 4HRA peak

Where’s my bottleneck now? Staying ahead of your 4HRA (webinar)


Following a hockey puck can be challenging. It moves really fast and it’s not always obvious what the next player is going to do. Wayne Gretzky famously said: “Skate to where the puck is going; not where it’s been”. The same analogy can be applied in most sports: football quarterbacks throw to where the receiver is going to be; not where they are. Your monthly 4-Hour Rolling Average (and resulting MLC) is also a moving target.

By now, many shops are using soft caps and/or taking advantage of special pricing offerings from IBM such as Mobile and zNALC. These are excellent ideas — but, as all performance and capacity professionals know, reducing one 4HRA bottleneck only creates another.

Roll along, safely

If you take advantage of IBM’s variable workload license charges (VWLC), you’re more than familiar with the challenges of keeping costs low. In all likelihood, due to the complexity of how the rolling-four-hour-average (R4HA) is calculated, you find out the good or bad news only after you get your bill. You probably have IMS, CICS, DB2 and more running in a variety of LPARs with demand fluctuating throughout the day. And even if you keep your eye on your monitors, looking at the online work may give you a false feeling of confidence about how well you’re managing.

Capacity planning: Are you proactive or reactive?

proactive capacity planning

When it was first introduced, IBM’s sub-capacity pricing was a boon for capacity planners from a financial standpoint—allowing them to be more proactive in their planning. In the pre-sub-capacity era, all upgrades had to be carefully managed because of the huge potential impact on software pricing. Now, you can right-size your hardware and worry less about software costs—until you hit a soft cap, that is.

Reduce MLC costs with or without capping

reduce mlc costs

When it comes to lowering your company’s Rolling 4-Hour Average (R4HA), is capping always your best option? As we’ve mentioned elsewhere, while sub-capacity pricing can immediately reduce software costs, most installations need a way to guarantee a limit to the monthly charges to experience substantial savings. IBM offers a number of ways to do this, but virtually all of them involve the notion of “capping”. Capping is incredibly beneficial in certain scenarios; but, it isn’t necessarily the best choice for every installation.

CPU vs. R4HA peaks

Is that ten-minute burst of CPU activity at market open driving up your software bill? What about that extremely busy hour yesterday afternoon? Well, it’s possible—but these instances also might not make an impact at all. As we’ve mentioned in various posts, software license fees under IBM’s sub-capacity pricing model are determined according to the Rolling 4-Hour Average (R4HA). Since the R4HA is literally an average over four hours, it takes a long time to rise and a long time to fall. Further, it may not recur at the same day or time every month.