Date:         Wed, 14 Jul 2010 06:50:12 -0500
Reply-To:     "Data _null_;" <iebupdte@GMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Data _null_;" <iebupdte@GMAIL.COM>
Subject:      Re: x "path\app.exe" vs x "start app.exe"
Comments: To: Ya Huang <ya.huang@amylin.com>
In-Reply-To:  <201007132226.o6DHIoxW008369@willow.cc.uga.edu>
Content-Type: text/plain; charset=ISO-8859-1

Perhaps SYSTASK or INFILE PIPE would be better.  I "never" use X.
Sounds like a job for SYSTASK, but PIPE will also work.  Depends on
the command and how the output is produced and used.

systask command 'start notepad.exe' nowait;


/* This data step runs the entire time the application is running
which for NOTEPAD may not be desireable*/
data _null_;
   command = 'start notepad.exe test.sas';
   infile dummy pipe filevar=command;
   input;
   stop;
   run;

I would be good to know more the application your are starting.


On 7/13/10, Ya Huang <ya.huang@amylin.com> wrote:
> Hi there,
>
> I need to run some apps with x command. I have two ways to
> run it:
>
> 1.
> options xsync xwait;
> x """&apppath\app.exe"" /swiths ""&outpath\filename""";
>
> 2.
> options xsync xwait;
> x "start app.exe / ""outpath\filename""";
>
> For 1., I have to specify the apppath, which is not always in the
> same place.
> For 2., advantage is that I don't have to specify the apppath, windows
> can find the app.exe automatically. disadvantage is the DOS window
> won't close. I can't use noxsync and noxwait before the x command.
>
> I would prefer start method, if there is a way to close the dos window.
> I tried x "exit"; and failed.
>
> Thanks
>
> Ya
>