You use Scriptname in CA ESP Workload Automation to call shell scripts and the CMDNAME statement to run binary files as per the Reference Guide. At times, you are required to change Scriptname to CMDNAME to get the script to work.
search cancel

You use Scriptname in CA ESP Workload Automation to call shell scripts and the CMDNAME statement to run binary files as per the Reference Guide. At times, you are required to change Scriptname to CMDNAME to get the script to work.

book

Article ID: 52346

calendar_today

Updated On:

Products

Workload Automation Agent DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

Description:

CA uses Scriptname in CA ESP WA to call shell scripts and the CMDNAME statement to run binary files as per the Reference Guide. At times, we are required to change Scriptname to CMDNAME to get the script to work. When must I use the Scriptname over the CMDNAME method of calling the script?

Solution:

This is an example of the use of scriptname and cmdname:

SCRIPTNAME /usr/apps/scripts/cleanup.ksh

To correct, you had to change the SCRIPTNAME to the following:

CMDNAME /bin/sh
ARGS -c 'env +
/usr/apps/scripts/cleanup.ksh'

You can use the CMDNAME method for all scripts. There is no requirement to use the Scriptname over the CMDNAME method. The Scriptname method exists because it's simpler to code than the CMDNAME method. Note that the Scriptname method is only valid for Unix scripts. You must use the CMDNAME method for windows.

Environment

Release:
Component: SYSAGM