Automic Workload Automation

  • 1.  How to avoid daily and hourly jobs from clashing

    Posted Nov 05, 2015 04:30 AM
    Hi all,
    I have JOB1 that runs every Hour on an event. 
    I have JOB2 that runs every Day on a schedule.

    I want to avoid these jobs from clashing. 

    It's slightly more complicated by the fact that JOB1 runs on multiple Unix Hosts. The Host is passed into the Job via a variables.
    JOB2 also runs on multiple Unix hosts, the host also being passed in via variable.

    I'm only concerned about these jobs clashing if they are running on same Unix host.

    I'm sure there is built in Automc functionality to avoid this clash but I'm wrecking my brain to remember it.

    Can anyone help?

    Thanks,
    John.


  • 2.  How to avoid daily and hourly jobs from clashing

    Posted Nov 05, 2015 10:38 AM
    Depending how the tasks are activated you may want to consider using either a Sync or perhaps a Start type of a Group object.  I'm guessing that a Sync is the most straight forward and flexible.

    The "trick" might be the issue of the same job name executing on multiple hosts and you only care about execution on the same host.

    eta:  I see this was answered previously in a duplicate discussion - How to avoid clash of hourly and daily job


  • 3.  How to avoid daily and hourly jobs from clashing

    Posted Nov 05, 2015 11:11 AM
    thanks, didn't see this post before I closed it as it was in the wrong area. I'm not sure the SYNC will work for me.
    I don't want to have to create a SYNC object for every host, I may have 100 hosts....
    It might be easier to put some code into the actual script that JOB1 and JOB2 are calling to not execute if other job running on that host....


  • 4.  How to avoid daily and hourly jobs from clashing

    Posted Nov 05, 2015 11:27 AM
    I've done something similar using SYS_ACTIVE_COUNT with a Host parameter.  I've used either a loop with a WAIT statement or activate a Time Event with the WAIT parameter and the Event's ! Process again checks the count until it's 0 and ends so that the waiting job can continue execution.


  • 5.  How to avoid daily and hourly jobs from clashing

    Posted Nov 05, 2015 12:01 PM
    ok, thanks, will take a look at that.


  • 6.  How to avoid daily and hourly jobs from clashing

    Posted Nov 05, 2015 12:10 PM
    Yes, this works great, thanks for that.