ECLI Commands Fail With "command not found" Error

Products

• CA Workload Automation AE

Issue/Introduction

All ECLI commands fail with the following displayed in the Errors...

sh: <command>: command not found

where <command> is the actual command attempted.

Environment

Release : 12.0

Component : WORKLOAD CONTROL CENTER (WebUI)

Cause

In R12, the ECLI uses the AutoSys Web Server and logs into it as the Monitor ID. That is the ID that will be executing the command on the AutoSys server. The "command not found" error will occur when the MonitorID does not have permission to read the $AUTOSYS/bin directory on the AutoSys server.

Resolution

Ensure the MonitorID configured for the AutoSys server in WCC has permission to read the $AUTOSYS/bin directory on the AutoSys server. It will also need execute permissions on the commands within $AUTOSYS/bin.