View previous topic :: View next topic
|
Author |
Message |
madhu2010
New User
Joined: 30 May 2010 Posts: 10 Location: Bangalore
|
|
|
|
Hi,
If I want to run a jcl for 3 -4 days then what should be the TIME parameter?
please suggest.
thanks |
|
Back to top |
|
|
Phrzby Phil
Senior Member
Joined: 31 Oct 2006 Posts: 1042 Location: Richmond, Virginia
|
|
|
|
Your folks need to tell you about job classes first - the jobcard CLASS parm.
Ask them for all the details. They should have a one page doc as everyone needs this installation-specific info. |
|
Back to top |
|
|
madhu2010
New User
Joined: 30 May 2010 Posts: 10 Location: Bangalore
|
|
|
|
actually I was asked this question in an interview.
i told as to give TIME = MAXIMUM or TIME = 1440, but not sure whether right or wrong.
So pls suggest the correct answer for this. |
|
Back to top |
|
|
Phrzby Phil
Senior Member
Joined: 31 Oct 2006 Posts: 1042 Location: Richmond, Virginia
|
|
|
|
If I don't know an interview question, I either:
1. Make an educated gues, and let them know that's what I'm doing. No one knows everything, and they should be impressed that you can try to reason it out given other knowledge.
2. Tell them I am familiar with the (online?) documentation and use it frequently in such cases. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
My answer would have been that i do not/will not create jobs that need to run continuously for 3-4 days. . . |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
I would consider making it a started task. then the time parm would be redundent. |
|
Back to top |
|
|
nevilh
Active User
Joined: 01 Sep 2006 Posts: 262
|
|
|
|
Quote: |
I would consider making it a started task. then the time parm would be redundent |
In relation to the time parameter Started Tasks are subject to the same rules and restrictions as batch jobs |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
thx nevilh,
always thought started tasks,
by virtue of being in 'a class of their own',
automatically had different time constraints.
glad to be wiser. |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
madhu2010 wrote: |
If I want to run a jcl for 3 -4 days then what should be the TIME parameter? |
"3-4 days" is a very strange choice, even for an interview.
Quote: |
i told as to give TIME = MAXIMUM or TIME = 1440, but not sure whether right or wrong. |
So what was interviewer's reaction on that?
TIME=1440 exempts the job from all CPU and wait time limit checking the job can execute as long as it needs to. No S322 or S522 abend will occur for the job. TIME=NOLIMIT is the same as coding TIME=1440; no CPU time or wait time limit checking is performed by zOS.
However TIME=MAXIMUM allows the job to use up to 357,912 minutes of CPU time, or about 248.5 days of continuous CPU usage - much more than 3-4 days. |
|
Back to top |
|
|
|