On Thu, 17 Dec 2015 14:33:50 +0100, Peter Hunkeler wrote: >In other words, JES is *not* in control to tell any specific initiator >on any specific system "you're gonna work this job now". JES is >simply picking up the top most job in a jobclass queue and hands >it over to the initiator asking for work. > >What is different from the above (assuming it is correct) when the >initiators are WLM-managed? It is WLM instead of the operator or >automation package which decides when and where to start and >stop initiators for the WLM-managed jobclasses. That's it. > >Once initators are up and running, WLM is out of control which one >will get which job to work on. It is still the initiator that is going to >ask JES for work. And it is still JES that will pick up the top most >job from the jobclass queue.
I believe that what you write is correct. There is one difference with WLM-managed initiators that I am aware of. If there is a job that you want to run right now, an operator can issue the $S JOB command. When the command is issued, a new initiator will be started and it will run that job regardless of where it is in the queue. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
