On Tue, 7 Apr 2009 18:41:21 -0500, John McKown <[email protected]> wrote:
>On Tue, 7 Apr 2009, Staller, Allan wrote: > >> Code/install IEFUSI to limit *ALL* test jobs to (e.g.) 5 min of cpu >> time. Code/install IEFUTL to calc elapsed time and extend (or not) as >> required. IIRC, All of the required info needed should be available to >> the exit >> >> Adjust CPU time limit to desired granularity based on your shop. Not too >> precise but it should come close to your needs. >> >> HTH, >> > >Problem: I must restict WALL CLOCK or ELAPSED time, not CPU used time. >It's a weird political thing. > You should be able to accomplish this with SMF / JES2 exits and automation. We did so in the past - back when I consulted here around Y2K - so I don't know / recall all the details. Only jobs in a long running test classes were canceled (by automation) based on $HASP308. JES2 exits (ThruPut Manager actually) enforced CPU time also by class. So unless something really strange happened, you wouldn't see a HASP308 for a test jobclass with a 5 or 10 minute CPU time limit. But it is a bad idea... the reason I don't know much about this and can't look at the details now is that I convinced everyone at the time that it was not an equitable control and the code was removed. 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
