Problem With ExecCommand Activity

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
sturdyvel
Participant
Posts: 9
Joined: Fri Aug 18, 2006 12:05 am

Problem With ExecCommand Activity

Post by sturdyvel »

Hi,

The scenario is, i am calling a shell script using Exec Command Activity Stage in Job Sequencer.Currently, i am working in development environment.When moving to the production environment the path of the shell will be changed.So, we are giving environmental variables in Admin level and we are using the same for the path and other things in all other stgaes...but we are not able to do with Exec Command Stage ... how can i give the path details using environmental variables in Exec Command Activity Stage

Rgds
Kadir
meena
Participant
Posts: 430
Joined: Tue Sep 13, 2005 12:17 pm

Post by meena »

Hi,
Check whether you script exists in the production server or not. And post the error or warning what you are getting.And can you be clear to this sentence:
So, we are giving environmental variables in Admin level and we are using the same for the path and other things in all other stgaes
I want to know what are the "other things in all other stages".
kris007
Charter Member
Charter Member
Posts: 1102
Joined: Tue Jan 24, 2006 5:38 pm
Location: Riverside, RI

Post by kris007 »

Passing your path as a parameter should solve the problem. Which version of DataStage are you on?
Kris

Where's the "Any" key?-Homer Simpson
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Read the parameter in the JobSequence that useses the CommandActivity by assigining the default value as $PROJDEF. And now you can pass the parameter to the commandActivity stage from the JobSequence.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Xpert
Premium Member
Premium Member
Posts: 85
Joined: Wed Mar 01, 2006 7:17 am

Post by Xpert »

Hi,

As earlier replied message, give ur path as parameter and pass to the Execute Command activity in Job sequence, it will work fine.
With regards,
Xpert
Post Reply