Hello,
It's been a while since the workload capping group topic was last discussed on this list, but last year my interest was really piqued when I noticed the thread below. I have since spent some time searching for more information on the topic, and also to find out exactly how to configure and take advantage of workload capping groups.
I have found the concept of workload capping groups very useful, both in terms of ring fencing processor intensive workloads as well as also "capping" license fees. As for the latter it's worth noting that both IBM MQ (previously named Websphere MQ) and DB2 Web Query are examples of software products that allow you to scale down the number of processor cores assigned to the product's runtime - and thereby also reduce the associated license fees accordingly.
My research so far revealed that IBM actually made a decent effort to properly inform about and explain the workload capping group capabilities - introduced by PTF all the way back in release 6.1. Yet somehow this communication had flown under my radar, until I noticed the thread here on midrange.com. So in order to further help in getting the message out, and to fill in some gaps in the current CL command offering in this area, I thought I'd better share what I have come up with so far. For that purpose I've written a new APIs by Example article and included a few of the "missing" CL commands to make managing workload capping groups a little easier. You can find the article and links to the associated code here:
https://apimymymy.wordpress.com/2017/09/26/apis-by-example-workload-capping-groups-save-license-fees-and-manage-workload-capacity/
At the end of the article I've also included links to the articles, presentations and other relevant documentation that I have come across in the cause of my research.
Cheers,
Carsten
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mitchell, Dana
Sent: 21. juli 2016 15:35
To: Midrange Systems Technical Discussion
Subject: RE: Processor shifting due to Mimix
I don't think Workload capping will work for Mimix. We were using a Workload capping group to restrict our usage of iTERA to a subset of our Licensed i cores. This spring, we began a conversion to MIMIX, and immediately received a message telling us that 'Product 7VSI001 cannot be part of work load capping group xxxxx' I opened a problem with Vision solutions inquiring about it and their reply was to either purchase a license that covers all cores we are running or reduce the number of cores.
Dana
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bdietz400
Sent: Thursday, July 21, 2016 6:45 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Processor shifting due to Mimix
Rob, I'm looking at doing something with Workload Capping Groups. Essentially "restricting" the mimix product to use "x" number of processors on a particular LPAR. The way it stands now it(licensing) looks at all LPARs on a frame using the product. I'm not sure that it will work but am pursuing.
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzaks/rzaksworkloadcapping.htm
--
Bryan
midrange.com
