Automic Workload Automation

Expand all | Collapse all

How to accomplish the Automic equivalent of an Autosys "NO_EXEC"

  • 1.  How to accomplish the Automic equivalent of an Autosys "NO_EXEC"

    Posted 8 days ago

    There are time when we need to temporarily stop a WF from executing in the daily schedule, but not hold up external dependencies in downstream WFs.

    If we set the WF INACTIVE in the schedule the WF/jobs do not run but all downstream dependencies remain unsatisfied resulting in batch processing stopping while waiting for the jobs to complete in an INACTIVE WF (which will never happen).

    What is the recommended method for accomplishing our objective?

    Thank you.



    ------------------------------
    Global Workload Automation Engineer
    GM Financial
    ------------------------------


  • 2.  RE: How to accomplish the Automic equivalent of an Autosys "NO_EXEC"

    Posted 7 days ago
    Edited by Pothen Verghese 7 days ago
    Are you doing this under SCHEDULE object?

    If you set the JOB/WF INACTIVE that you wish to skip, within the parent workflow does it meet your requirement?

    Regards
    Pothen


  • 3.  RE: How to accomplish the Automic equivalent of an Autosys "NO_EXEC"

    Posted 7 days ago
    Probably the simplest is to put the following code on the Process tab of the workflow.  The workflow will generate and then end with an "ENDED_EMPTY - task is empty (STOP NOMSG)", though any dependencies will need to allow a status of ANY_OK for the workflow.

    :stop nomsg​



  • 4.  RE: How to accomplish the Automic equivalent of an Autosys "NO_EXEC"

    Posted 7 days ago
    We use the "stop nomsg" solution, and we typically make it conditional based upon the contents of a VARA object that can be dynamically manipulated to turn it ON and OFF.

    ------------------------------
    Pete Wirfs
    SAIF Corporation
    Salem Oregon USA
    ------------------------------