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, <snip> I have been given a distasteful task. TPTB have decided that "test" jobs will only be allowed to run for a maximum of 2 hours of WALL CLOCK time. The only way that I've determined to do this is to set ESTIME NUM=120,OPT=YES to have JES2 issue a $HASP308 message. I will then trap that with CA-OPS/MVS. But I think this WTO is being issued by the JES2 started task, not the job itself. Is this correct? If so, that makes it very difficult to determine from the message which RACF user did the submit of the job. IOW, this is not going to be as "easy" as I had planned because I don't know the RACF id under which the job is running. Is this correct? Any ideas for a free/gratis solution? </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
