>Because sometimes the client says that they want to see n number of jobs in a >certain class running. >We know that it might not be the best thing, but the client is always right.
You need to convince them (if you can) that performance experts know better. Having more jobs in a class than the WLM has determined optimum: 1. Can lead to over-initiation. 2. Doesn't guarantee the class throughput will improve. 3. Can impact other classes, or workloads. As long as service levels are met, all else is secondary. PS: What happens if there aren't "N" jobs in the system? - Ted MacNEIL [email protected] Twitter: @TedMacNEIL ---------------------------------------------------------------------- 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
