Jobs remains in running status for ever, while it fails on the agent with an error code.
All agent supported OS above r11.3 versions.
When job fails with any specific error code on the agent, the status will not be sent to the scheduler
This happens when the below parameter is not set in agentparam.txt file :
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 agentparam.txt for the respective agent and restart the agent: oscomponent.noexitcode=256