Time and Priority value clarification
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. timeRPRT1 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
Re: Time and Priority value clarification
That JES2 initialization statement has nothing to do with job execution time limits. TIME=nn 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 ifRPRI1 ohwnc*/ TIME=2/* 2 min. exec. timeRPRT1 ohwnc*/ /* */ JOBPRTY(2) PRIORITY=8, /* Job Prty=8 if 5 min.RPRI2 ohwnc*/ TIME=5/* etc.ohwnc*/ /* */ JOBPRTY(3) PRIORITY=7, /* Job Prty=7 if15 min.RPRI2 ohwnc*/ TIME=15 /* etc.ohwnc*/ /* */ JOBPRTY(4) PRIORITY=6, /* Job Prty=6 if nolimRPRI2 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 -- 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
Re: Time and Priority value clarification
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. timeRPRT1 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 Jgs, First very good post. If you want to limit the length of time a job runs, then the PRIORTY card will not do that. PRIORITY and TIME is the length of time a job is sitting in the queue before it gets bumped up to the next priority. You want to look at the JOBCLASS definitions for TIME. This is documented in the JES2 Init and Tuning Reference and JES2 Init and Tuning Guide (see section Operator control of the batch job workload). The following threads (done with a google of JES2 PRIORITY) should help in understanding JES2 job selection http://www.mail-archive.com/ibm-main@bama.ua.edu/msg11493.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
Re: Time and Priority value clarification
Hello Jacob/All, That JES2 initialization statement has nothing to do with job execution time limits. TIME=nn 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.comwrote: That JES2 initialization statement has nothing to do with job execution time limits. TIME=nn 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 ifRPRI1 ohwnc*/ TIME=2/* 2 min. exec. timeRPRT1 ohwnc*/ /* */ JOBPRTY(2) PRIORITY=8, /* Job Prty=8 if 5 min.RPRI2 ohwnc*/ TIME=5/* etc.ohwnc*/ /* */ JOBPRTY(3) PRIORITY=7, /* Job Prty=7 if15 min.RPRI2 ohwnc*/ TIME=15 /* etc.ohwnc*/ /* */ JOBPRTY(4) PRIORITY=6, /* Job Prty=6 if nolimRPRI2 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.htmlhttp://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.htmlhttp://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
Re: Time and Priority value clarification
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
Re: Time and Priority value clarification
Look at your JOBCLASS parameters. Mark Jacobs On 12/06/11 10:42, jagadishan perumal wrote: Hello Jacob/All, That JES2 initialization statement has nothing to do with job execution time limits. TIME=nn 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 Jacobsmark.jac...@custserv.comwrote: That JES2 initialization statement has nothing to do with job execution time limits. TIME=nn 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 ifRPRI1 ohwnc*/ TIME=2/* 2 min. exec. timeRPRT1 ohwnc*/ /* */ JOBPRTY(2) PRIORITY=8, /* Job Prty=8 if 5 min.RPRI2 ohwnc*/ TIME=5/* etc.ohwnc*/ /* */ JOBPRTY(3) PRIORITY=7, /* Job Prty=7 if15 min.RPRI2 ohwnc*/ TIME=15 /* etc.ohwnc*/ /* */ JOBPRTY(4) PRIORITY=6, /* Job Prty=6 if nolimRPRI2 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.htmlhttp://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.htmlhttp://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 -- 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
Re: Time and Priority value clarification
Thanks Jacob, I took a Look at JC(JOB CLASSES) option from SDSF panel to see the execution time coded on each Classes. This Information will help me in restricting the processing time. Jags On Tue, Dec 6, 2011 at 9:24 PM, Mark Jacobs mark.jac...@custserv.comwrote: Look at your JOBCLASS parameters. Mark Jacobs On 12/06/11 10:42, jagadishan perumal wrote: Hello Jacob/All, That JES2 initialization statement has nothing to do with job execution time limits. TIME=nn 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 Jacobsmark.jacobs@custserv.**commark.jac...@custserv.com wrote: That JES2 initialization statement has nothing to do with job execution time limits. TIME=nn 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 ifRPRI1 ohwnc*/ TIME=2/* 2 min. exec. timeRPRT1 ohwnc*/ /* */ JOBPRTY(2) PRIORITY=8, /* Job Prty=8 if 5 min.RPRI2 ohwnc*/ TIME=5/* etc.ohwnc*/ /* */ JOBPRTY(3) PRIORITY=7, /* Job Prty=7 if15 min.RPRI2 ohwnc*/ TIME=15 /* etc.ohwnc*/ /* */ JOBPRTY(4) PRIORITY=6, /* Job Prty=6 if nolimRPRI2 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.htmlhttp://bama.ua.edu/archives/**ibm-main.html http://bama.ua.**edu/archives/ibm-main.htmlhttp://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.htmlhttp://bama.ua.edu/archives/**ibm-main.html http://bama.ua.**edu/archives/ibm-main.htmlhttp://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.htmlhttp://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
