<snip> I have read a few articles that say that multiple periods are not recommended for batch service classes. Multiple periods seems to be considered a bit old fashioned.
I haven't been able to find anything clearly explaining why. I have always felt that they worked well. My best guess is that it is something to do with the behaviour of WLM managed initiators but I'm not sure. Can anyone shed any light, or point me to some further reading? </snip> I can't point to anything specific, but my feeling has always been batch is batch is batch (possibly with a divide between test/dev/qc and production). I can't think of any WLM related reason for this recommendation. I can see a techno-political use for a "penalty" service class. i.e. If a particular job exceeds the installation defined limits for a particular type of work, migrate to a service class just barely above discretionary, as a "punishment". You might check here: http://www-03.ibm.com/systems/z/os/zos/features/wlm/ for further enlightenment. I myself have not been through all of the information available there. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
