Thanks everyone for their replies.
My thinking on discretionary has been similar to Tom Marchant's - I
think it is a good fit for batch. If you are running at 100% and
discretionary isn't getting service, I would suggest you don't have
enough work in discretionary - or you really do need a bigger processor.
I also see discretionary as the buffer that allows you to run at 100% -
it is the cushion that absorbs the peaks and troughs in your other work,
much faster than WLM can make adjustments. If you are running at 100%
without much discretionary the ride can be a bit rocky.
> what prioritizes production over test / development batch?
In the past I have used performance periods - production got a much
longer first period with a response time goal, test a shorter first
period. Second period for both was discretionary.
Jobs that were time critical were handled in a separate service class
with goals to match.
In reality the production/development distinction can be a bit political
anyway - production batch tends to be scheduled, whereas
test/development batch is submitted by someone waiting for the result.
So often it is delays to the test/development batch that cost real money
i.e. productivity.
Multiple periods often seem to be the best fit for general batch - the
distinction between short batch, where someone might be waiting for it
and long batch where people expect it to take a long time can be more
significant than test/development/production.
Regards
Andrew Rowley
--
Andrew Rowley
Black Hill Software Pty. Ltd.
Phone: +61 413 302 386
EasySMF for z/OS: Interactive SMF Reports on Your PC
http://www.smfreports.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
