<Command file not found> error on CA WA System Agent

book

Article ID: 72530

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

Issue/Introduction

Command job fails with error <Command file not found> error.

autorep -j test_job -d

Job Name Last Start Last End ST Run/Ntry Pri/Xit
________________________________________________________________ ____________________ _______________
test_job 03/01/2018 16:05:23 03/01/2018 16:05:23 FA 15514/1 20007

Status/[Event] Time Ntry ES ProcessTime Machine
-------------- --------------------- -- -- --------------------- ----------------------------------------
STARTING 03/01/2018 16:05:23 1 PD 03/01/2018 16:05:23 WA_AGENT
RUNNING 03/01/2018 16:05:23 1 PD 03/01/2018 16:05:24 WA_AGENT
FAILURE 03/01/2018 16:05:23 1 PD 03/01/2018 16:05:24
<Command file not found>
[*** ALARM ***]
JOBFAILURE 03/01/2018 16:05:24 1 PD 03/01/2018 16:05:25 WA_AGENT

 

Cause

Some parameters may need to be added to agentparm.txt.

Environment

All Operating Systems

Resolution

Confirm the following parameters are set in the agentparm.txt:

oscomponent.lookupcommand=true 
oscomponent.cmdprefix.force=true 
oscomponent.cmdprefix.force.quotes.full=true


After making these modifications, save the agentparm.txt and restart the agent.

Additional Information

Note: If the job is still failing then check the path of the command.  The command path may need to be added to PATH environment variable or use the full path in the job.

E.g.

Instead of 'ls'  use:  /bin/ls