On Wed, 1 Jul 2009 14:55:33 -0500, Richard Peurifoy <[email protected]> wrote:
>Mark Zelden wrote: >> On Wed, 1 Jul 2009 09:38:10 -0700, John Mattson <[email protected]> >> wrote: >> >> I am >>> currently negociating with my operators to get them to open up ENOUGH >>> inits because I have "loved" jobs sitting for 40 minutes waiting for inits >>> because "unloved" jobs are sitting on them, and only 20 inits started. >> >> >> WLM INITs are the way to go. >> >> But WLM inits aren't for all applications / needs. Many shops (including >> ours) have >> a class (or a few classes) set aside for JES2 initiators for jobs that must get >> initiated immediately, regardless of the system utilization being at or near >> 100%. >> This can be anything, but often, from what I have seen over the years, it >> is a job submitted from CICS or MQ that is part of a "transaction". > >You may also need to use JES inits if you need to control the >maximum number of jobs running in some class. We have a database >that doesn't support enclaves, so batch calls run at the same >priority as CICS calls. We need to limit the number of batch jobs >to keep online response time acceptable. > >-- You've always been able to set the max by JOBCLASS, but it used to be MAS wide. You've been able to do it by MAS member (a single system) since z/OS 1.8 . So no excuses. :-) 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
