How to start CSAM automatically at boot-time on AutoSys client/agent machines.

book

Article ID: 19739

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation Agent CA Workload Automation Agents DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

Most client/agent systems have the agent configured to start at boot time.
As of AutoSys 11.3, CSAM (csampmuxf) is not necessarily used by the agent.
That configuration is optional.
If the agent is using plain sockets, CSAM is not started when the agent starts.
CSAM will start when the 1st client request happens, such as "autorep" or "jil".
Some customers would prefer to have CSAM already running.
Additionally, a user who issues an autosys command may lack privileges to actually start CSAM.

Our recommendation is to create a startup script for csam and place it in the boot startup sequence.

Create a new file, S99StartCsam
Add statements to source the /etc/profile.CA and to run /opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux start.

Example:

. /etc/profile.CA
opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux start

Then place the script along with the other boot time startup scripts.
Typically the startup scripts are located in the following locations:
Solaris/Linux: /etc/init.d
AIX: /etc/rc.d
HP: /sbin/init.d

Consult your Unix/Linux admin for more details regarding where in the boot sequence to place the script.

Environment

Release: ATSYHA99000-11.3.5-Workload Automation AE-High Availability Option
Component: