Agreed. The OP's management wanted a 2 hr. elapsed time. How close is "good enough"? I do not know the granularity required by the OP. Is 2hrs 10 min OK? 2 hr 20 min?
The limit needs to be set low enough that the s322 abend will be invoked within the granularity required by the O/P. Then IEFUTL will then get control to make the elapsed time calc and take appropriate action. <snip> >The use of IEFUSI is intended to be a trigger. This is to force invoke >IEFUTL at an interval so that elapsed time can be calculated. If the >elapsed time calc in IEFUTL indicates, for example, 10 miniutes elapsed, >set the IEFUTL retcode to extend the job. If it indicates 2 hrs & 1 >minute elapsed, allow the job to abend. > >This will not be precise, but it will be close. Feel free to contact me >off list if you like. It will not be close unless you make the CPU time limit very small. Certainly if you allow 5 minutes CPU time it will not be within one minute of wall clock time. It *especially* will not be close if the system is heavily loaded and the test job in question is not getting much access to the CPU. Perhaps if you make the CPU time limit 1 second it will be close enough, but then you will have a lot of IEFUTL exit calls. Sounds like an expensive solution to me. </snip> ---------------------------------------------------------------------- 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
