|
On 28 Jun 02 03:45:07 GMT, Philip_Crane@WORKCOVER.VIC.GOV.AU wrote:
>The following command calls and correctly executes my shell script (HP
>unix)
>
> 39 %sysexec /home/regulation/cranp1/sasarch.sh;
>
>But when I try to pass some parameters with it; like this
>
> 40 %sysexec "/home/regulation/cranp1/sasarch.sh &path &file";
>
>it does not. It appears as though unix treats the whole string as the name
>of an object that it tries to execute and then complains it cannot find it.
>
>Can someone please advise on how to nominate a shell script to run and pass
>parameters to it.
Generally, I'd use an 'X' command, like this:
X "unixcmd &parm1 &parm2" ;
I've never used %sysexec macro, so can't comment on what's wrong with
your approach, but this way should work fine.
--
Ace in Basel - bruce dot rogers at roche dot com
| 
