Execution time clarification

All questions about Control-M jobs definitions
Post Reply
User avatar
peterrowan
Nouveau
Nouveau
Posts: 22
Joined: 23 Dec 2008 12:00

Execution time clarification

Post by peterrowan » 04 Mar 2010 1:55

Our New day procedure runs at 12noon. If I put not before 2200 on the job executing tab
then does that mean it can run any time between 2200 and 2400 or does thatmean any time between 2200 and next start of day e.g before 12 noon the next day.

User avatar
philmalmaison
Nouveau
Nouveau
Posts: 1148
Joined: 08 Jun 2007 12:00
Location: Ile de France

Post by philmalmaison » 04 Mar 2010 2:24

it will run at 12noon with a new ODAT

regards
philmalmaison

User avatar
peterrowan
Nouveau
Nouveau
Posts: 22
Joined: 23 Dec 2008 12:00

Post by peterrowan » 04 Mar 2010 2:49

I thought that only happened if you put > in the time to field.

User avatar
Banshee06
Nouveau
Nouveau
Posts: 79
Joined: 10 Jul 2009 12:00
Location: Salem, Oregon

Post by Banshee06 » 04 Mar 2010 7:27

Our new day is also at 12:00 or noon.
If I have a job start at 22:00 then it will run at 10:00 pm that night
if you put 00:05 then it will run after midnight.

User avatar
peterrowan
Nouveau
Nouveau
Posts: 22
Joined: 23 Dec 2008 12:00

Post by peterrowan » 08 Mar 2010 12:51

I understand that if you put 2200 it will run at 22:00 after the ODATE was set at 12noon e.g. 10 hours later. The question is, what is the window it is allowed to run when you put 2200. Is it that it can only run between 2200 and 2400. As you get nearer to 2400 that window seems to get smaller e.g, if you put 2359 does that mean it has only one minute to run in. e.g if for some reason it doesn't run exactly on time because of quantitative resources restrictions if it is just one minute late does that mean it can't run at all until 2200 the next day which then forces a manual edit of the job or a manual force to get it to run earlier.

Also what happens to that ODATE instance if it doesn't run when it should. Will it run for that ODATE automatically at 12noon (not for the new ODATE).

User avatar
Banshee06
Nouveau
Nouveau
Posts: 79
Joined: 10 Jul 2009 12:00
Location: Salem, Oregon

Post by Banshee06 » 08 Mar 2010 4:36

Not sure I understand all of your questions but will try to explain what I think your asking. If a job is set to run at 22:00 and doesnt start in time because of resources then it will keep trying to run until 12:00 the next day when the newday starts again and if the job has not executed I think it will continue through the new day still waiting for that resource or if it is executing.

User avatar
peterrowan
Nouveau
Nouveau
Posts: 22
Joined: 23 Dec 2008 12:00

Post by peterrowan » 09 Mar 2010 11:35

You have answered my question. The issue is whether a job scheduled to not start before 2200 will be able to still run after midnight without being forced.

User avatar
Senthilkumar
Nouveau
Nouveau
Posts: 12
Joined: 03 Feb 2009 12:00
Location: Bangalore

Execution time clarification

Post by Senthilkumar » 12 Mar 2010 1:34

If you want to run a job not before 22:00 and run after the newday (depends on the resource Availablity). In the Time '2200' and until '>'. so It wont start before 2200 and it will run once the quantitative resource are available.

some times during the maintenance time, we used to do the same (that is until '>'). we stopped all the quantative resources. and after some time we release the resources, some of the jobs are Out of time window. so we put > in until filed so it will submit the job once the resources are available.

Thank you,
Senthil

Post Reply