Piffle for the first job perhaps but not when the latent demand reaches 20 or more as anyone who has watched the Workflow% drop to 0% for batch workload will attest.
As to your last comment, I agree. If management won't let you manage the workloads let the jobs finish when they will as oppossed to wasting cpu on cancelled jobs which will only be re-submitted. ----Original Message----- PIFFLE! NOT enough to worry about. Show me the metrics. SRM/WLM will only adjust one service class per interval. If a higher importance class is in trouble, it will be 'fixed'. If the lower ones are being adjiusted, then: 1. They need it; everything is fine. 2. Somebody higher should have been adjusted. Solutions: 1. Is correct. No worries! 2. Is correct. Adjust the policy! Otherwise, let'm rot! Eventually, they'll get service. And, that's better than cancelling them so the user can re-(submit/logon). When in doubt. PANIC!! ---------------------------------------------------------------------- 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
