jagadishan perumal wrote: >We tried Changing the time parmeter as TIME=(5,0) , but still job takes more >than 5 mins. Even when user dont code the TIME,PRTY keyword it is even taking >more than 5 minutes of processing time for PRTY=9 value.
You've got good replies about scheduling priority against execution time, but ... JES2 Statement JOBCLASS(<?>) TIME=(min,sec) is about what the limits for each job STEP should be in case there is NOT a TIME statement in the JCL EXEC statement. Is it a problem of too much/little priority for that job (for that specific submitter) or too long wall clock time? Or do you have limited resources to justify those job execution limitation? >Are there any way to restrict the Jobs taking more than 5 minutes of >processing time. What is your goal to restrict it? Stopping a possible loop? Limiting output? Something else? I also see your answer: 'IEFUTL option looks to be a great EXIT to control the Job execution time limit.(Based on WTOR message to cancel)' IEFUTL is indeed a good exit, but if you want to limit batch jobs only, you need to add checks in that exit to ensure that limiting actions are done for batch jobs only. Or have SMF call that exit only for batch jobs. Just note that IEFUTL is called when the time limit expires for: - time limit from JOB statement, - time limit for step (from EXEC statement or default from JES2), - when there is a wait limit as stated in SMFPRMxx. Be careful with those WTORs... You may get replies which could give the operator a surprise pavement promotion. :-D HTH! Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
