AutoSys Workload Automation

  • 1.  AutoSys Dependencies

    Posted Nov 03, 2012 08:30 PM
    Hi,

    Currently, using version AutoSys 4.5 - should be upgrading to r11 soon.

    I'm a basic user of AutoSys and would like to have some clarification around some scenario's.

    1) If Box A is dependent on Box B and both boxes are on different AutoSys instances, what's the best approach to enable this dependency?
    - in the past I've used "^". Are there any downsides to this approach?
    - Any performance issues? I've been led to believe using the "^" this may cause a performance issue.

    2) Box A is dependent on the SUCCESS of Box B and Box C. Both Boxes A, B and C run on a daily basis, which by definition Box B and Box C runs to SUCCESS then Box A runs to SUCCESS.
    - If Box B runs to SUCCESS on Monday, but Box C is still running or fails in effect Box A does not start meet it's starting conditions, so does not start on Monday. On Tuesday, Box C completes, Box B is still in a SUCCESS state from the Monday run, Box A is still in a Waiting (or equivalent) state from Monday. Does this mean Box A will start immediately after the SUCCESS of Box C, using the previous day SUCCESS of Box B and Tuesday SUCCESS of Box C?
    - What scenario's would mean Box A would run on a previous day SUCCESS of any of these jobs?
    - What would be the best approach to avoid the previous day SUCCESS of a Job?
    - Do we need some daily reset job - is this advised?
    - If using a reset job, how would this work - would there be any disadvantages of this approach?

    Thanks


  • 2.  RE: AutoSys Depencies
    Best Answer

    Posted Nov 07, 2012 04:29 AM

    asparmar wrote:

    Hi,

    Currently, using version AutoSys 4.5 - should be upgrading to r11 soon.

    I'm a basic user of AutoSys and would like to have some clarification around some scenario's.

    1) If Box A is dependent on Box B and both boxes are on different AutoSys instances, what's the best approach to enable this dependency?
    - in the past I've used "^". Are there any downsides to this approach?
    - Any performance issues? I've been led to believe using the "^" this may cause a performance issue.

    2) Box A is dependent on the SUCCESS of Box B and Box C. Both Boxes A, B and C run on a daily basis, which by definition Box B and Box C runs to SUCCESS then Box A runs to SUCCESS.
    - If Box B runs to SUCCESS on Monday, but Box C is still running or fails in effect Box A does not start meet it's starting conditions, so does not start on Monday. On Tuesday, Box C completes, Box B is still in a SUCCESS state from the Monday run, Box A is still in a Waiting (or equivalent) state from Monday. Does this mean Box A will start immediately after the SUCCESS of Box C, using the previous day SUCCESS of Box B and Tuesday SUCCESS of Box C?
    - What scenario's would mean Box A would run on a previous day SUCCESS of any of these jobs?
    - What would be the best approach to avoid the previous day SUCCESS of a Job?
    - Do we need some daily reset job - is this advised?
    - If using a reset job, how would this work - would there be any disadvantages of this approach?

    Thanks
    Ok, just my two cents:

    1) I'm not even aware of the fact that you can make dependecies cross instance (why should you use different instranced otherwise??).

    2)
    - Yes, Box A would start immediately.
    - Autosys 4.5.1 doesn't look at days. Unlike CA Unicenter NSM, Autosys 4.5.1 doesn't work with a Job tracking file (whioch is submitted at x time). There you could have dependecies that looks a day back (e.g. PREVIOUS/CURRENT).
    - Run a Job at x time (night?) that will change the Job status to SUCCESS (SENDEVENT command)
    - This is up to you. Does the programm or script you're running require that it comes to a success? If it doesn't you can do the reset, if not, you should make sure you fix the problem before running the reset command (SENDEVENT command)
    - No disadvantege as for Autosys. Like I said before, the program or script you're running is leading.

    Cheers,

    Danny


  • 3.  RE: AutoSys Depencies

    Posted Nov 15, 2012 12:38 AM
    Hi,

    1) for example, appears box A was setup as a dependency due on another box X on instance1, but we have box C in instance2 which should be dependent on box A. File watcher etc maybe the workaround here.

    2) just trying to cover all bases here, even if not a failure - ensuring a Job does not run from previous day success.

    Thanks,
    Amrit


  • 4.  Re: [CA AutoSys Workload Automation General Discussion] RE: AutoSys Depenci

    Posted Nov 15, 2012 03:45 AM
    Hi,

    Not sure I follow the first one but I think you can do both already. The second one was new in 11.3.

    Peter

    Sent from a mobile device; please excuse any errors.

    On Nov 15, 2012, at 5:38 AM, "CA Workload Automation (Distributed) Global User Community" <CommunityAdmin@communities-mail.ca.com> wrote:
    Hi,

    1) for example, appears box A was setup as a dependency due on another box X on instance1, but we have box C in instance2 which should be dependent on box A. File watcher etc maybe the workaround here.

    2) just trying to cover all bases here, even if not a failure - ensuring a Job does not run from previous day success.

    Thanks,
    Amrit
    Posted by:asparmar
    --
    CA Communities Message Boards
    99652243
    mb.2269986.99649703@myca-email.ca.com
    https://communities.ca.com