On Wed, 7 Jan 2015 13:14:00 -0600, Elardus Engelbrecht <elardus.engelbre...@sita.co.za> wrote:
>Or use WLM and change their job priority so they are in 'Siberia work >priority'. (absolute low priority, so low, it is freezing) Discretionary work that's running on a system with available capacity will run. And if in doing so, it's holding locks in DB2 or pushing useful data out of the buffer pools, that might be unfortunate. Or say it's running at 6am, it might drive up the R4H enough that the production LPAR hits it's defined or group capacity limit at 8am when it normally wouldn't. If you want to keep a workload from consuming anything (or nearly so) in such a situation you'll have to use a resource group in WLM. Note that running the work on another LPAR on the machine may also not keep it from impacting the R4H in an undesirable manner as well. But there you also have the option of setting a defined capacity on the non-production LPAR. And that LPAR can have both a defined capacity limit as well as be part of a capacity group for the entire CEC. Scott ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
