Correct. The JOBCLASS TIME will rule all TIME= for that class. If you do not exceed the JOBCLASS TIME= limit then either the JOBCARD or STEP will then enforce the limit.
If the JOBCLASS TIME=30 is coded (30 mins) then it will not matter to code TIME=60 on the JOBCARD or the STEP. The 30Mins for the JOBCLASS will enforce the time limit. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Burrell, Todd > Sent: Tuesday, October 25, 2016 4:53 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: TIME= on JOB card vs. EXEC card > > I thought that the jobclass time limit overrides everything - so for this > example wouldn't the time be 60? > > Examples (for one-step job): > jobclass ; JOBcard ; EXEC ; effective > 60 ; none ; 90 ; 90 - increased > > I thought that the jobclass was the maximum regardless of what you set on the > exec or job card? > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of R.S. > Sent: Tuesday, October 25, 2016 5:48 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: TIME= on JOB card vs. EXEC card > > W dniu 2016-10-25 o 04:55, Jesse 1 Robinson pisze: > > OK, consider this case. All defaults, no TIME= coded anywhere. JES2 parms > have TIME=3. Five steps. How long will the job run? > > > Answer: it depends. > First: we talk about CPU time, not "wall clock" time. > Second: we know there is a limit 3 minutes for whole job. Maybe each step > consume 2 seconds, then 2x5steps = 10s CPU. > Assumed first step consumed 30s the limit for the rest of the job is (2,30). > Assumed second step consumed 10s, the limit for the remaining steps is (2,20), > etc. > > Geeneral rules: > TIME=value coded in JOB can only DECREASE default value. > TIME=NOLIMIT or TIME=1440 in JOB card INCREASE the default to infinity (no > time limit) > > TIME coded in EXEC can INCREASE or DECREASE default value. > TIME=NOLIMIT or TIME=1440 in EXEC card INCREASE the default to infinity (no > time limit) > > When coded both JOB and EXEC, the most restrictive value is in effect. > > Examples (for one-step job): > jobclass ; JOBcard ; EXEC ; effective > 60 ; none ; none ; 60 > 60 ; none ; 10 ; 10 > 60 ; 70 ; none ; 60 - job value ignored > 60 ; 20 ; none ; 20 - job value decreased default > 60 ; 20 ; 10 ; 10 - most restrictive from > (job, exec) > 60 ; 20 ; 90 ; 20 - most restrictive from > (job, exec) > 60 ; none ; 90 ; 90 - increased > 60 ; 50 ; 1440 ; 50 - most restrictive from (job, > exec) > 60 ; 1440 ; none ; NOLIMIT > 60 ; none ; 1440 ; NOLIMIT > > Rule of thumb: KISS! > Keep It Simple! > > Don't code TIME in both JOB and EXEC > Be generous when setting default values. In case of TIME exhaustion abend the > most common scenario is to repeat the job with (hopefully!) bigger time limit. > So, setting time default small is a waste of time! ;-) > > > HTH > > -- > Radoslaw Skorupka > Lodz, Poland > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
