Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Time=1440 to be avoided in production

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
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    Post subject: Time=1440 to be avoided in production
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: 8593
Location: Back in jolly old England

PostPosted: Wed Aug 04, 2010 12:22 am    Post subject:
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

Site Director


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

PostPosted: Wed Aug 04, 2010 5:15 am    Post subject:
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

Senior Member


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

PostPosted: Wed Aug 04, 2010 6:52 pm    Post subject:
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:

http://www.ibmmainframes.com/viewtopic.php?t=50054&highlight=1440
http://www.ibmmainframes.com/viewtopic.php?t=46553&highlight=1440
http://www.ibmmainframes.com/viewtopic.php?t=41089&highlight=1440
http://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    Post subject: Reply to: Time=1440 to be avoided in production
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

Senior Member


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

PostPosted: Fri Aug 06, 2010 1:50 pm    Post subject:
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: 8593
Location: Back in jolly old England

PostPosted: Fri Aug 06, 2010 2:07 pm    Post subject: Re: Reply to: Time=1440 to be avoided in production
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

Active Member


Joined: 08 May 2006
Posts: 992
Location: Dublin, Ireland / Edinburgh, Scotland

PostPosted: Fri Aug 06, 2010 2:14 pm    Post subject:
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

Site Director


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

PostPosted: Fri Aug 06, 2010 7:31 pm    Post subject:
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    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Date and time format in CICS Chandru3183 CICS 2 Sat Mar 18, 2017 12:46 pm
No new posts How to get current date -1 and curren... murali.andaluri DFSORT/ICETOOL 3 Wed Mar 08, 2017 2:09 pm
No new posts CICS transaction slow response time vasanthz All Other Mainframe Topics 3 Thu Jan 19, 2017 1:31 am
No new posts HALDB data refresh/copy from producti... vineetanand2007 IMS DB/DC 1 Mon Jan 02, 2017 11:16 am
No new posts DD DUMMY & CPU TIME Nileshkul Testing & Performance analysis 16 Mon Dec 19, 2016 11:35 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us