Tag Archives: CICS
In our last post, we reviewed the Automated Capacity Management (ACM) feature of ThruPut Manager and its ability to control the rolling 4-hour average (R4HA) by constraining or deferring specified workloads as the R4HA approaches the soft cap limit. But you may prefer more granular control in order to more fully leverage the opportunity for MLC savings, or you may not prefer to put caps in place at all, but still wish to reduce demand and enjoy the resulting cost savings.
You know you need to reduce software costs wherever possible. Fine tuning of your batch can do this for you. IBM may recommend using a single LPAR group (Group Capacity soft cap limit) for all LPARS on a CPC; but, this implementation might not work for you on every CPC. You might have LPARs with products or applications that differ a great deal in CPU hourly usage rates from other LPARs. What you really want is to have all the control possible to ensure you strike the right balance between cost savings and performance. A brand new feature of ThruPut Manager can help.
Since the days when processor time was costly (and you input a job on punch cards), the CPU Busy metric has had intense focus. There are so many ways to look at the metric, all having vastly different meanings. Virtualization made it even more complicated. But for many in our field, this is still a very critical number. But is it the most important number?
For those exploiting the benefits of sub-capacity pricing to reduce IBM software costs, the Rolling 4-Hour Average (R4HA) is a critical measure to watch—but are you watching it effectively? If you’re like many systems programmers and capacity managers, you’ve probably created a specific job to keep your company’s R4HA in check.
This job likely focuses on key online workloads—those that impact the costs of CICS, IMS, DB2 and other licenses—and monitor changes to transaction mixes, new workloads and code, which can all cause your average to creep up, leading to increased software charges. Despite this effort, however, you may continue to see your R4HA rise, because you’re missing one sneaky cost contributor: batch.
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.
Just as IBM helped customers with CPU costs by offering zIIP engines, it’s again stepping up to the plate to make the cost of mobile applications more affordable. The company’s new program, highlighted in a previous post, is designed for z/OS customers running such programs as CICS, IMS and DB2 with IBM’s new Mobile Workload Pricing program (MWP). The new program allows those implementing sub-capacity AWLC, AEWLC or zNALC to run a new tool, the Mobile Workload Reporting Tool (MWRT), which acts like SCRT but for mobile workloads.