When running AutoSys r11.0 commands like autorep the results are displayed but so too are errors, CAUAJM_E_10029.

Document ID : KB000011004
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

When running AutoSys r11.0 commands like autorep the results are displayed but so too are errors, CAUAJM_E_10029.

Example:

$ autorep -J commandjob1   CAUAJM_E_10029 Communication attempt with the Unicenter AutoSys JM   Application Server has failed! [machine1:9000]      Job Name                Last Start            Last End           ST Run Pri/Xit   ______________________ ____________________ ____________________ __ _______ ___   commandjob1             10/24/2010 12:10:45  10/24/2010 12:10:46 SU    9636/1  

 

Environment:
Product: Workload Automation AE 11.0.XPlatform: Windows, UNIX, LinuxDatabase: Oracle, Sybase, MS SQL
Answer:

The above suggests that the AutoSys environment consists of multiple application servers. Typically one would see an entry like the following in the $AUTOUSER/config.$AUTOSERV: 

AutoServer=machine1,machine2,machine3 
AutoServerPort=9000

The client utilities, like autorep and jil, read the local $AUTOUSER/config.$AUTOSERV file to determine which application server host/port to contact to make its request. It reads the entries from left to right. In the above case it will always try machine1 1st. If machine1 was not available it would return an error like the one listed above CAUAJM_E_10029 and then proceed to try machine2. In the above case machine2's application server was available and returned the requested data.

Application servers do not rollover in a manner like Schedulers. Local requests will continue to try machine1 1st unless the config.$AUTOUSER file is modified, re-ordering the machines.