AutoSys Workload Automation

  • 1.  AutoSys failover

    Posted Jan 17, 2017 05:35 PM

    When AutoSys fails over how do you ensure the jobs running on primary server, continue to run on shadow server?  I used to define the jobs with machine:localhost, and thought this worked with 4.5. Jobs would continue running on shadow server.



  • 2.  Re: AutoSys failover

    Posted Jan 17, 2017 05:59 PM

    This still holds true. In the current release (11.3.6) when you define a machine using the scheduler hostname it is registered as localhost (you will see an associated message in the scheduler log).

    Then when you define a job using machine: localhost it will use the scheduler (local) hostname to run. So it will run on the active scheduler at runtime (primary or shadow).



  • 3.  Re: AutoSys failover

    Posted Jan 17, 2017 06:11 PM

    In addition to Mark's point....

    The following is from the $AUTOUSER/config.$AUTOSERV file:

     


    #+----------
    #
    # Keyword: LocalMachineDefinition=<name>
    #
    # Specifies the host name of a  type 'a' machine  that acts as  the
    # localhost. This machine must be defined in the event server.
    #
    # Notes:
    #
    # 1. If the LocalMachineDefinition parameter has  an empty value, a
    #    warning  message  is  issued  and  CA Workload  Automation  AE
    #    performs system calls to get the host name of the machine. The
    #    clients  can  add  a machine definition while the scheduler is
    #    running and the scheduler picks up this machine definition and
    #    starts running jobs on the localhost.
    #
    # 2. When you define a  job, if  you  set  the machine attribute to
    #    localhost,  and the  LocalMachineDefinition  parameter  has an
    #    empty value,  CA Workload Automation AE  runs  the job  on the
    #    localhost or on the  machine  where the scheduler is currently
    #    running.  The LocalMachineDefinition parameter  value must  be
    #    the same on both the primary scheduler and shadow scheduler.
    #
    #LocalMachineDefinition=



  • 4.  Re: AutoSys failover

    Posted Jan 18, 2017 10:56 AM

    Hi Chandru,

     

    Yes, I know about the entry in the configuration file for LocalMachineDefinition.  Here’s what we are looking for, we have many jobs defined(hardcoded in the jil), with the machine: dcav001.amfam.com,(primary server).   If AutoSys fails over to shadow server(dcav003.amfam.com),  jobs are  in a running state,  will the jobs continue to run, if I update the jobs machine to locahost?

     

    Please explain.

     

    Thanks,



  • 5.  Re: AutoSys failover

    Posted Jan 18, 2017 11:04 AM

    This is what we are looking to do:  we have many job where the machine attribute is hardcoded in the jil. If one of these jobs are in a running state and AutoSys fails over, we want the jobs to continue running on the shadow server.     Should changing the machine attribute to localhost be enough?    Thanks



  • 6.  Re: AutoSys failover

    Posted Jan 18, 2017 11:06 AM

    Why are jobs running on the EP?~

     

     

     

    Steve C.

     

     

    Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.

     

    Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.



  • 7.  Re: AutoSys failover

    Posted Jan 18, 2017 02:34 PM

    Jobs are executed by the System/Remote Agent on the host. If the job is in running status at the time of the EP/Scheduler failover to the Shadow, the Agent (on the Primary scheduler) would send the completion status to the Shadow scheduler, provided the failover wasn't caused by a server crash or network isolation.

    By changing the machine attribute to localhost, you ensure further/future runs of the job occur on the Shadow scheduler (again, the System Agent on the Shadow).



  • 8.  Re: AutoSys failover

    Posted Jan 18, 2017 05:34 PM

    The jobs running on the EP server are the crossover jobs to CA-7, mostly do a sleep 2.  And some housekeeping type jobs. 



  • 9.  Re: AutoSys failover

    Broadcom Employee
    Posted Feb 13, 2017 04:17 PM

    Hi,

     

    You need to configuration Failover Support for Cross-Instance Scheduling.

    Please see the product documentatin at this URL:

    https://docops.ca.com/ca-wla-ae-wcc/11-4-2/en/installing/ae-implementation/configuring-cross-platform-scheduling/configu… 

     

    Thanks,

    Zenghui (Jack) Liu