Jobs Running For Ever

Products

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

Issue/Introduction

Jobs remains in running status for ever, while it fails on the agent with an error code.

Environment

Release: All agent supported OS
Component: Workload Automation Agent

Cause

When job fails with specific error codes, the status is not sent back to the scheduler (Default: 255 for UNIX, 127 for Windows).

This happens when the below parameter is not set in agentparm.txt file :

oscomponent.noexitcode

Specifies the exit code that tells the agent not to send a completion code to the scheduling manager host.

Default: 255 for UNIX, 127 for Windows

Resolution

When job runs for ever on the scheduler and you notice that the job has already failed on the agent with an error code in the spool file

Please add the following parameter to agentparm.txt for the respective agent and restart the agent:

Windows:  oscomponent.noexitcode=128
UNIX/Linux: oscomponent.noexitcode=256