> On Jul 21, 2016, at 12:25 PM, Elardus Engelbrecht > <[email protected]> wrote: > > Tim Hare wrote: > >> Because of scheduling dumbness (another story) they have several gaps in >> their batch window where nothing runs, giving some leeway for jobs to >> increase their elapsed time - not the usual thing you want to do, but bear >> with us. > > What are the other STCs doing? Were they also busy or were they also idling? > > >> Would it be worth investigating setting a resource group limit for the batch >> service class(es) to hold the total 4HRA down as a cost-saving measure, or >> are resource group limits going to cause more trouble than they are worth? > > Good question. If you get any good replies on that, please post them on > IBM-MAIN if you can.
We had a similar issue at one company and add to the situation a real not in my world mind set. I would suggest possibly bringing in a 3rd party to take a real look at the issue. Some times a 3rd party can brake the log jam and start the cob webs moving. Ed ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
