Automic Workload Automation

  • Private Community

  • 1.  Set Objects in a Schedule to INACTIVE automatically

    Posted Oct 22, 2015 10:01 AM
    Does anyone know of a way with either UC4 scripting or perhaps the Application Interface (or any other method) to inactivate objects in a schedule? We know you can go to the schedule in Monitor mode and then set an object to Inactive, but this poses a challenge in certain situations here because we may want to inactivate something that runs in 2 days and we re-execute our schedules on a daily basis.  We do this because what was happening is people would make temporary changes and not undo them.  So we just re-activate schedules daily.  Which of course means any temporary modifications are lost.  So it's very tricky sometimes to inactivate things that aren't in the immediate future. Just wondering if anyone has figure this out.  Thanks.


  • 2.  Set Objects in a Schedule to INACTIVE automatically

    Posted Oct 22, 2015 10:25 AM
    I create static calendar keywords to suspend a process and when a single run is to be skipped you just assign that day to the calendar keyword and then the schedule can be refreshed whenever you need and process will not get activated on whichever date you want to skip


  • 3.  Set Objects in a Schedule to INACTIVE automatically

    Posted Oct 22, 2015 11:28 AM
    If you add a workflow around the object, the workflow can use task preconditions to interrogate a variable (e.g. VARA.OBJECT1.STATE, values = "ACTIVE" or "INACTIVE") and either run or skip the object.  


  • 4.  Set Objects in a Schedule to INACTIVE automatically

    Posted Dec 22, 2016 04:32 AM
    In addition to Peter´s solution (which ist my most preferred) you could do:

    A. Modify the JSCH object - Entry itself (possily you meant that "you can go to the schedule in Monitor mode and then set an object to Inactive")

    dkynrvp0ntr5.jpg


    B) You can set the job itself to inactive
    3d7zfme2kw3x.jpg

    C - a bit weird workaround
    You could specify a special QUEUE to run in and set it to STOP Mode (requires manual deletion of the job run)

    D- create an include with a STOP nomsg command and include this into your job


  • 5.  Set Objects in a Schedule to INACTIVE automatically

    Posted Dec 22, 2016 07:12 AM
    With a combination of scripting and API you could schedule a future execution of a process that sets your target object inactive. You could technically do this completely through AE scripting via export/import but it's easier to manage or modify via the API. 

    If if you want an example I can provide it. 

    If your schedules get reactivated daily but your objects do not you could just set the objects themselves inactive and while the schedule will execute the objects will not. This obviously doesn't help if the objects are used elsewhere unless you create a jobplan and deactivate the tasks against the objects in question. 


  • 6.  RE: Set Objects in a Schedule to INACTIVE automatically

    Posted Jul 30, 2020 03:56 PM
    Michael,

    I would appreciate an example of scripting the active/inactive objects solution you mentioned.

    We are migrating an existing ESP installation o Automic. The existing installation has a batch process that begins by 'suspending' a large number of applications (workflows in our Automic solution) to avoid interference. As the batch progresses, the suspended applications are 'resumed' by various batch applications once they are no longer in possible conflict. The most straight-forward method of replicating this function in Automic would be a Suspend task at the beginning of the batch workflow and a reusable Resume task in the appropriate child workflows where Suspend sets a workflow(s) or job(s) inactive and Resume sets the workflow(s) or job(s) active. None of the suspensions would occur while the wrokflow/task is executing so things like TOGGLE_OBJECT_STATUS or ACTIVATE/DEACTIVATE do not apply since there is not a run ID available.

    Thanks.
    Original Message


  • 7.  RE: Set Objects in a Schedule to INACTIVE automatically

    Posted Jul 30, 2020 07:24 PM
    We use the following method for dynamic deactivation of UC4 processing.  It requires a VARA, two workflows, and a little scripting.  You can be as clever as you want about scheduling the two workflows to activate/deactivate your processes when you need them to.

    Created a VARA.MYPROCESS.STATE variable.

    Created two workflows:
    1. SET.MYPROCESS.STATE.INACTIVE
    2. SET.MYPROCESS.STATE.ACTIVE

    And add this small script into any objects that need to be inactivated by this variable;

    :set &MyState# = get_var(VARA.MYPROCESS.STATE,state,1)
:print "MYPROCESS State: &MyState#"
:if &MyState# = "INACTIVE"
:   print "MYPROCESS.STATE is OFF. Terminating."
:   stop NOMSG
:endif


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

    Original Message