Autosys job stopped working after agent upgrade to

Products

• Autosys Workload Automation

Issue/Introduction

A command job which used to work fine fails after the agent upgrade with error:

exec: command=1: not found

 

Environment

Workload Agent 12.1 

Resolution

The issue encountered after the agent upgrade was related to the following parameter set to “true” in agentparm.txt file of the new agent:

oscomponent.wrapper.exec.force=true

There were several commands in the job’s “command” attribute and this was causing the job failure because of the value of the “oscomponent.wrapper.exec.force” parameter modification.

Resolved by setting the “oscomponent.wrapper.exec.force” to “false” to allow to use multiple commands in the job’s command line.

You can consult the following documentation page for more information :

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/autosys-workload-automation/12-1/scheduling/ae-scheduling/command-jobs-overview/define-a-command-job.html

Define a Command Job

To support chained commands (commands that are separated by a semicolon) on UNIX, ensure that the oscomponent.wrapper.exec.force parameter in the agentparm.txt file is set to false (the default).