Job with exit code 127 or execution error with WA Agent (Autosys or dSeries)
search cancel

Job with exit code 127 or execution error with WA Agent (Autosys or dSeries)


Article ID: 219473


Updated On:


CA Workload Automation AE - System Agent (AutoSys) Workload Automation Agent CA Workload Automation DE - System Agent (dSeries)


Customer get exit code 127 when running the job with WA Agent.



Release : 12

Component : CA Workload Automation System Agent


The exit 127 normally refers to command not found.

If the command is available then agent install had issues, check nohup.stdout and nohup.stderr.  

Logs and joblog may show error like these:

XX/XX/20XX 00:00:12.345+0200: Preparing job 252.17638_1/WAAE_WF0.1/MAIN - 20XXXXXX 000012345-0200 WA_AGENT JavaAgent#tcpip@UAT_SCH 252.17638_1/WAAE_WF0.1/MAIN RUN . Data(Args="/opt/logs",Command="/bin/ls") ComponentType(AUTOSYS.APPSRV) .............
XX/XX/20XX 00:00:12.345+0200: Job 252.17638_1/WAAE_WF0.1/MAIN starting
XX/XX/20XX 00:00:12.345+0200: Execution error(error).




Check for errors in nohup.stdout and nohup.sterr.

If the nohup files report of any errors related to cybspawn, then agent install was incorrectly done or files were moved.

Check to make sure the user in the job has permission to run the command or script from the job.  Test the job manually to make sure the command actually works.