Run Jobs on varying schedules - AE

[Legacy User]

Lets have a discussion about a commonly asked question from many of our customers. Here's the scenario

 

Job A runs every day of the week at 2am

On Sundays, the job should run at 3am instead of 2am

On Month End, the job should run at another schedule

 

Right now they schedule the off-schedule jobs (Sunday and month end) as separate jobs.

 

JMO had a little feature that would allow you to do something similar to this, without the need to create additional jobs.

 

What have your experiences been around this area?

 

Thanks,

Deekshit

[Steve Carrobis]

There's no need for discussion.. it's quite simple. I have taught this scenario for 20 years    all those in my class know it as FIZBIN.. they will tell you :-)

 

if its one job. then create 3 jobs.

 

if its a jobstream then use global variables and have the global set for those time periods via jobs  and have the jobstream run on the global variable being set

use of global variable over FORCESTART is much safer so use globals better to be safe than fired..

 

I am sure some fancy extended,standard has a hidden feature as well,  calendar magic can be done but then its way behind the curtain and could get lost in the shuffle. its best to do it out in open and have it documented..

 

good luck with the issue.

 

Steve C.

[Legacy User]

I think we all know what the situation is like today and what I am bringing forward is a common problem from customers. But thanks for your feedback.

[Steve Carrobis]

Deekshit

 

Agreed and I brought forth  the common answers to resolving those problems.

As i said there's 3 ways to handle the situation in AutoSys, It has been an issue for many many years. and it is handled as a said. duplicate jobs, global variable trigger, special calendar magic.

 

I am sure there are "other" ways to facilitate the resolution but it would mean an enhancement to the product  and it would have to be something that makes sense within AutoSys

     . e.g. taking a feature known from another product and figuring out how it can work with how autosys functions.

 

Part of our job is to perform miracles or request enhancements ;-)

It's all in a days work ... the key is not to overly compare, with another product but to facilitate a palatable solution ..

Hope this helps and hang in there .. ;-)

[Legacy User]

I agree Steve - and my hope was if it makes sense to the Product Management team to include it in AutoSys, then it should be included.

 

We all perform these "workarounds" as its not really a solution...its how the product was designed and its a limitation...which is why we work around the situation to get it moving forward.

 

What you are suggesting is the same approach I have taken for many many years. Not 20, but close to it...and the idea was not to compare...it was to see if there were other people who thought this would help if it was rolled in as an enhancement.

 

Thanks again

--Deekshit

[Chandru.Venkataraman]

job overrides, another workaround if you will...