Trying to run AutoSys commands such as autoping, job_depends, autorep, etc. results in errors like below:
exec(): 0509-036 Cannot load program /apps/autotree/autosys/bin/sendevent because of the following errors:
@0509-022 Cannot load module /apps/autotree/autosys/lib/libmsgII.so.
@0509-150 Dependent module libcasocket.so could not be loaded.
@0509-022 Cannot load module libcasocket.so.
@0509-026 System error: A file or directory in the path name does not exist.
@0509-022 Cannot load module sendevent.
@0509-150 Dependent module /apps/autotree/autosys/lib/libmsgII.so could not be loaded.
@0509-022 Cannot load module .
The AutoSys environment has not been sourced. Thus, required libraries and paths are not defined and are preventing successful command execution.
In order to be able to execute AutoSys commands on any machine, the AutoSys environment must be sourced!
Sourcing the environment is as easy as updating your logon profile on the Unix server to read in the AutoSys environment profile located in $AUTOUSER
on your UNIX server.
The $AUTOUSER
environment variable will vary in your environment. By default this location is set to /opt/CA/WorkloadAutomationAE/autouser.$AUTOSERV
(where $AUTOSERV
is the 3 character instance identifier).
Below is an example listing of the 5 environment profiles that will be present on your UNIX/Linux server. The files on your server will have your hostname appended to the filename.
autosys.bash.<hostname>
autosys.csh.<hostname>
autosys.env.<hostname>
autosys.ksh.<hostname>
autosys.sh.<hostname>
Depending on your OS and what shell you use, you will need to source one of these in your user profile in order to be able to execute AutoSys commands.
. /opt/CA/WorkloadAutomationAE/autouser.ACE/autosys.sh.<hostname>
Note: Contact your System Administrator for assistance if you are unsure about which user profile needs to be sourced for your environment.