Running multi instance job from sequence job

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
naren6876
Participant
Posts: 233
Joined: Mon Feb 07, 2005 7:19 pm

Running multi instance job from sequence job

Post 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.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

In a word: PATH
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Possible second word: full
-craig

"You can never have too many knives" -- Logan Nine Fingers
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

And I'll chip in one word as well - "Use"

Now push them all onto a stack and then read :D
naren6876
Participant
Posts: 233
Joined: Mon Feb 07, 2005 7:19 pm

Post 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.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post 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.
-craig

"You can never have too many knives" -- Logan Nine Fingers
naren6876
Participant
Posts: 233
Joined: Mon Feb 07, 2005 7:19 pm

Post 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.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post 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.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post 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.
-craig

"You can never have too many knives" -- Logan Nine Fingers
naren6876
Participant
Posts: 233
Joined: Mon Feb 07, 2005 7:19 pm

Post 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.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post 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.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply