Execute Unix commands in datastage

[Magesh_bala]

Hi All,

How to execute unix commands in Datasatge.

path/ Touch File.txt
path/ rm File.txt

Is this commands will work from datastage?

[sachin1]

where you want to execute these commands, i mean before/afte job subroutine or in basic code.

[hamzaqk]

specify the command in the job properties tab (either in the before or after job ) Select Execsh in the drop down list and infront of it specify the command you want to execute

[Magesh_bala]

I have to use this in sequence job, I belive only shell scripts can be executed in the before/after execute job execsh, Is there any other option to execute the unix commands directly in datastage.

[ray.wurlod]

In job sequences you have the Execute Command activity available. Does that name suggest its possible purpose?

[Magesh_bala]

In Execute command we cant execute the shell script commands, We can call only the shell scripts files.

[balajisr]

In Execute command we cant execute the shell script commands, We can call only the shell scripts files.

No.Did you try using Execute command in the first place as suggested by Ray?

[ray.wurlod]

In Execute command we cant execute the shell script commands, We can call only the shell scripts files.

Not true.

If you can prove that your assertion is true I would be interested in seeing the proof.

I execute individual commands through Execute Command activity quite frequently.

[chulett]

Both the before/after ExecSH commands and the Execute Command stage can execute operating system commands directly as well as scripts.

[Magesh_bala]

Hi Ray, Thanks for your reply. Whe we execute the command
touch opt/Ascential/Data/Samplefile.txt --> It works

But when we use the Parameter

touch #path#samplefile.txt --> Its not working in Execute command stage

Can you please suggest how to use the parameter in execute command stage.

Thanks and Regards
N.Magesh

[ray.wurlod]

Where is the parameter coming from?

You can not use parameters in the Command field in the Execute Command stage. You can only use them in the Parameters field.

Therefore the solution that you require for this particular problem (assuming that there exists a job sequence parameter called "path" and that its value includes a terminating pathname delimiter character ("/" on UNIX)) is as follows:

Command: touch
Parameters: #path#samplefile.txt

[Magesh_bala]

Hi Ray, Can you please tell me the solution.

[ray.wurlod]

I did. A very complete solution.

Please purchase a premium memberhip that will allow you to read it, or have your employer purchase it.

Premium membership is one of the ways that the hosting and bandwidth costs of DSXchange are defrayed. By taking premium membership you are not only getting the benefits thereof but you are also helping to keep DSXchange alive. At less than 30c (Rs12) per day it is not expensive.

[manuel.gomez]

Where is the parameter coming from?

You can not use parameters in the Command field in the Execute Command stage. You can only use them in the Parameters field.

Therefore the solution that you require for this particular problem (assuming that there exists a job sequence parameter called "path" and that its value includes a terminating pathname delimiter character ("/" on UNIX)) is as follows:

Command: touch
Parameters: #path#samplefile.txt

What if the command 'touch' requires the complete path to be executed?
For example, /pathforcommands/touch

How can I tell Datastege the path where the command is in order to be executed?

Thanks a lot

[chulett]

Simply put your shell of choice in the command prompt, say "ksh", and then the complete command with whatever parameters you need in the parameter prompt.