Joined: 13 Jul 2006 Posts: 205 Location: At my desk
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:
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.
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
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.