Thanks a lot for everyone and appreciate your time and help, I will consider the recommendations given as i move on, Thanks again!
On Thu, Nov 8, 2012 at 11:00 AM, nitz-...@gmx.net <nitz-...@gmx.net> wrote: > > Not sure how Workload Manager is being used or configured at your shop. > > From the original description, I am assuming that that installation runs > more than one lpar on the box, most probably with lpar weights that reflect > importance of the lpars. If the OP happens to work on an lpar that is not a > loved one in terms of lpar weight, then almost no amount of WLM tuning will > get that lpar service if another lpar is using that service. What's more, > an execution velocity goal that is achievable on a loved lpar won't be on > an unloved one for the exact same job with the exact same data. > > If the *box* (all physical cps) is running at 100% cpu (as they are in > many smaller shops), then you need to drastically reduce the number of WLM > service classes/service class periods, at least in the unloved lpars. Get > down to less than 10 service classes, preferably only one per importance. > Be prepared to have a fight with just about everyone because they all think > they're more important than the rest of the world and they all want to be > at least importance1, better in sysstc. Traditionally, everything will > cluster in sysstc and importance 1 service classes, with almost nothing in > importance 4 and 5. > > Barbara Nitz > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
