On Thu, 14 Feb 2008 15:05:24 -0500, Angel Tamayo <[EMAIL PROTECTED]> wrote:
>Hi, >Customer had requested to start JES2 with all INITs drained, in order to >prevent that batch jobs start running on >INITs after the IPL and before batch processing application is fully up. > >What options do I have? > You can have the inits defined as drained in your JES2 parms. But ever since WLM inits, we added $PXEQ to the JES2 parms (before we converted to WLM controlled initiators). This works for both JES2 inits and WLM controlled inits. While we could issue the $SXEQ with automation at the appropriate time after an IPL, queues are held and our job scheduling packing is "held" until operations releases them. both. During our software change windows, we never issue $SXEQ and force jobs we need to run with $SJOB. Even when we had JES2 inits, we defined a single class as WLM controlled just for this purpose. It was a lot safer / cleaner then temporarily starting an init for a certain JOBCLASS then draining it again. 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
