Using TIME=1440 in JCL.

[Disha Shetty]

Hi

I was seaching on google and got a post whcih goes like this:

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 accomodate 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.

Why 1440 is not allowed?

[Robert Sample]

Because TIME=1440 is telling z/OS that this job can use as much CPU time as it wants. So if the job runs for the next six weeks, it still won't get timed out.

[ Post made via iPhone ]

[Marcels68]

The modern version of TIME=1440 is TIME=NOLIMIT

[Anuj Dhawan]

TIME=NOLIMIT

Pardon my ignorance but what is modern about it? I have used it around 11 years back!

Said that, do I sound old now!

The topic author is actually asking about why TIME=1440 is not allowed in production? And for that matter, TIME=NOLIMIT is just instructing exactly the same to system and so, as such, is not welcomed; and Robert has told why it is not a good practice.

[Shahid]

So TIME=1440 and TIME=NOLIMIT are equal? Or they are different? If they are different when should we use which parameter?

[Robert Sample]

The manual tells you they are the same and either can be used.

[ Post made via iPhone ]

[Disha Shetty]

Thanks for all the answers.