Thomas H Puddicombe wrote:
One way would be to define a third LPAR. Assign a weight to the new LPAR equivalent to 4/32 of the total of all the LPAR weights. Cap this new LPAR. Put a looping task into this LPAR. PR/SM will then ensure that no more and no less than 4/32 of the total CPU is wasted running a silly loop. Whatever's not used by the loop is available to the other LPARs. Warn capacity planners and resource billing people that there's a "soaker" workload.
I don't get it! Is this "soaker" some sort of stand-alone IPLable program you've written? Or do you need to IPL z/OS to run it? If the latter case, how does it keep your z/OS VWLC peak from reaching 32 MSU? Is there some sort of VWLC exemption for running a z/OS "soaker"? Does IBM allow you to exclude that LPAR's SMF records from your SCRT input?
-- 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
