Looks to me like you are not running this from the UNIX side as a user that is not 'DataStage aware' for lack of a better term. Typically, users that will doing things like this will be setup to do this automatically in their .profile - you need to 'source' the dsenv file first. Try this:
I think that you are missing your ENVironment settings for your job call. You should do a "cd `cat /.dshome`" followed by a ". ./dsenv" which should set your paths and variables up so that you can run dsjob.
sudharsanan wrote:In order any Datastage job through Unix command line.. you have to give dsjob command from the Datastage bin directory..
If you look at what was posted, you'll see that the OP did just that. It found the dsjob command, tried to execute it and promptly failed. I'm betting because of the issue that Arnd and I posted.
-craig
"You can never have too many knives" -- Logan Nine Fingers
If the $DSHOME/bin directory is in your PATH you can execute the dsjob command from anywhere. Or you can use the full pathname of dsjob, as illustrated below. But you do need the environment variables which are set in the dsenv script to have been set.
Thanks everyone...
I did not know about dsenv as it was not required on Windows platform to run dsjob...
Regards,
Ashwin
ray.wurlod wrote:If the $DSHOME/bin directory is in your PATH you can execute the dsjob command from anywhere. Or you can use the full pathname of dsjob, as illustrated below. But you do need the environment variables which are set in the dsenv script to have been set.
Hi,
such commands will not affect other settings? only will properly set the paths for dsjob to be run?
ArndW wrote:ashwin2912,
I think that you are missing your ENVironment settings for your job call. You should do a "cd `cat /.dshome`" followed by a ". ./dsenv" which should set your paths and variables up so that you can run dsjob.