Automic Workload Automation

  • 1.  Cancelling a job to include the processes running on the host machine (Windows)

    Posted Dec 07, 2016 05:28 PM

    We have had some questions recently regarding stopping a job in Automic. Sometimes when this is done, the process/sub-processes that is/are running will keep going. In order to cancel jobs and the associated process/sub-processes it creates, you can utilize the Job Object section of the Windows tab:

     

    https://docs.automic.com/documentation/webhelp/english/ALL/components/AE/10.0/All%20Guides/help.htm#ucaazz.htm

     

       
     

    Job object

     
     

    Determines whether the Windows Job object is   used to group a process (job) and all the sub-processes it creates.

     

    If an Automation Engine job which is assigned a Job object   is canceled, all sub-processes will also be canceled. Moreover, a Job object   signals its end when all sub-processes are terminated.

     

    Without a Job object, the Job has no control   of its sub-processes. As a result, this means the job may end even if   sub-processes are still running. Moreover, if such a job (without the Job   object) is canceled, sub-processes are not terminated. This is a burden in   automation and even for restarts.

     

    Note that the Automation Engine job does not end before all   sub-processes are ended. The job reports show whether a particular job used a Windows Job object.

     


  • 2.  Cancelling a job to include the processes running on the host machine (Windows)

    Posted Dec 07, 2016 05:57 PM


  • 3.  Cancelling a job to include the processes running on the host machine (Windows)

    Posted Jan 06, 2017 01:17 PM
    Spencer_Cockrell_39

    Thank you for this post.  Changing "Job object" to "No" has simplified one of our processes.  In our case the windows program we are launching invokes a process that uses AdobeReader to process PDF documents.  AdobeReader stays resident, and was not allowing the UC4 job to finish.  My workaround was to engineer a process to kill AdobeReader, but by changing "Job object" I was able to eliminate this workaround.