Date:         Thu, 13 Mar 2003 18:51:33 -0500
Reply-To:     Huck <huck@FINN.NOSPAM.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Huck <huck@FINN.NOSPAM.COM>
Organization: Posted via Supernews, http://www.supernews.com
Subject:      Re: exec win2k resource utilities
Content-Type: text/plain; charset=us-ascii

On 13 Mar 03 22:10:13 GMT, cassell.david@EPAMAIL.EPA.GOV (David L.
Cassell) wrote:

>fernd alois <ferndalois@HOTMAIL.COM> wrote:
>> I use some win2k resourcekit utilities on the sas win2k server to get
>some
>> knowledge about the processes , used memory ea
>> This goes by the mechanism
>>    filename  test pipe "pslist.exe SAS" ;
>>    data _null_ ;
>>    infile .....
>>
>> With some resource kit utilities utilities I get no answer ; I think
>this is
>> because these  utilities use stderr    and not stdout
>> Is there a way to read  the stderr output from the pipe by using
>> the unix symbols   > & 2 or by another way ?
>
>As a SAS-L expert pointed out, this is a shell issue, and win32 doesn't
>have the sort of shells available in unix.
>
>Instead, you could use a language like Perl or Python to run the
>utility,
>grab the stderr, and then hold that information so that you could use
>FILENAME to pipe that to SAS.
>
>HTH,
>David

there is a discussion going on over in comp.lang.perl.moderated about
this, the thread titled "Win32: Ways of redirecting STDOUT and STDERR
of external pgm at the same time?"

one repsonder "Louis Erickson" suggested

>$rc = system("program > foo.txt 2>&1");

>You'll have to make sure buffering doesn't bite you there, but that
>does what you want.  It looks just like how you'd do it under Unix.
>Works in Windows 2000 and anything newer, and probably in NT4.  Can't
>speak for 98/ME, etc.  I suspect they don't work.

i have not tried this at all yet