Not what you asked for, but I divide my primary batch service class into
periods like so:
* Service Class BATCH - Batch jobs w/o specific goals
Created by user DBA on 2005/08/22 at 11:23:17
Base last updated by user DBA on 2014/04/14 at 16:51:03
Base goal:
CPU Critical flag: NO
# Duration Imp Goal description
- --------- - ----------------------------------------
1 1200 4 50% complete within 00:00:06.000
2 27000 4 95% complete within 00:01:30.000
3 4 Execution velocity of 10
This gets fast turnaround on very short jobs, even when the processor is
otherwise saturated with longer-running ones.
(I forget why I used execution velocity for period #3 instead of discretionary.
Perhaps WLM refused to initiate the job in a saturated system when the last
period was discretionary. z/OS 1.12, so behavior may be different for you.)
--
David Andrews
A. Duda & Sons, Inc.
[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
