Execute command activity stage

Jayakannan · Post by **Jayakannan** » Fri May 28, 2010 5:38 am

Hi,

DataStage version 7.1

In my sequencer job design i am using Execute Command Activity Stage to invoke a Shellcript. I need to pass the parameters in that stage.

When i am trying to pass the Environment variables or user defined variables as parameter it is not getting passed to the Shellscript.

If i hard code the parameter value then it is getting passed to the Shellscript.

Is there any specific way to pass the Environment variables or user defined variables in Execute Command Activity Stage (DS v7.1)???

Regards,
Kannan

ArndW · Post by **ArndW** » Fri May 28, 2010 5:49 am

You will need to pass your job parameters in the form #ParameterName# to your external command.

Jayakannan · Post by **Jayakannan** » Fri May 28, 2010 5:57 am

I have passed the environment variable as #$parameter# and user defined variable as #parameter#. But its not working.

ajay.vaidyanathan · Post by **ajay.vaidyanathan** » Fri May 28, 2010 6:12 am

Hi,

In the Execute Command Stage, there will be two tabs. In the TOP one defined your shell (ksh,...) and the bottom mention your script whatever you are trying to call (xyz.sh,...)... Is this the way you are calling your script in your Execute Command Stage... ???

If this is not the way you are calling it, then it will not get the parameters...

Jayakannan · Post by **Jayakannan** » Fri May 28, 2010 6:18 am

There are 2 tabs. First one is Command tab where i have mentioned shellscript name (abc.sh) and second one is Parameters tab where i have mentioned the parameters which needs to be passed to the script.

Regards,
Kannan

chulett · Post by **chulett** » Fri May 28, 2010 6:19 am

And there's no need to pass environment variables to it as they are already accessible to it, being part of the environment and all.

ajay.vaidyanathan · Post by **ajay.vaidyanathan** » Fri May 28, 2010 6:33 am

Jayakannan,

The first tab (COMMAND) is for specifying your shell alone (ksh...)
In the second tab (PARAMETERS) you need to specify your script name with the parameter values passed to it.

chulett · Post by **chulett** » Fri May 28, 2010 6:43 am

No, you only "need" to do it that way if the path to your script/command is parametrised as well. What they've said that they are doing should be working fine.

You need to tell us what "not working" means - that statement by itself means nothing. Show us your exact input and output, log entries, etc so we have some clue about what you are doing and what you are seeing.

If no joy comes of this, contact your official support provider and see if it is a 7.1 issue, which is a... pretty darn version old nowadays.