Specifies the default for the maximum processor time that each job step may run. And that CPU Time not clock time.
So each step no more than 3 minutes. 3 mins 1 sec it fails on that step. So is there a specific issue you are trying to resolve? Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Jesse 1 Robinson > Sent: Monday, October 24, 2016 7:56 PM > To: [email protected] > Subject: Re: TIME= on JOB card vs. EXEC card > > OK, consider this case. All defaults, no TIME= coded anywhere. JES2 parms have > TIME=3. Five steps. How long will the job run? > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-302-7535 Office > [email protected] > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Anthony Thompson > Sent: Monday, October 24, 2016 6:50 PM > To: [email protected] > Subject: (External):Re: TIME= on JOB card vs. EXEC card > > As Lizette said. Default job TIME is set in the JOBCLASS definition in the > JES2 parameter deck. > > If JOBCLASS doesn't specify a CPU time limit, the IBM default is 30 minutes. > > Ant. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Lizette Koehler > Sent: Tuesday, 25 October 2016 9:36 AM > To: [email protected] > Subject: Re: TIME= on JOB card vs. EXEC card > > My understanding is the step is the step - but if coded on the JOBCARD it > rules it all. > > Also, if your JES2 JOBCLASS has a time lime, then that will control all of it. > > Found that out the hard way. > > So if you have a time limit on the JOBCLASS def in JES2, it takes precedent If > nothing major in the JOBCLAS def, but you have a STEP TIME coded, then so long > as the step time does not exceed the JOBCLASS it will work If you have TIME > coded on the JOB and it does not exceed the JOBCLASS, it will work If you have > TIME coded on the JOB and the STEP then the JOB TIME limit will restrict the > STEPs. If the total time executed for all steps exceeds the TIME= on the > JOBCARD then it abends. > > Good write up on KB here > > http://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieab5 > 00 > /iea3b5_JOB_and_EXEC_TIME_parameter.htm > > > By coding TIME=1440 or TIME=NOLIMIT, the TIME parameter can instead be used to > give a job or step an unlimited amount of time. Specifically, the system > allows a step to remain in a continuous wait state for an unlimited time, > rather than the time limit established through SMF. However, if TIME=1440 is > specified on the JOB statement, any TIME values on an EXEC statement and any > default TIME values will be nullified. All steps within the job will have > unlimited time, as with TIME=1440 or TIME=NOLIMIT. > > > Note: the JES2 JOBCLASS definition can make things interesting. > > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Jesse 1 Robinson > > Sent: Monday, October 24, 2016 3:31 PM > > To: [email protected] > > Subject: TIME= on JOB card vs. EXEC card > > > > It's embarrassing to have to ask this question after decades in the > > biz, but I want to confirm my understanding of the TIME parameter and > > how it works on the JOB card vs. EXEC PGM= (step) card. > > > > The doc is pretty clear about the step level. What you code (or accept > > as default from JES) sets the limit for that step. When you reach that > > limit, IEFUTL gets control. This is true for each individual step > > regardless of other steps. > > > > The role of TIME= on the JOB card is not so clear, especially in > > relation to a default. As I read the doc, there is no specific default > > for JOB time parameter. That is, the effective limit for the whole JOB > > is the sum of all the individual steps. If you don't want the job to > > run that long, you can code TIME= for some lower value. But you cannot > > increase the JOB time by coding a higher value. And if don't code it at all, > you get the sum of the steps. > > > > From the JCL manual: > > > > "You can use the TIME parameter on a JOB statement to decrease the > > amount of processor time available to a job or job step below the > > default value. You cannot use the TIME parameter on a JOB statement to > > increase the amount of time available to a job step over the default > > value. To increase the allowable time over the default value, use the TIME > parameter on the EXEC statement." > > > > In other words, there is no explicit default value at the job level. > > Am I right? > > > > . > > . > > J.O.Skip Robinson > > Southern California Edison Company > > Electric Dragon Team Paddler > > SHARE MVS Program Co-Manager > > 323-715-0595 Mobile > > 626-302-7535 Office > > [email protected]<mailto:[email protected]> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
