Converting a routine from Linux to work on NT

crouse · Post by **crouse** » Tue Jan 13, 2009 12:34 pm

I have a DS routine that works just great on Linux/Unix.
Trying to convert to work on an NT server.
We have installed MKS Toolkit on the the NT server.
The routine issues Unix commands and then does stuff with RT_LOG files...
The very first command is giving me fits.
The command is "find . -name "RT_LOG*"" (minus the first and last double quotes).
The asterisk I believe is messing it up, but I need the asterisk and am struggling with why the command is being messed up via the dsexecute command.

Code: Select all

      UnixCmd = ' find . -name    "RT_LOG*"'
      Call DSLogWarn("UnixCmd =":UnixCmd ,'AAA')
      Call DSExecute("NT", UnixCmd, ScreenOutput, SystemReturnCode)
      Call DSLogWarn("ScreenOutput =":ScreenOutput,'AAA')

The output from testing the routine is:

Test completed.
 
DSLogWarn called from : AAA
Message to be logged is...
> UnixCmd = find . -name    "RT_LOG*"
DSLogWarn called from : AAA
Message to be logged is...
> ScreenOutput =Unknown option "RT_LOG10"
> Usage: find directory ... expression
> 

Result = Unknown option "RT_LOG10"
Usage: find directory ... expression

I've tried a million (ok, 10 or more) different things like escaping the spaces, or escaping the asterisk, but can't get it to work.
The command will be parsed and executed successfully without the asterisk, but I need the asterisk.

If I run the commands from the command line they work perfectly, just not via DS.

I've checked to make sure env variables are the same between my user session command lines and the DS env variables, like PATH and such.

Any ideas?

chulett · Post by **chulett** » Tue Jan 13, 2009 12:41 pm

Perhaps silly, but what happens if you say "UNIX" rather than "NT" for the O/S? There is a DOS find command, by the way, perhaps it is using that rather than the MKS version. Or just make sure the MKS directories are first in the PATH... are they?

crouse · Post by **crouse** » Tue Jan 13, 2009 12:58 pm

Tried the UNIX instead of NT... DS says "that command is not supported on this platform"

Also did a "which find" command from the routine and it is using/finding the MKS find command.

And the env var PATH, as seen from DS within the routine is "Path=C:\PROGRA~1\MKSTOO~1\bin;C:\PROGRA~1\MKSTOO~1\bin\X11;C:\PROGRA~1\MKSTOO~1\mksnt;c:\orant9i\jre\1.4.2\bin\..."

I also tried the whole thing with cygwin instead of MKS Toolkit and am getting the exact same issue.

So, it appears the DSExecute command is horking up the command I'm sending it.

I'm sure some combination of escapes or quotes or spaces will work, just haven't found it yet.

Is there an escape character for DOS? (like backslash in Unix)

chulett · Post by **chulett** » Tue Jan 13, 2009 1:05 pm

crouse wrote:Is there an escape character for DOS? (like backslash in Unix)

From what I recall, it's the "^" (what we used to call the "hat" or "tee-pee" but now is some kind of vegetable) but I don't think that's going to help as you really do want the metacharacter and not the literal value.

crouse · Post by **crouse** » Tue Jan 13, 2009 1:12 pm

you're right on both accounts... it is a ^ and it doesn't help.

I can't even reproduce that error message from the command line. If I could format a command to give me the error then I could maybe start there.

narasimha · Post by **narasimha** » Tue Jan 13, 2009 2:18 pm

My 2 cents...

Try giving a DOS command in the routine.
Something like

Code: Select all

dir /B RT_LOG*

This should find all the files starting with RT_LOG in the current directory

crouse · Post by **crouse** » Tue Jan 13, 2009 2:50 pm

That'd work, but I have a whole boat load of other UNIX commands chained to this one for sizing and sorting...

Going to try putting the UNIX commands in a script, then execute the script. Wish me luck.

Also, you need to update you bill rate. The was worth more than 2 cents.

And get back to work.

-Craig

ray.wurlod · Post by **ray.wurlod** » Tue Jan 13, 2009 2:55 pm

Don't you need single quotes around a -name argument to find when the argument contains wildcards? Also don't you have to do something with what's found (for example -exec or -print)?

Code: Select all

find . -name 'RT_LOG*' -print

crouse · Post by **crouse** » Tue Jan 13, 2009 3:02 pm

UNIX usually requires double quotes around the file name if it contains wildcards or other stuff for an expression. I've tried double and single quotes, and no quotes, with same error response. The -print is a default... you leave it off and it's implied. And I tried including it and same result. Backing off to a script now.

narasimha · Post by **narasimha** » Tue Jan 13, 2009 3:53 pm

Craig,

Best of luck on your conversions and set-ups.
And get back soon