Hello Jacob/All, "That JES2 initialization statement has nothing to do with job execution time limits.
TIME=nnnnnn Specifies execution times (1-279620), in minutes, that are to be associated with job-scheduling priorities, as specified in a corresponding PRIORITY parameter." Out of curiosity : If JES2PARM is initializing parameter and it has nothing to do with job execution time limits, then where does the current user submitted job statement reads the value like : PRIORITY=9 and TIME=NOLIMIT where we have not even added the IEFUTL exit. IEFUTL option looks to be a great EXIT to control the Job execution time limit.(Based on WTOR message to cancel) Jags On Tue, Dec 6, 2011 at 6:20 PM, Mark Jacobs <mark.jac...@custserv.com>wrote: > That JES2 initialization statement has nothing to do with job execution > time limits. > > TIME=nnnnnn > Specifies execution times (1-279620), in minutes, that are to be > associated with job-scheduling priorities, as specified in a > corresponding PRIORITY parameter. > > The keyword here is job-scheduling, not job execution. > > You'll have to write a user exit, IEFUJI comes to mind, to set, or > override job execution time limits. You should also consider having an > IEFUTL exit to get control when a job exceeds time limits, prior to > allowing it to time out. > > Mark Jacobs > > > On 12/06/11 07:07, jagadishan perumal wrote: > >> Hello All, >> >> In our shop whenever a user job is submitted by default the priority >> value is taken as "9". When I check the CPAC.PARMLIB(JES2PARM) below is >> the >> customization which talks more about the PRTY and TIME >> >> JOBPRTY(1) PRIORITY=9, /* Job Prty=9 if&RPRI1 ohwnc*/ >> TIME=2 /*< 2 min. exec. time&RPRT1 ohwnc*/ >> /* */ >> JOBPRTY(2) PRIORITY=8, /* Job Prty=8 if< 5 min.&RPRI2 ohwnc*/ >> >> TIME=5 /* etc. ohwnc*/ >> /* */ >> JOBPRTY(3) PRIORITY=7, /* Job Prty=7 if<15 min.&RPRI2 ohwnc*/ >> >> TIME=15 /* etc. ohwnc*/ >> /* */ >> JOBPRTY(4) PRIORITY=6, /* Job Prty=6 if nolim&RPRI2 ohwnc*/ >> >> TIME=1440 /* etc. ohwnc*/ >> /* */ >> /* >> >> 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. >> >> Our JES2 level : 1.8 >> There are no third party products to monitor JES. Could anyone please >> throw >> some light on the above and if there Are there any way to restrict the >> Jobs >> taking more than 5 minutes of processing time. >> >> Jags >> >> ------------------------------**------------------------------** >> ---------- >> 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<http://bama.ua.edu/archives/ibm-main.html> >> >> >> > > > -- > Mark Jacobs > Time Customer Service > Tampa, FL > ---- > > One of life's greatest mysteries is how the boy who > wasn't good enough to marry your daughter can be the > father of the smartest grandchild in the world. > > Yiddish Proverb > > ------------------------------**------------------------------**---------- > 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<http://bama.ua.edu/archives/ibm-main.html> > ---------------------------------------------------------------------- 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
