search cancel

Incorrect function error when command uses output redirection


Article ID: 74925


Updated On:


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


Command job on Windows fails when the command attribute in the job definition (JIL) includes standard error/output redirection (> or >>).
For example:
command: echo %DATE% %TIME% >> C\:\Temp\test.txt

The job log from the failed run shows the following message:
CAWA_I_20018 Job failed. Exit code 1, Status: "Incorrect function."


Missing System Agent configuration parameter "oscomponent.cmdprefix.force=true" and/or the Windows machine definition missing the "opsys: windows" (JIL) attribute.


CA Workload Automation AE r11.3.5 and r11.3.6.
CA Workload Automation System Agent 11.3 on Windows.


Update the CA WA System Agent agenparm.txt file with the following parameter and restart the CA Workload Automation System Agent service.

Setting oscomponent.cmdprefix.force=true causes the CA WA System Agent to submit the command using the Windows command interpreter (cmd.exe).

Excerpt from the job log with the aforementioned setting:
CAWA_I_20013 Command to be executed: "C:\Windows\SYSTEM32\cmd.exe" /c echo %DATE% %TIME% >> C:\Temp\test.txt

If "oscomponent.cmdprefix.force=true" is set in the agentparm.txt already, yet the "Incorrect function" error manifests, then ensure the Windows System Agent machine definition has the "opsys: windows" coded (JIL).

Additional Information

We do not recommend using output / error redirection in the command line. Instead, use the std_err_file and std_out_file JIL attributes to achieve the same objective.
For example:
Remove the ">> C\:\Temp\test.txt" bit from the command part of the job definition and add the following attributes:

std_err_file: >> C\:\Temp\test.txt
std_out_file: >> C\:\Temp\test.txt,Linux,Windows,oriSeriesAgentParameters-oscomponent.cmdprefix.force

<Command file not found> error on CA WA System Agent: