DSXchange

I would think this should be no problem... You do need to install the MultiClientManager to switch between two versions.

Here is the command for export:

dscmdexport /H hostname /U username /P passowrd /O Omitflag project pathname /V

The single quote solved my problem. Although using both double and single quotes work fine on the unix command line, but I guess DataStage only likes the single quote.

Yes, the file path parameter stays the way as it was.

Thank you all again

yahooooo! It works. Thank you so much

Here is the exact input value for Afater-Job Routine ExecSH I used: sed "s/a/b/g" < #FilePath#/input.txt > #FilePath#/output.txt where #FilePath# is /dir1/dir2/dir3 I can see in the job log that the #FilePath# is expanded correctly, but there is nethier error messages nor output.txt file b...

Sorry for not clearly explained my situation. If you look at the built-in source code for routine ExecSH, it actually calls the DSExecute() function to execute the unix command. the output and msg (or should I say returncode) can be used for capturing what is going on. These two arguments returned n...

The command uses absolute path. The command does not work because there is no output.txt file created, and there is no output from the DSExecute("UNIX",..,output,msg) function to tell what went wrong.

Thanks,

Does anyone know why after-job routine ExecSH does not work on unix command like --> sed "s/a/b/g" <input.txt >output.txt ??

This command works fine if I run it on the command line.

Thanks.