Yes, WLM managed initiators can be your best friend. When the machine gets saturated, WLM will bring the work under control.
Also a good starting point would be to back off the goals for batch. It's better if the work is over-achieving rather than under-achieving. On Tue, 25 Mar 2008 10:38:59 -0500, Hoesly, Bret <[EMAIL PROTECTED]> wrote: >If the operators are opening the floodgates, have you considered using >WLM managed initiators? That will let WLM initiate only whatever it >believes it can handle. > >As for your TSO vs. Prod batch issue, how many TSO users are competing >with the batch, what are they doing that's running so long into period >2, and how important is what they are doing compared to the batch work? >The quick fix of moving TSO up to importance 3 is probably your best bet >as long as you don't have an excessively large number of TSO users >running long tasks simultaneously. > >Just my 2cents worth. > >Have a good day! >Bret > >Bret Hoesly >Senior Systems Administrator - Mainframe >Telephone & Data Systems, Inc. ---------------------------------------------------------------------- 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
