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.
>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
o: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 t
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
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
[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
; 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-M
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
,
-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
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
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
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
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
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
>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
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
>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
-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
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
; 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 a
...@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
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
to: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 m
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
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
25 matches
Mail list logo
