AppWorx, Dollar Universe and Sysload Community

Expand all | Collapse all

Using an Absent condition does not function as expected

  • 1.  Using an Absent condition does not function as expected

    Posted 07-04-2017 09:54 AM
    The expectation was that by using an Absent condition, if the predecessor had a status of Event Wait, then the successor would not run.
    However, an Event Wait status does not meet the criteria of "Absent", as defined in the DUAS Reference Guide:

    ########
    Absent: means that the Uproc is neither running nor completed (either correctly or abnormally) nor waiting to run, but it does not signify that the Uproc is not scheduled. 
    It may even have already been activated, and waiting for an event. 
    ########

    A better approach might be to use the "If Planned" dependency condition available as of DUAS v6.8.01.

    ######## 
    The "If planned" option allows subtracting the condition of the launch formula if the expected job is not present in the job event database and is not scheduled (checked in this order). 
    This avoids unnecessary waiting or complex workarounds if the conditioning job is not scheduled at the same frequency as the conditioned job.
    ########

    Please refer to the Dollar Universe 6.8 Reference Guide for more details, at https//docs.automic.com/documentation/PDF/english/all/components/DU_AS/latest/Dollar+Universe+-+Release+Notes 


  • 2.  Re: Using an Absent condition does not function as expected

    Posted 05-08-2019 02:03 AM

    “If planned” does not work if the expected Uproc is running in a Session. That's too bad. Is there a workaround?