Before I'd hardcap, I'd make sure the WLM Service Policy is setup according to the Business needs. I'd consider Resource Groups before capping.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tommy Tsui Sent: Tuesday, September 09, 2008 SYSN 06:10 PM To: [email protected] Subject: Re: Capping LPARs You can use Hard capping - Pros - all weighting/resource for each LPAR is fixed, easy for collect statistic/charging for each LPAR Cons - each LPAR cannot use more weighting at the peak hour (like soft capping) until you reset the all the weighting again On Wed, Sep 10, 2008 at 6:25 AM, gsg <[EMAIL PROTECTED]> wrote: > We process for two banks and they each have their own Production and Test > LPARs. We have a window that we would like to finish processing in, but > periodically miss the goal by a few minutes. Management is pressing for a > reason why we are missing it. There are sooooo many variables to determine > this, so I'm suggesting that we cap our systems to hopefully create a more > consistent environment. What are the Pros/Cons of capping the LPARs? > > TIA > > ---------------------------------------------------------------------- > 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 > > ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
