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: WLM

Overinitiation: When more isn’t better


Even knowledgeable performance experts make the mistake of throwing more resources at work. If 10 buffers are good, 15 would be even better, right? If we have more batch work, throw initiators at it; it will get things moving faster. But it turns out that overinitiation is very similar to putting up more toll collectors on a bridge. Immediately after the toll is paid, the lanes have to shrink to the number that fits on the bridge. If you have too many toll takers, the merge following the toll gets crazy, accidents can happen and no one is moving fast.

The Batch Service Metric: Creating SLAs that work

batch service metric

We systems programmers love metrics – and we have a lot of them. Leveraging its Batch Service Metric, ThruPut Manager can help you set and achieve SLAs that are achievable and desirable. Give it a try and see how better communication between IT and the business can lead to career opportunities and advancement.

Dataset contention – “No fighting, No biting”

Dataset contention - No Fighting, No biting

As children, many of us read the timeless classic, ‘No Fighting, No Biting,’ a tale of warring alligator siblings and how their mother sought to broker peace between them. There are parallels to the problems of dataset contention. It’s inevitable that batch jobs will fight over limited system resources. In a capacity-constrained system, this can really cause delays, if jobs must wait a long time for CPU, memory or I/O channels.

Less is more – Too much of a good thing

less is more

Once upon a time, we had the luxury of throwing resources at performance problems. But even back then, we knew that didn’t always work and that there were diminishing returns, especially for batch workloads. A perfect example is buffering. For OLTP work, you could throw a lot of buffers at it and generally see some benefit, though the gains tended to diminish. However, with batch, you not only found that at some point, you got no further benefit, but that having to scan all those buffers could slow the system down. Often, the ‘right’ number was a good deal lower than what you thought.

Optimizing batch workload with dynamic initiators

dynamic initiators

When you hear the term dynamic initiators, you probably think of an initiator that simply starts and stops automatically. The thing is, when these initiators become part of a complete automation solution for z/OS batch processing, like ThruPut Manager, they’re capable of much, much more. ThruPut Manager’s automation algorithms optimize resource utilization and throughput of the workload as a whole by deciding to add or remove initiators based on current system load and datacenter policies.

Pros and cons of manual capacity management

Strict caps, as we’ve mentioned in previous posts, can be harmful to application performance. On the flip side, raising a cap to meet the needs of workload conditions can increase the Rolling 4-Hour Average (R4HA) and, as a result, cancel out the benefits of soft capping. So what is an organization to do?

Well, believe it or not, it is possible to take advantage of the financial benefits of soft capping and meet the needs of your organization at the same time. One technique is to lower the multi-programming level (MPL) of a system by controlling the available batch initiators.