Communication manager address change on all agents

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• Workload Automation Agent

Issue/Introduction

You had a network issue yesterday evening between the event demon, the application server and the autosys database. 
Due to this issue, you have restarted both the event demon and the application server. 

After the agents were restarted, the autosys instance changed the address of the communication manager they use
From 
communication.manageraddress_3=examplecompany.example.com 
To 
communication.manageraddress_3=example 

Environment

Autosys version 11.3.6 SP5 with cumulative fix 1. 

Resolution

When the agent is back online, AutoSys registers itself with the agent and sends the hostname name to use. 

Autosys uses the gethostname() O/S API to get the hostname. 

This means that, when the agent was back online, autosys collected on the machine the hostname "example" which is defined somewhere on the Autosys server machine.
 
To workaround that and be sure to always use the FQDN, you can uncomment the ManagerHostAlias value in the config.AUTOSERV, and specify the FQDN. Otherwise, you would need to work with your sysadmins to ensure that the hostname returns the FQDN on the server (as it likely did before the network problem you got).