Autosys commands not working due to unable to load modules
search cancel

Autosys commands not working due to unable to load modules

book

Article ID: 144010

calendar_today

Updated On:

Products

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

Issue/Introduction

Customer's attempting to execute AutoSys commands such as autoping, job_depends, autorep, etc. are unable to do so due to errors specific to libraries not found or unable to load module. Such example of errors is shown 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 .

 

Environment

Release : All releases of Workload Automation AE
Component : CA Workload Automation AE

Cause

The AutoSys environment has not been sourced. Thus, required libraries and paths are not defined and are preventing successful command execution.

Resolution

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 of the 4 environment profiles that will be present on the server. The files on your server will have your hostname appended to the filename.
autosys.csh.aixdb2de12
autosys.env.aixdb2de12
autosys.ksh.aixdb2de12
autosys.sh.aixdb2de12

You will need to source one of these in your user profile in order to be able to execute AutoSys commands.

  1. Open your user profile for editing using your choice of editors.
  2. Go to the bottom of your profile and add the line (including the preceding period): . /opt/CA/WorkloadAutomationAE/autouser.SAB/autosys.sh.aixdb2de12
  3. Save the file.
  4. Launch another terminal session and login back in.
  5. You should now be able to execute the AutoSys commands

Note: You will need to speak with your System Administrator to determine which of the 4 profiles to source for your environment.

Powered by Wolken Software