Re: AW: Re: TIME= on JOB card vs. EXEC card

[Bill Woodger]

Peter, yes, you are correct. I was thinking too narrowly, of TIME= from the 
JOBCLASS being the same or longer than on the JOB, as stated in the question. 

I liked your bucket analogy. A longer JOBCLASS TIME= than JOB TIME= will not 
allow a step to run for longer than what is on the JOB card. Indeed, no step 
can exceed what remains in the bucket when the step starts.. It is the same for 
a longer TIME= on the EXEC. The JOB TIME= is one time to rule them all...

For testing, I always use a short TIME=, LINE= being as small as needed and 
with ,C and estimate the output DASD in CYLS and specify as primary with no 
secondary. If it loops, the system notices it earlier than I would. 
Fire-and-forget. 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

AW: Re: TIME= on JOB card vs. EXEC card

[Peter Hunkeler]

>If you put TIME= on the JOB card, then this trounces the JOBCLASS TIME=, and 
>none of your steps, either the first step or in total, can exceed the TIME on 
>the JOB card.




While I agree with the second part, I do not with the first.


As I described earlier, the job level TIME= defines how much CPU time *all* 
steps may use in total. The JOBCLASS TIME= value will still be the default for 
every step *not* specifying TIME= on the EXEC statement.


However, the effective amount available to a step depends on how much is left 
in the job level bucket. And this may be less than asked for if the job level 
bucket is limited, i.e. if TIME= is specified on the JOB statement.


--
Peter Hunkeler



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TIME= on JOB card vs. EXEC card

[R.S.]

W dniu 2016-10-25 o 19:15, Jesse 1 Robinson pisze:

Answer inline

It's interesting to see varying opinions and interpretations. To reiterate: my 
question is not 'how to accomplish something' but merely how it actually works. 
So:

-- No TIME= of any kind coded on JOB or EXEC card

Then jobcard valu is used


-- JES2 time for a particular JOBCLASS is 3

Then it's 3 minutes per each step



-- Five steps in the job

Every step has 3 minutes (my fault in previous post)


-- No IEFUTL action

So the above is as I described. IEFUTL coudl change it.



-- No ISV product or RYO code

As above.




As I understand it, each step can use up to a maximum of 3. The whole job 
cannot use more than 15, the simple sum of all the steps. This is not an 
implicit limit, just the (coincidental) effect of 5*3 minutes of accumulated 
step time. Exceeding 3 on any step will cause S322; otherwise no abend.

Yes



Now, to accomplish my actual goal of abending runaway hard-loop jobs, we could 
add TIME= to the JOB card, which will effectively limit the step sum regardless 
of what any individual step(s) have coded. In other words, S322 for exceeding 
the JOB card value regardless of TIME= on any or all steps. Is this right?
Yes, but I would suggest coding TIME on EXEC card. You have 5 steps. I 
think only one of them is "suspected", isn't it?

So, remaining 4 steps do not need special control.



HTH
R.S.




-Original Message-

From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Tuesday, October 25, 2016 9:28 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: TIME= on JOB card vs. EXEC card

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.

CORRECTION: the below is valid for JOB TIME=3

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
.

Re: TIME= on JOB card vs. EXEC card

[Bill Woodger]

Yes.

The TIME= from the JOBCLASS only affects any EXEC which doesn't have an 
explicit TIME= (all of yours). If you put TIME= on the JOB card, then this 
trounces the JOBCLASS TIME=, and none of your steps, either the first step or 
in total, can exceed the TIME on the JOB card.

(you've not mentioned the use of PROCs, so I'll avoid pursuing that little 
discovery for now - I'm going to assume that that only kicks in with an 
explicit TIME= on the EXEC of the PROC).

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TIME= on JOB card vs. EXEC card

[R.S.]

W dniu 2016-10-25 o 18:28, Lizette Koehler pisze:

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.


