|
View previous topic :: View next topic
|
| Author |
Message |
ksikdar
New User
Joined: 30 Jun 2006
Posts: 13
|
|
|
|
Hi all,
Can some one tell me what is the execution time required for the job where in the JOBCARD it is mentioned that TIME = 1440 ? |
|
| Back to top |
|
 |
diwa_thilak
Active User
.jpg)
Joined: 13 Jul 2006
Posts: 205
Location: At my desk
|
|
|
|
Hi,
When the job executes more than normal time(depending upon the class) the job will abend saying time exceeded (or) it will be cancelled by the operator.
To avoid this abend we are giving the parameter as 1440 which is equivalent to time = nolimit.
Execution time will depend upon the job, in general we cannot say the how much time a job can run.
From the Manuals:
| Quote: |
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.
To allow a job or step to use the maximum amount of time, code TIME=MAXIMUM. Coding TIME=maximum allows the job or step to run for 357912 minutes. |
|
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
ksikdar,
I would like add some more.
time=1440 will be equal to 24 Hrs of CPU time, which will cost a lot, nearly $34,000 only for a single JOB(if JOB does not end even after 24 Hrs, which is unlikely), at least in my shop.
If you want to know the actual CPU time used for execution of some JOB,
then go JESMSGLG & give a search on 'Unnormalized CPU time'
You will get some message like this
Unnormalized CPU time: 0.05 seconds
This is the execution time of JOB. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Do not specify TIME=1440 on your job - even if your site doesn't automatically flush your job (many do). TIME=1440 is not a proper choice for programmers to make.
If you are trying to prevent a time-out abend, see your systems support or operations people. Your site probably has different job classes for different resources required. There may be a class already defined that will accommodate your cpu time requirement. If not, they can tell you what you need to do.
It would be good to determine just why the amount cpu time is needed. If your job processes many millions of records, it may very well not run in the same class that supports compiles and small testing.
If there are still questions after talking with your systems/operations people, please let us know. |
|
| Back to top |
|
|
|
|
