The issue is described by the following scenario:
A Linux job should execute a command like the following in a shell:
The variable &variable# should normally be populated in the Pre-Process of the job, e.g. with the date:
The script SomeShellScript.sh is a simple script with only this content:
I.e., the following command will be executed in Linux:
The resulting report shows, the input variable is passed to the script and displayed:
It might happen that the variable is not populated. E.g. you populate the variable &variable# not like in the example above, but is some script with e.g. IF-conditions. In this case, the command executed in Linux is:
The report now shows the following:
The job ends with:
Nevertheless, as can be seen in the report, the script was executed without the variable. Remarkable: The Output of the script is written after the Job ended statement of the job messenger.
Fazit: The job ends with ENDED_NOT_OK - aborted, but the script is executed. When e.g. an operator sees the job status, he/she might start the job again and the shell-script is executed twice. For some customers, this can cause problems.