No, EXEC TIME can increase the limit from the jobclass
JCL Reference is clear here:
"You can use the TIME parameter on an EXEC statement to increase or 
decrease the

amount of processor time available to a job step over the default value."

--
Radoslaw Skorupka
Lodz, Poland






---
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku 
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie 
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem 
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania 
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by 
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie 
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo 
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru 
Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. 
Wedug stanu na dzie 01.01.2016 r. kapita zakadowy mBanku S.A. (w caoci 
wpacony) wynosi 168.955.696 zotych.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TIME= on JOB card vs. EXEC card

[Jesse 1 Robinson]

It's interesting to see varying opinions and interpretations. To reiterate: my 
question is not 'how to accomplish something' but merely how it actually works. 
So:

-- No TIME= of any kind coded on JOB or EXEC card
-- JES2 time for a particular JOBCLASS is 3
-- Five steps in the job
-- No IEFUTL action 
-- No ISV product or RYO code 

As I understand it, each step can use up to a maximum of 3. The whole job 
cannot use more than 15, the simple sum of all the steps. This is not an 
implicit limit, just the (coincidental) effect of 5*3 minutes of accumulated 
step time. Exceeding 3 on any step will cause S322; otherwise no abend. 

Now, to accomplish my actual goal of abending runaway hard-loop jobs, we could 
add TIME= to the JOB card, which will effectively limit the step sum regardless 
of what any individual step(s) have coded. In other words, S322 for exceeding 
the JOB card value regardless of TIME= on any or all steps. Is this 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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Tuesday, October 25, 2016 9:28 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: TIME= on JOB card vs. EXEC card

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

Re: TIME= on JOB card vs. EXEC card

[Lizette Koehler]

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

Re: TIME= on JOB card vs. EXEC card

[Lizette Koehler]

Or products like Trident Software z/OSEM or MVS Solutions (?) Thruput Manager.

You could also look a EASYEXIT by DTS Software.

So if the JOBCLASS definition does not include a TIME= parm the default for that
class is 30 mins
If there is a JOBCARD TIME= it controls all steps.  So the total time on the
steps cannot exceed the TIME= On the jobcard 
  STEP1 TIME=2
  STEP2 TIME=3
  STEP3 TIME=2
  STEP4 TIME=8
  STEP5 TIME=3

So if the JOBCARD has TIME=5 (5 mins) the job would fail on step 3.
If there is no TIME coded on the JOBCARD.  Each step would get the time they
specify so long as it does not exceed the TIME= on the JOBCLASS

This is not clock time but CPU Time.  So the job may run longer (clock time) due
to being swapped out (I think) and not hit the TIME= limit.


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Allan Staller
> Sent: Tuesday, October 25, 2016 5:37 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: TIME= on JOB card vs. EXEC card
> 
> Try Jes2 Exit 6 to enforce the limits. I had some fun a while back writing
> some code to process the internal text of the job and force the values I
> wanted for the time parameter.
> 
> If TIME= was coded, it was forced to the expected value.
> 
> May also be done (I think) in IEFUSI or IEFUJI.
> 
> HTH,
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Jesse 1 Robinson
> Sent: Monday, October 24, 2016 10:37 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: TIME= on JOB card vs. EXEC card
> 
> Issue: we're trying to limit jobs to a particular amount of CPU time. I'm not
> sure of the relationship between JOB time and STEP time. I understand that
> TIME=3 on the STEP limits that step to 3. With 5 steps, what is the limit for
> the whole job?
> 
> .
> .
> 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
> robin...@sce.com
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Lizette Koehler
> Sent: Monday, October 24, 2016 8:08 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: TIME= on JOB card vs. EXEC card
> 
> 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:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Jesse 1 Robinson
> > Sent: Monday, October 24, 2016 7:56 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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
> > robin...@sce.com
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Anthony Thompson
> > Sent: Monday, October 24, 2016 6:50 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Lizette Koehler
> > Sent: Tuesday, 25 October 2016 9:36 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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 ex

