|
View previous topic :: View next topic
|
| Author |
Message |
kvelisetti
Currently Banned
New User
Joined: 18 Oct 2012
Posts: 9
Location: india
|
|
|
|
| What is the maximum CPU execution time for a job and give the code? If this time is exceeded with which code does the job abend? |
|
| Back to top |
|
 |
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
1) Look at the manual (link at the top of the page)
2) Test it out
3) You forgot to ask Opal to make a cup of tea for you |
|
| Back to top |
|
|
kvelisetti
Currently Banned
New User
Joined: 18 Oct 2012
Posts: 9
Location: india
|
|
|
|
| TIME=1440 that implies a day but i heard it as 8 months and 25 days. |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| And what do you understand when you read about it? |
|
| Back to top |
|
|
kvelisetti
Currently Banned
New User
Joined: 18 Oct 2012
Posts: 9
Location: india
|
|
|
|
sorry to say i cannot access the forums.
does 'TIME=MAXIMUM' exist?
if not how to specify maximum time for execution of a job?
also please give a brief explanation of my first question. |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
Look at the JCL manuals. There is a link at the top of the page if they are not otherwise available to you at your site.
What you are asking/wanting is too simple to explain. If you have a problem with a potentially enormously long-running job, talk to your site support. |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
| Quote: |
TIME=1440 that implies a day but i heard it as 8 months and 25 days.
|
TIME=1440 is "forever". There are 1440 minutes in a day and the counter wraps to zero after 1439, so the jobs never reaches 1440 and therefore never gets cancelled. This is equivalent to TIME=NOLIMIT.
The default time limit is installation-dependent and job/step will abend S322 when this is exceeded. If the TIME= parameter specifies less than 1440, then the job/step will abend S322 if the specified time is exceeded .
Garry. |
|
| Back to top |
|
|
ezio vin
New User
Joined: 16 Aug 2012
Posts: 44
Location: india
|
|
| Back to top |
|
|
Escapa
Senior Member
Joined: 16 Feb 2007
Posts: 1399
Location: IL, USA
|
|
|
|
Even for 1439 you got to give strong justification and is often rejected ...  |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
| Quote: |
Even for 1439 you got to give strong justification and is often rejected ...
|
I always use it for my online regions - CICS, DB2, IMS, MQ - never an issue ... 
Garry |
|
| Back to top |
|
|
kvelisetti
Currently Banned
New User
Joined: 18 Oct 2012
Posts: 9
Location: india
|
|
|
|
hi vin,
does time=1440 implies time=nolimit.
also when we specify time=1440 you mentioned that cpu doesnt care about the execution time and keeps on execting.
my point here is how much time will it execute? |
|
| Back to top |
|
|
kvelisetti
Currently Banned
New User
Joined: 18 Oct 2012
Posts: 9
Location: india
|
|
|
|
hi garry 'forever' implies how much time i mean does it end in few months or years or does it still run?
if it ends in specific time is it same for all the mainframe vendors or does it defer? |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
Read Garry's first post.
What other mainframe manufacturers?
TIME=MAXIMUM has a limit. TIME=NOLIMIT does not. TIME=1440 is as Garry has said it is. |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
| kvelisetti wrote: |
hi garry 'forever' implies how much time i mean does it end in few months or years or does it still run?
if it ends in specific time is it same for all the mainframe vendors or does it defer? |
With TIME=NOLIMIT or TIME=1440, the job will keep running until cancelled by external intervention or on (e.g.) system failure.
It should be the same for all instances of MVS, z/OS operating systems regardless of machine though I have no experience of any non-IBM mainframe vendor.
Garry. |
|
| Back to top |
|
|
kvelisetti
Currently Banned
New User
Joined: 18 Oct 2012
Posts: 9
Location: india
|
|
|
|
bill,
thats what i mean.
time=1440 is continous but does it end or not? |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| kvelisetti, you need to be aware that there is NO relationship between CPU time as coded on the TIME= parameter of the JOB statement in JCL and the amount of elapsed time the job will run. The amount of elapsed time depends upon the mix of jobs in the system, the number of jobs in the system, the relative priorities of those jobs, their use of CPU and I/O devices, and many other factors. A job that takes 15 seconds of CPU time at my shop can complete in 3 minutes when the system is not busy -- but when the system is busy, the same job has taken 8 hours or more to complete, even though the CPU time was the same. |
|
| Back to top |
|
|
kvelisetti
Currently Banned
New User
Joined: 18 Oct 2012
Posts: 9
Location: india
|
|
|
|
| Thank you robert. but my trainer mentioned it as 8 months and 25 days. |
|
| Back to top |
|
|
Peter cobolskolan
Active User
Joined: 06 Feb 2012
Posts: 104
Location: Sweden
|
|
|
|
| Time=1440 (= 60 x 24 ) "Round the clock" |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
| kvelisetti wrote: |
bill,
thats what i mean.
time=1440 is continous but does it end or not? |
The job will continue to run as long as any executing program in the job does not complete (either normally or abnormally) . Once a step completes, the job moves on to the next (if any) step (depending on condition codes) and when the last step completes, the job ends.
Garry. |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
This is hard work :-)
You mention a trainer. There is our "sister" site www.ibmmainframeforum.com which may be more appropriate for you.
There are 24 hours in a day. If you have a job running "all day" the CPU time used is going to be substantially less than 1440 minutes.
What 1440 means, is that there is no limit to the amount of CPU time that can be used by the JOB (if specified there) or the STEP (unless the JOB limits).
There is a maximum amount of TIME that you can specify. This will be your eight months thing. This is with TIME=MAXIMUM or by coding it out (the JCL manual gives you the numbers to put in).
If you actually code that, it would probably allow your job to run for a considerable number of years, all other things being equal.
TIME=1440 = TIME=NOLIMIT = No limit (except by TIME on JOB card if specified for a step).
The things that run "forever" are not things you will be involved with, most likely, other than by using them (look at the list Garry provided, ask your "trainer" about "started tasks"). |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| What is "8 months and 25 days"? We IPLed our mainframe on September 23, 2012. The previous IPL was July 11, 2011. We therefore had started tasks that ran for 14 months and 12 days with no issues. If your trainer told you no job can run more than 8 months and 25 days, then your trainer is wrong and need to go back to school as well. |
|
| Back to top |
|
|
kvelisetti
Currently Banned
New User
Joined: 18 Oct 2012
Posts: 9
Location: india
|
|
|
|
| thank you. |
|
| Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
| kvelisetti wrote: |
| Thank you robert. but my trainer mentioned it as 8 months and 25 days. |
Your trainer is badly confused...at least. I suggest that you smile and nod, ignore everything that heesh says, and seek more accurate sources of information. |
|
| Back to top |
|
|
kvelisetti
Currently Banned
New User
Joined: 18 Oct 2012
Posts: 9
Location: india
|
|
|
|
 thank you |
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
From the z/OS JCL Language Reference (an irony in the name, but there we are:
| Quote: |
minutes
Specifies the maximum number of minutes a job may use the processor. Minutes must be a number from 0 through 357912 (248.55 days).
Do not code TIME=0 on a JOB statement. The results are unpredictable.
seconds
Specifies the maximum number of seconds that a job may use the processor, in addition to any minutes that you specify. Seconds must be a number from 0 through 59. |
Why somebody decided to "convert" CPU minutes into a number of "days" I have not the slightest idea. If those many minutes are specified, the job will not suddenly stop after "eight months and something days". Remember also. There is no "standard" length for a "month" even... so how some "exact" number of months and days could be meaningful even at that level, I don't know. |
|
| Back to top |
|
|
|
|
