New AutoSys 12.0.0.1 install - unisrvcntr is in /opt/CA/WorkloadAutomationAE/autosys/csutils/bin but startup scripts are looking for old location

Products

• Autosys Workload Automation

Issue/Introduction

We have a fresh install of Autosys 12.0.0.1 - I was surprised to see unisrvcntr (and similar binaries) is now located in /opt/CA/WorkloadAutomationAE/autosys/csutils/bin and not /opt/CA/SharedComponents/bin/unisrvcntr.    The new location change isn't an issue, however the start up scripts are still looking for the old path via /opt/CA/SharedComponents/bin/unisrvcntr because /etc/profile.CA has CASHCOMP set to the old location. 

Can we just change CASHCOMP value in profile.CA?

 

# cat /etc/profile.CA
CA_SECTION=${CA_SECTION:-${1:-}}; export CA_SECTION #Set CA_SECTION to the first argument
CA_ETC_CAPROFILE() {
CASHCOMP=/opt/CA/SharedComponents; export CASHCOMP
if [ -f "$CASHCOMP/bin/csutils_envusr" ];then
     . "$CASHCOMP/bin/csutils_envusr"
fi
[ "$CA_SECTION" = "minimum" -a CASHCOMP ] && return 0
CABIN=/opt/CA/SharedComponents/bin; export CABIN
CALIB=/opt/CA/SharedComponents/lib; export CALIB
CA_CAILANGUAGE=enu; export CA_CAILANGUAGE
CSAM_SOCKADAPTER=/opt/CA/SharedComponents/Csam/SockAdapter; export CSAM_SOCKADAPTER
if [ -f "$CSAM_SOCKADAPTER/scripts/csamsetlibpath.sh" ];then
     . "$CSAM_SOCKADAPTER/scripts/csamsetlibpath.sh"
fi
CSAM_LOGGER_CONF=/opt/CA/SharedComponents/Csam/SockAdapter/cfg/logger.cfg; export CSAM_LOGGER_CONF
}; CA_ETC_CAPROFILE $CA_SECTION
[ "${CANOLOG_flag:-${CANOLOG_flag:-}}" = "off" ] && set +o nolog; CANOLOG_flag="" # return to system setting
[ "${CACSUTILS_setu:-${CACSUTILS_setu:-}}" = "1" ] &&  set -u; CACSUTILS_setu="" # return to system setting
CASYSEDGE="/opt/CA/SystemEDGE"; export CASYSEDGE

AUTOSYS_INSTALL_LOCATION=/opt/CA/WorkloadAutomationAE; export AUTOSYS_INSTALL_LOCATION

AUTOSYS_CSUTILS=/opt/CA/WorkloadAutomationAE/autosys/csutils; export AUTOSYS_CSUTILS

PATH=$AUTOSYS_CSUTILS/bin:$PATH; export PATH

 

# grep unisrvcntr /etc/init.d/CA-WAAE
# Check user id to allow any user to call unisrvcntr and start services as
         $CASHCOMP/bin/unisrvcntr start $COMP
      $CASHCOMP/bin/unisrvcntr start -X $COMP
         $CASHCOMP/bin/unisrvcntr shutdown $COMP
      $CASHCOMP/bin/unisrvcntr shutdown -X $COMP
      $CASHCOMP/bin/unisrvcntr cycle $COMP
      $CASHCOMP/bin/unisrvcntr status $COMP

Environment

Release : 12.0

Component : CA Workload Automation AE (AutoSys)

Resolution

This specific client installed a new AE/WCC host but did not realize it had an agent on it already.  As a result the CA-CCS file already existed and pointed to $CASHCOMP/bin/unisrvcntr which does not exist there in the new version.  Support provided the client with a CA-WAAE file from a fresh 12.x install and they removed the CA-CCS file as they had no NSM or CCI needs on this host.