Errol Van staden wrote:
Hi Group! I need to implement GCL for two LPARS in a Sysplex on a single footprint z9.

The two LPARs are Production (P) and TEST (T). The P LPAR should always be able to use spare capacity from the T LPAR but not vice versa.

>From my research, I can achieve this by soft-capping the T LPAR at its normal MSU capcaity, let the P system run uncapped (soft) and cap the group at the total MSU rating.

Questions
1) Is my understanding correct?
I believe so.
2) Do I have to also active IRD in order for it to adjust the LPAR weights when P LPAR can get spare capacity?
I don't think so. AFAIK, so-called phantom weights are used to enforce the group capacity. So long as the group is not maxed out, capacity will be available for P.
3) Will WLM not steal capacity from P LPAR when T LPAR high importance workload is struggling to achieve its targets?
The relative weight of the LPARs decides the share each LPAR receives when the group is maxed. If you want the relative weights adjusted, I think you will need to activate WLM dynamic LPAR weight management.
4) Will the soft-capping of T LPAR prevent this when it is running at high usage?
If T exceeds its LPAR defined capacity, it will be hard-capped by WLM on and off until its R4HA comes back down. This happens independently of any LPAR capacity group. WLM on each image is in charge of capping itself.

Have you read these and other related sections in the WLM planning guide?
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2W190/3.8.2
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2W190/3.8.1

--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[email protected]
http://www.phoenixsoftware.com/

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to