On Wed, 29 Jul 2009 11:11:38 -0500, Chris Craddock <[email protected]> wrote:
> If it was my ass on the line, I would want the application owner to >either make the decision, or have a policy of some sort in place to tell the >operator (or automation) what action to take. > Yep... none of our CPU limits are put in place for production jobclasses. If an operator / scheduler suspects a job looping (either from a monitor warning, SDSF display, much longer run time than prior history shows, etc.), they call the on-call programmer for that app. One thing ops can't do is see if the system is running at or near 100% and if the job in question is using a lot of CPU. That is SOP here. :-) 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