Re: TIME= on JOB card vs. EXEC card

[Allan Staller]

Try Jes2 Exit 6 to enforce the limits. I had some fun a while back writing some 
code to process the internal text of the job and force the values I wanted for 
the time parameter.

If TIME= was coded, it was forced to the expected value.

May also be done (I think) in IEFUSI or IEFUJI.

HTH,

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Monday, October 24, 2016 10:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TIME= on JOB card vs. EXEC card

Issue: we're trying to limit jobs to a particular amount of CPU time. I'm not 
sure of the relationship between JOB time and STEP time. I understand that 
TIME=3 on the STEP limits that step to 3. With 5 steps, what is the limit for 
the whole job? 

.
.
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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday, October 24, 2016 8:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: TIME= on JOB card vs. EXEC card

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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Jesse 1 Robinson
> Sent: Monday, October 24, 2016 7:56 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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
> robin...@sce.com
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Anthony Thompson
> Sent: Monday, October 24, 2016 6:50 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Lizette Koehler
> Sent: Tuesday, 25 October 2016 9:36 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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.v2
> r2.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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson
> > Sent: Monday, October 24, 2016 3:31 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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 paramete

Re: TIME= on JOB card vs. EXEC card

[Elardus Engelbrecht]

Radoslaw Skorupka wrote:

>Answer: it depends.

Absolutely. For once, I have TIME to agree with you.
I wish I have TIME (sic!) to test your one step job examples, but... 


>Rule of thumb: KISS!
>Keep It Simple!

Indeed.


>Don't code TIME in both JOB and EXEC

We tell people to rather sit any TIME= in the JOB card, not in EXEC card, 
simply for KISS reason. 

Or, we just tell them use jobclass for classes reserved for TIME=1440.


>Be generous when setting default values. 

Yup, why bother with S322? S322 is so ancient...

We may be generous except in two/three classes reserved for quick and dirty 
short jobs (small TIME and REGION) with one step usually and no 
tapes/cartridges. 

We also don't use IEFUTL for batch jobs for this reason: KISS

Of course there are tradeoffs. If the system is really that busy, priority for 
jobs with TIME=1440 + excessive cumulative CPU usage are sometimes lowered.

Groete / Greetings
Elardus Engelbrecht

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TIME= on JOB card vs. EXEC card

[Burrell, Todd]

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






---
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku 
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie 
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem 
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania 
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by 
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie 
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo 
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
http://secure-web.cisco.com/1XhGrmetHLO9M1ggjBw161tA19oX0d7sQHzG-5ETRvY2DIDklDQo15AZbOpa7n4RGMW2JvnO5BgjwD6y_JjXWO11xlViSw-4QbeQXAWLta-WG052OLzgFjTZFt1QCY_kWRbi6KLtGtPFpjxSen-l-W9NQivgvh5cNsM20sW6woUo0euyvFuWVpxyeYvEPoqkQ8TZw0MVw7fu6QP8EpOxY8FKROyoYcne1Zuf9N1sbsRa81jQySZgO3n7dPXwh5l3ji9scsMLfEsQbYACly2252MkN0BYaHa2Fvwgb6eZr9d9XnkQwKXHGm_qH3L1LWkSttCWudHLiI-gRA0Id2Htxd65sNkbflur1ubIghp1vAR5sl7vomow4sgA1Nzk5M6iN/http%3A%2F%2Fwww.mBank.pl%2C%20e-mail%3A%20kontakt%40mBank.pl
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru 
Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. 
Wedug stanu na dzie 01.01.2016 r. kapita zakadowy mBanku S.A. (w caoci 
wpacony) wynosi 168.955.696 zotych.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



This email transmission and any accompanying attachments may contain CSX 
privileged and confi

Re: TIME= on JOB card vs. EXEC card

[Tom Marchant]

