Oops, I lied. Previously I had tried using put _infile_ rather than list. put _infile_ appeared to hang as I stated previously, but using list I get an infinite list of lines that look like th following (only stopped by aborting the program). In the lines below (which may be screwed up by differeing fonts than the original output), the "0" values are all in column 2, and I have absolutely no idea where there are coming from. In the VB program that is sending data across the pipe, I verify the value that is being written to the pipe *immediately* before writing it. Furthermore, the VB progam hangs at this point and never writes any more lines to the pipe, so I have no idea how/why SAS seems to be getting all of these lines.

MACROGEN(SASPIPES): data _null_; MACROGEN(SASPIPES): infile SASIn lrecl=32767; MACROGEN(SASPIPES): input; MACROGEN(SASPIPES): list; MACROGEN(SASPIPES): run;

NOTE: The infile SASIN is: Named Pipe Access Device, PROCESS=\\.\pipe\SASIn,RECFM=V,LRECL=32767

RULE: ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0 1 0 2 0 3 0 4 0 5 0 6 0

----- Original Message ----- From: "Kevin Myers" <KevinMyers@AUSTIN.RR.COM> To: <SAS-L@LISTSERV.UGA.EDU> Sent: Friday, July 09, 2010 16:13 Subject: Re: SAS Communication with VB.Net Application Using Named Pipes

> Been there done that Tom. A simple data _null_ step such as the one that > you provided appears to hang waiting on input. No useful warnings or > error > messages. > > ----- Original Message ----- > From: "Tom Abernathy" <tom.abernathy@GMAIL.COM> > To: <SAS-L@LISTSERV.UGA.EDU> > Sent: Friday, July 09, 2010 16:02 > Subject: Re: SAS Communication with VB.Net Application Using Named Pipes > > >> Kevin - >> Try debugging with normal SAS statements and datasteps. >> Then if you can get it to work you can try to figure out the FOPEN, >> FREAD >> functions. >> >> FILENAME IN .... ; >> data _null_; >> infile in lrecl=32767; >> input; >> list; >> run; >> >> - Tom >> >