Page 1 of 1

Running multi instance job from sequence job

Posted: Sun Apr 18, 2010 11:51 pm
by naren6876
Hi,
I am using the Execute Command stage to run the job as below

Command:
dsjob

Parameters:

-run -mode NORMAL -param SEQ_ID=#StartLoop_ID.$Counter# TEST testjob.#StartLoop_ID.$Counter#

But, job didn't started.

Please find the log below.

Executed: dsjob -run -mode NORMAL -param SEQ_ID=1 TEST testjob.1
Reply=127
Output from command ====>
SH: dsjob: not found.

Please advice.

Thanks in advance.

Posted: Sun Apr 18, 2010 11:59 pm
by ray.wurlod
In a word: PATH

Posted: Mon Apr 19, 2010 6:05 am
by chulett
Possible second word: full

Posted: Mon Apr 19, 2010 6:06 am
by ArndW
And I'll chip in one word as well - "Use"

Now push them all onto a stack and then read :D

Posted: Mon Apr 19, 2010 6:34 am
by naren6876
ArndW wrote:And I'll chip in one word as well - "Use"

Now push them all onto a stack and then read :D ...
Hi All,

Thanks for your responses.

I have ran the job as below
-run -mode NORMAL -param SEQ_ID=#StartLoop_ID.$Counter# /home/dsadm/Ascential/DataStage/Projects/TEST /home/dsadm/Ascential/DataStage/Projects/TEST/testjob.#StartLoop_ID.$Counter#

and

-run -mode NORMAL -param SEQ_ID=#StartLoop_ID.$Counter# /home/dsadm/Ascential/DataStage/Projects/TEST testjob.#StartLoop_ID.$Counter#


But, job didn't started.

The job log is
Executed: dsjob -run -mode NORMAL -param SEQ_ID=1 /home/dsadm/Ascential/DataStage/Projects/TEST /home/dsadm/Ascential/DataStage/Projects/TEST/testjob.1
Reply=127
Output from command ====>
SH: dsjob: not found.

Please advice.

Thanks in advance.

Posted: Mon Apr 19, 2010 6:46 am
by chulett
Thanks but nothing is helping so I'll just post the same error again? :?

SH: dsjob: not found

The SHell cannot find the 'dsjob' command. This is because, as Ray noted, its home directory is not in your PATH environment variable. One option to 'fix' that is to fully path the command, as I noted.

This is all Command Line 101 stuff regardless of operating system.

Posted: Mon Apr 19, 2010 7:58 am
by naren6876
chulett wrote:Thanks but nothing is helping so I'll just post the same error again? :?

SH: dsjob: not found

The SHell cannot find the 'dsjob' command. This is because, as Ray noted, its home directory is not in your PATH environment variable. One option to 'fix' that is to fully path the command, as I noted.

This is all Command Line 101 stuff regardless of operating system.
Hi,

Thanks for the responses.

i have ran the job from command prompt
$/home/dsadm/Ascential/DataStage/DSEngine/bin

$ dsjob -run mode-NORMAL TEST testjob
exec(): 0509-036 Cannot load program dsjob because of the following errors:
0509-150 Dependent module libvmdsapi.so could not be loaded.
0509-022 Cannot load module libvmdsapi.so.
0509-026 System error: A file or directory in the path name does not exist.

Do I need to fix something here or Datastage Admin can help me out in this regard?

Thanks in advance.

Posted: Mon Apr 19, 2010 8:07 am
by ArndW
Now that you've fixed the path issue, you have hit the next common error, discussed many times here. You need to source the "dsenv" file in the $DSHOME directory, this script sets up the environment and maps the directories. From UNIX the usual command is ". ./dsenv" when attached to the $DSHOME directory. Note the the command starts with a dot, then a space, then dot-slash-dsenv; that first dot is very important.

Posted: Mon Apr 19, 2010 8:20 am
by chulett
Note that this is now a "from the command prompt" issue and is not something you'll need to do for the Execute Command stage. You will, however, still need to resolve your PATH issue there.

Posted: Mon Apr 19, 2010 9:05 am
by naren6876
chulett wrote:Note that this is now a "from the command prompt" issue and is not something you'll need to do for the Execute Command stage. You will, however, still need to resolve your PATH issue there.
Thanks for the responses.

Please guide me to fix the PATH issue for the execute command stage?


Thanks in advance.

Posted: Mon Apr 19, 2010 9:27 am
by chulett
The way we noted here. Include where it lives in your PATH variable in the dsenv file. Or 'cd' to the directory first. Or fully path the command.