>I have to agree, an unattainable goal is an invalid goal. >If you're getting a PI of 1.4 to 2 (or higher) that likely means that the work that is running in that particular service class is actually getting a >velocity of 64 (at best ~ 1.4 PI) down to 45 or worse (at >= 2 PI).
>We don't have any velocities over 50 for anything, no matter how important. Most of them are around 30 for started tasks. If it's so important that it >needs the highest priority, it goes to SYSSTC. I think it should be noted that a goal that is too low is equally invalid. Goals should be set according to what a workload needs to meet its real world objectives and not according to what one "hopes" to get. Unattainable goals simply result in the workload being largely ignored by WLM, while goals that are too easily achieved will result in resources being taken away when other service classes need more. The latter case can be easily overlooked when there is no constraint. Adam ---------------------------------------------------------------------- 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
