Workload Agent sending sendevent to the wrong scheduler

[Mark Shnayer]

I have built a new Linux R24 Autosys scheduler to replace our old Linux r11.3.6.8 scheduler.

The old scheduler machine is sch01asy
The old scheduler machine is sch07asy
I have copied the jobs from the old scheduler to new. I have removed the agent machine from the old scheduler and inserted it to the new scheduler. I bounced the old scheduler to ensure it doesn't have the agent cached anywhere.
The agentparm is updated to have the new scheduler connection only.

Both schedulers are still up. I am stuck with that till all jobs are cutover and turned off in the old scheduler. 
Everything seems to work except for any sendevent. The job on the new scheduler still tries to connect to the application server on the old scheduler and fails to perform sendevent and I can see the failure in the agent log

The agent correctly sends job status to the new scheduler (activated, running, failure, etc) but times out trying to perform sendevent on the old scheduler instead of running sendevent on the new scheduler.

CAUAJM_E_10527 Timed out waiting for response from the CA WAAE Application Server: [uvaapmmsch01asy:9000]
CAUAJM_E_50033 Error initializing tx subsystem:  CAUAJM_E_10062 Failed to get initial configuration from CA WAAE Application Server(s).

I am not sure what I can do to resolve this issue.

Thanks in advance,

Mark

[Chandrasekaran Venkataraman]

Hi Mark,

The client (CLI - sendevent, autorep and suchlike) goes by the AutoServer= parameter in the $AUTOUSER/config.$AUTOSERV (For example: /opt/CA/WorkloadAutomationAE/autouser.PRD/config.PRD) for the Application Server(s) to use. Maybe the agent is still pointing to the old 11.3.6 SP8 scheduler/application server host(s).

Hope that helps.

Best,

Chandru V