IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Time=1440 to be avoided in production


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
meenakshi_forum
Warnings : 1

Active User


Joined: 27 May 2008
Posts: 121
Location: India

PostPosted: Tue Aug 03, 2010 10:29 pm
Reply with quote

Hi,

I need to know why Time=1440 should be avoided in production jobs?

Thanks
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Wed Aug 04, 2010 12:22 am
Reply with quote

It should be avoided in ANY job as it allows unlimited CPU time to be allocated to the job.

Just imagine if the code gets into a loop
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Wed Aug 04, 2010 5:15 am
Reply with quote

Hello,

On well managed systems, jobs with time=1440 are automatically purged and not executed. The only exceptions are certain system tasks (like CA-1, database, CICS, etc).

There is no good reason to ever submit any application job with time=1440. Other than being extremely dangerous, it is downright rude. . .
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Wed Aug 04, 2010 6:52 pm
Reply with quote

If you are trying to prevent a time-out abend, suggest you check with 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.

Here are some earlier threads:

www.ibmmainframes.com/viewtopic.php?t=50054&highlight=1440
www.ibmmainframes.com/viewtopic.php?t=46553&highlight=1440
www.ibmmainframes.com/viewtopic.php?t=41089&highlight=1440
www.ibmmainframes.com/viewtopic.php?t=32671&highlight=1440
Back to top
View user's profile Send private message
santy
Warnings : 1

New User


Joined: 19 Jul 2007
Posts: 22
Location: mumbai

PostPosted: Fri Aug 06, 2010 1:44 pm
Reply with quote

TIME=1440, is the maximum (Unlimited) time allowed for the job.

If you not put time parameter then some job execute for long time and might be goes into infinite loop.

to avoid that TIME=1440 is the best option.
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Fri Aug 06, 2010 1:50 pm
Reply with quote

Question asked
Quote:
I need to know why Time=1440 should be avoided in production jobs?
and this response
Quote:
TIME=1440 is the best option.
actually does not go with each other!

Suggest you read through the entire thread again and have a look on the given links.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Fri Aug 06, 2010 2:07 pm
Reply with quote

santy wrote:
If you not put time parameter then some job execute for long time and might be goes into infinite loop.

to avoid that TIME=1440 is the best option.
Please learn to comment on things that you actually have knowledge of and understand.
Your comment is completely ar$e about face.
Back to top
View user's profile Send private message
Garry Carroll

Senior Member


Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland

PostPosted: Fri Aug 06, 2010 2:14 pm
Reply with quote

Quote:
to avoid that TIME=1440 is the best option.


I would think that this was meant to read
"avoiding TIME=1440 is the best option."

Garry.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Fri Aug 06, 2010 7:31 pm
Reply with quote

Hi Garry,

Unfortunately, "santy" advocates using 1440 to avoid the timeout.

Far better would be to either fix the code or run in the appropriate class.

With some of the slop that is being permitted these days, some people (when they are not prohibited) are using 1440 so their jobs won't time out. . . What nonsense icon_rolleyes.gif

I'm completely in favor of these being auto-purged icon_exclaim.gif
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts To get the the current time DFSORT/ICETOOL 13
No new posts RC query -Time column CA Products 3
No new posts C Compile time time stamps Java & MQSeries 10
No new posts Parallelization in CICS to reduce res... CICS 4
No new posts Insert system time/date (timestamp) u... DFSORT/ICETOOL 5
Search our Forums:

Back to Top