There's a system where their 4-hour rolling average maximum is always during their batch window, when they routinely reach their defined capacity limit, which in turn affects what they pay in a chargeback system.
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. 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? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
