Page 1 of 1

problem using execute command stage

Posted: Thu Aug 30, 2007 3:58 pm
by UPS
Hi,
I am running a dsjob (Multiple Instances) using a shell script from the execute command stage. If all the instances of the job run then i return a code 0 else 1. I trigger two different jobs based on the return code.I tried using stage_value.$CommandOutput and
stage_value.cmd.$ReturnValue
but both of them are not able to capture the return code of the shellscript
please let me know if there is a way in which I can capture the return code of the shell script

Re: problem using execute command stage

Posted: Thu Aug 30, 2007 4:44 pm
by chulett
UPS wrote:stage_value.cmd.$ReturnValue
Is that a typo? You should be using "stage_value.$ReturnValue" - there's no ".cmd" in there.

Posted: Thu Aug 30, 2007 4:56 pm
by michael_west
I switched to using routine stage with execSH routine because of problems with error handling. I don't remember what these problems were, but I don't have any problems now. It is a fine option for running scripts.

Re: problem using execute command stage

Posted: Fri Aug 31, 2007 2:23 am
by rajeevn80
Creating your own specific routine for this will be a better option.

Posted: Fri Aug 31, 2007 7:37 am
by chulett
Or perhaps... oh, I don't know... a Job Activity stage?