Problem with execute_command activity

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Yes. This is a known issue with the Execute Command stage in some versions. If you know you are doing everything right, and the parameters are being correctly translated in the log, but the actual command still doesn't work - you're bugged.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

Maybe I am joining in the middle and missed a few lines.

In that case, you can try the 'echo' command to confirm that all parameters are being passed correct.

Secondly you can provide a wrong file name and see whether you get any output.
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Sainath.Srinivasan wrote: In that case, you can try the 'echo' command to confirm that all parameters are being passed correct.
My first request was to check this. May be the second option could also be used to confirm that.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Post Reply