On Sun, 10 Aug 2008 21:38:12 +0000, Ted MacNEIL <[EMAIL PROTECTED]> wrote:
John wrote: >>I'm not really very knowledgable about WLM initiators, but wouldn't it be possible to only tell the JES2 on a particular system to service a specific class? E.g. JES2 on SY1 has a JOBCLASS(C) MODE=WLM defination in it. JES2 on SY2 has JOBCLASS(C) MODE=JES and does not have any "static" initiators set up to service class C. > JOBCLASS(n) definitions are MAS wide, so assuming this is one MAS, then that would not be possible. >I wouldn't mix up WLM & JES management in the same MAS. Why? Not only is there no harm in doing it, it is a requirement in many shops. WLM inits were not meant for jobs that need immediate initiation as there can be some delay. I can give many examples, but a simple one would be a batch job submitted from a CICS transaction that does something that needs a very quick turnaround. A WLM init might not even start at all in that situation if the system is running near 100% busy. What you aren't suppose to do is mix WLM inits and JES2 inits in the same service class. Which also means you can "ease into" WLM inits by converting a certain set of service classes first (test vs. production). Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
