Weird problem with command activity

[gaurang033]

Hi All,

I have a shell script which i am calling from command activity, the script gives desired output when i run from Shell but it behaves weird when i call it from command activity.

I debug the script and figure it out that there is a particualr part in script which bahevs unexpected when i call it from command acitivity..

Code: Select all

 name=$1
output=`ls $1`
echo $output

When i call this script from shell like follows it list all the file with same pattern.

Code: Select all

 sh findFiles.sh "aa*1" 

but when i call same script with command output with same parameter it gives following output

aa*1 not found

Now i am not able to understand why this is happening. Any suggestion ???

[gaurang033]

this is also not working.

Code: Select all

 echo $1

if i will call above script like as below, it will list all the files

Code: Select all

sh findFiles.sh "aa*1"

However if i call same script with same parameter from Execute command it prints only following line
aa*1

[Kirtikumar]

It might be the issue with relative directory. When running the comman, from which directory do you run it.

When calling from the DS, are you sending directory name along with the pattern? Add pwd command in the script and see what directory it prints.

[gaurang033]

no there is no problem with the path. i copy the command generated by sequence from log and run on shell and it gives output.

[pandeesh]

May i know how you are calling in Execute Command activity stage?

What you are giving in command and parameters?

[chulett]

no there is no problem with the path. i copy the command generated by sequence from log and run on shell and it gives output.

FYI - this doesn't really prove anything, you could still have a path issue in the job. The only way to avoid that is to use an absolute path in the stage.

To me it seems like the quotes are being stripped... escape them.

[mark1024]

Think about what the Shell is doing, "aa*1" the shell is trying to figure out what the star means, try putting a "aa\*" . I know in bash the special chars get processed if you don't put a slash in them.

[pandeesh]

Yes! Mark's Suggestion is appropriate!!