On Tue, 25 Oct 2016 11:47:34 +0200, R.S. wrote:

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?
>
>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.

Nope. From the JES2 Init and Tuning reference:


TIME=(mm,ss)|(30,0)  Specifies the default for the maximum processor time 
that each job step may run. The "mm" indicates minutes (0-357912); the "ss" 
indicates seconds (0-59). The value specified is subject to the limits 
described for the TIME parameter in z/OS MVS JCL Reference.

This default TIME= specification is used when no TIME parameter is specified on 
the JCL EXEC statement. (See z/OS MVS JCL Reference for further details on 
specifying the TIME parameter on the EXEC statement. See notes for $T job 
C=class in z/OS JES2 Commands for further details concerning the results of 
changing the job class.)

Modification: $T JOBCLASS operator command or cold start

Note: This parameter only defaults the TIME for the EXEC statement; not for the 
JOB statement.


-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TIME= on JOB card vs. EXEC card

[Tom Marchant]

On Mon, 24 Oct 2016 17:06:00 -0700, Lizette Koehler wrote:

>Good write up on KB here
>
>http://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieab500/iea3b5_JOB_and_EXEC_TIME_parameter.htm

This is from the JCL User's Guide.

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TIME= on JOB card vs. EXEC card

[R.S.]

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






---
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku 
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie 
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem 
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania 
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by 
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie 
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo 
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru 
Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. 
Wedug stanu na dzie 01.01.2016 r. kapita zakadowy mBanku S.A. (w caoci 
wpacony) wynosi 168.955.696 zotych.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

AW: Re: AW: Re: TIME= on JOB card vs. EXEC card

[Peter Hunkeler]

>I didn't know that about the EXEC of a PROC.


Nor did I. Interesting.


--
Peter Hunkeler



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: AW: Re: TIME= on JOB card vs. EXEC card

[Bill Woodger]

There's a useful description with examples here: 
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieab500/iea3b5_JOB_and_EXEC_TIME_parameter.htm

I didn't know that about the EXEC of a PROC.

How it works must hark back to long ago. You booked your time to use on the 
machine...

If trying to limit the CPU of multiple-step JOBs, remember that programmers are 
cunning, and will immediately switch to single-step JOBs. (warning for the use 
of a rude word) https://xkcd.com/810/

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

AW: Re: TIME= on JOB card vs. EXEC card

[Peter Hunkeler]

>So each step no more than 3 minutes.  3 mins 1 sec it fails on that step.


Think of it as there being a big CPU time bucket for *the job*.
There is a limited amount of CPU time in it when TIME= *is* specified on the 
JOB statement, or an unlimited amount, when TIME= *is not* specified on the JOB 
statement.

Then, there is another CPU time bucket for *the step*.
At step initiation each step gets the bucket replenished from the job level 
bucket. The amount the system *tries* to fill in is the value of the TIME= 
parameter on the EXEC, if present, or the value from the JOBCLASS (JES2, don't 
know about JES3) otherwise. If the job bucket does *not* have unlimited 
amounts, the step can only get the amount assigned if there is enought left in 
the job bucket. So a step might not get as much as it was assigned.
At step end, the system puts back into the job bucket whatever the step has 
*not* used.


--
Peter Hunkeler

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TIME= on JOB card vs. EXEC card

[Anthony Thompson]

Assuming the JOBCLASS has specified TIME=3, then coding TIME=3 on each job step 
is wasted  and redundant effort.

With five steps, each individual step is limited to 3 minutes of CPU time, and 
the total CPU time absorbed by all steps (by the job) is similarly limited to 3 
minutes. 

So if the first step uses 2 minutes, 59 seconds of processor time, the 
remaining four steps have a grand total of 1 second of CPU time to successfully 
complete in, irrespective of what in coded on the various step's TIME parameter.

Complicating the above simplicity is the possibility of an IEFUTL exit that may 
extend the CPU time limit, based on whatever operational or business logic. The 
exit is called whenever a step of job CPU time limit is reached (and when job 
wait time as defined in SMFPRMxx is exceeded).   

