Execute command issue

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
roy
Participant
Posts: 2598
Joined: Wed Jul 30, 2003 2:05 am
Location: Israel

Execute command issue

Post by roy »

Hi All,
I came across a strange behaviour.
A server routine that calls dsexecute to performs: more +n filea > fileb
works fine when executed from the test routine option but when used from a sequence job both via routine stage or exec command stage the output file is empty.
parameters are same for test and sequence job but only from test option the output file has the desired content.
Has anyone faced this issue before?

Thanks in advance for your time...

P.S.
If all fails I intend to write a routine that does the job in DS Basic code
(the original implementation was written a while back by someone)
Roy R.
Time is money but when you don't have money time is all you can afford.

Search before posting:)

Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Image
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Execute command issue

Post by ArndW »

My first thought is that the difference might be in the attach point for the process and it might work if you use absolute pathnames. You could check this by adding a "pwd" command to see where your process is attached.
Post Reply