AutoSys Workload Automation

 View Only
Expand all | Collapse all

Avoid Parallel execution of dependent Boxes and usage of look back

  • 1.  Avoid Parallel execution of dependent Boxes and usage of look back

    Posted Dec 03, 2024 12:53 PM
    Hi,
     
    I have faced below scenario and wanted to clarify few things of Autosys behaviour and how we can use look back option.
     
    Consider No date_Condition for both BOX.
     
    BOX_B:
    Condition: s(BOX_A)
     
    BOX A completed at 10 AM Monday
    BOX B completed at 11 AM Monday
     
    BOX A triggered at 10:05  & B triggered 10:04 ( didn't wait for new run of BOX A) Next day.
    Whether BOX B will consider Monday 10 AM completion of BOX A status and trigger BOX B on Tuesday? 
    To handle:
    Will below look back will work to avoid above unexpected scenario ? BOX B will trigger only after sucessfull next new run? please advise. how putting 0 will wait for 0 mins ? or how its work
     
    Jil of BOX B would be as below 
    BOX_B:
    Condition: s(BOX_A,0)
     
    Thanks in advance.


  • 2.  RE: Avoid Parallel execution of dependent Boxes and usage of look back

    Broadcom Employee
    Posted Dec 04, 2024 03:27 AM

    Hi Veera,

    It sounds like there has probably been a failure in BOX_A at some point and then BOX_B has held onto the status of that. One thing you could do at the end of your batch is to inactivate both boxes in preparation for the next run.

    You also correctly say that the usage of a lookback condition will assist in this scenario too. From the documentation on lookbacks, when you specify 0, AutoSys Workload Automation examines the last end time of the job first. It then examines the last end time of the condition job. If the condition job has run since the last run of the job for which the condition is coded for, the job is allowed to start. If the condition job has not run since the last run of the job for which the condition is coded for, the job is not allowed to start.

    More information on lookback conditions can be found here:

    https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/autosys-workload-automation/24-0-00/reference/ae-job-information-language/jil-job-definitions/condition-attribute-define-starting-conditions-for-a-job.html#concept.dita_786915b26a4b3d5a37f3cedc0c9adf3d406804ea_LookBackDependencies

    Hope this helps!

    Thanks

    Richie



    ------------------------------
    Best regards
    Richie Heaney

    Automation Capability Specialist
    Agile Operations Division, Broadcom
    ------------------------------