Ant.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Tuesday, 25 October 2016 1:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TIME= on JOB card vs. EXEC card

Issue: we're trying to limit jobs to a particular amount of CPU time. I'm not 
sure of the relationship between JOB time and STEP time. I understand that 
TIME=3 on the STEP limits that step to 3. With 5 steps, what is the limit for 
the whole job? 

.
.
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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday, October 24, 2016 8:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: TIME= on JOB card vs. EXEC card

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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Jesse 1 Robinson
> Sent: Monday, October 24, 2016 7:56 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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
> robin...@sce.com
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Anthony Thompson
> Sent: Monday, October 24, 2016 6:50 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Lizette Koehler
> Sent: Tuesday, 25 October 2016 9:36 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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.v2
> r2.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 m

Re: TIME= on JOB card vs. EXEC card

[Jesse 1 Robinson]

Issue: we're trying to limit jobs to a particular amount of CPU time. I'm not 
sure of the relationship between JOB time and STEP time. I understand that 
TIME=3 on the STEP limits that step to 3. With 5 steps, what is the limit for 
the whole job? 

.
.
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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Monday, October 24, 2016 8:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: TIME= on JOB card vs. EXEC card

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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Jesse 1 Robinson
> Sent: Monday, October 24, 2016 7:56 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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
> robin...@sce.com
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Anthony Thompson
> Sent: Monday, October 24, 2016 6:50 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Lizette Koehler
> Sent: Tuesday, 25 October 2016 9:36 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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.v2
> r2.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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson
> > Sent: Monday, October 24, 2016 3:31 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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 
> > def

Re: TIME= on JOB card vs. EXEC card

[Lizette Koehler]

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:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Jesse 1 Robinson
> Sent: Monday, October 24, 2016 7:56 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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
> robin...@sce.com
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Anthony Thompson
> Sent: Monday, October 24, 2016 6:50 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Lizette Koehler
> Sent: Tuesday, 25 October 2016 9:36 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Jesse 1 Robinson
> > Sent: Monday, October 24, 2016 3:31 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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 

Re: TIME= on JOB card vs. EXEC card

[Jesse 1 Robinson]

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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Anthony Thompson
Sent: Monday, October 24, 2016 6:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Tuesday, 25 October 2016 9:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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.ieab500
/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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Jesse 1 Robinson
> Sent: Monday, October 24, 2016 3:31 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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
> robin...@sce.com<mailto:robin...@sce.com>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TIME= on JOB card vs. EXEC card

[Anthony Thompson]

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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Tuesday, 25 October 2016 9:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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.ieab500
/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:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Jesse 1 Robinson
> Sent: Monday, October 24, 2016 3:31 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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
> robin...@sce.com<mailto:robin...@sce.com>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TIME= on JOB card vs. EXEC card

[Lizette Koehler]

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.ieab500
/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:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Jesse 1 Robinson
> Sent: Monday, October 24, 2016 3:31 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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
> robin...@sce.com<mailto:robin...@sce.com>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TIME= on JOB card vs. EXEC card

[R.S.]

This is plain stupid design.

JOB limits TIME for the whole job (all steps)
EXEC can further limit time for the step
Both can only limit default (JES) value.

However NOLIMIT (or 1440) provide another logic.

Advice: set TIME-enough_value on jobclass or TIME=1440 in EXEC amd forget.


--
Radoslaw Skorupka
Lodz, Poland






---
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku 
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie 
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem 
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania 
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by 
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie 
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo 
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru 
Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. 
Wedug stanu na dzie 01.01.2016 r. kapita zakadowy mBanku S.A. (w caoci 
wpacony) wynosi 168.955.696 zotych.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

TIME= on JOB card vs. EXEC card

[Jesse 1 Robinson]

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
robin...@sce.com


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN