The WCC display doesn't seem to show failed jobs in job run
search cancel

The WCC display doesn't seem to show failed jobs in job run

book

Article ID: 44071

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent

Issue/Introduction

The WCC display doesn't seem to show failed jobs in job run

Environment

Release: ATSYHA99000-11.3.6-Workload Automation AE-High Availability Option

Cause

The command was specified as c\:\demo\sleep1.exe

The job was failing with the error “CAWA_E_20015 Command/Script not found.Error code: 20007 “

The process was not created since the file was not found. Hence there was no job run for the failed job. 

Resolution

There is a configuration named “oscomponent.cmdprefix.force” in the agentparm.txt. If the parameter is set to true in windows it indicates that the agent submits the command using cmd.exe. The command is prefixed with "cmd /c" to allow built-in commands such as dir and echo to execute properly. 

This is a default entry in the agentparm.txt when you install the agent in AutoSys compatibility mode. 

 

Additional Information

CA WA System Agent for UNIX, Linux, Windows, or i5/OS Agent Parameters

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-system-agent/11-3/reference/ca-wa-system-agent-for-unix-linux-windows-or-i5-os-agent-parameters.html