AutoSys Workload Automation

 View Only
  • 1.  An Application runs twice a day - want to run a specific job once

    Posted Mar 02, 2017 11:21 AM

    I have a CAWA DE application that runs at 12 pm (noon) and 10 PM daily.  There is a job in the application that needs to only run at 1 PM.  One way that was suggested to do this is to set the job in question as "on request only", then in the predecessor job, have a java script that "requests" the job at the specific time , else the job is bypassed.

     

    Is there an alternate approach to this that doesn't require the use of java script?



  • 2.  Re: An Application runs twice a day - want to run a specific job once
    Best Answer

    Posted Mar 06, 2017 02:43 PM

    Its very easy. 

    Schedule the event:

    12pm daily

    10pm daily

     

    Set the one job you need to run at 1pm like this:

    Run statement: 

    %IF(APPL._SHH == '12','true','false')

    Time Dependency: 1pm

     

    It will only load at 12pm.  Run at 1pm.  

     

    Try that with some simulations.  I believe that is what you are asking for. 



  • 3.  Re: An Application runs twice a day - want to run a specific job once

    Posted Apr 28, 2017 02:38 PM

    thank you Bill for the question on this situation and thank you April for the solution.  We had a request to day and I knew where to come find the answer

     

    sharon



  • 4.  Re: An Application runs twice a day - want to run a specific job once

    Broadcom Employee
    Posted Mar 06, 2017 11:52 PM

    Hi,

     

    You can also use Job Definition ->Time Dependencies -> Do not submit before 1 pm  to achieve the same without any javascript. Irrespective of when the event gets triggered , this job will only gets submitted at 1pm.

     

    Hope it helps!

    Ravi Kiran



  • 5.  Re: An Application runs twice a day - want to run a specific job once

    Posted Mar 07, 2017 11:13 AM

    Yes, but depending on the how the app is set up, this could cause other issues.  Is the application set to wait on previous generation, or maybe do not trigger if active? Can the other jobs in the app run simultaneously?  And what happens if something gets hung?  These are all variables that could cause issues if you just slap a 1pm wait time on there.  That method could cause other issues in the other jobs without knowing other requirements on the application running.