Michael Raithel wrote: > > Dear SAS-L-ers, > > In replying to Peetie Wheatstraws question on reading remote SAS data sets > without SAS/Connect, the amazingly prolific Peter Crawford posted, in part, > the following: > > <<Peter's entire posting can be found beneath the Sig line>> > > > ................ The only other alternatives I can think of, > > require you to be able to address the unix file system > > directly from the windows file system. > > - probably as rare as using the v6 library engine in v8 ;-) > > > > Peetie, just expounding upon Peter's comment: Here are SAS Mecca, our > clever systems engineers have set it up so that we may address the "unix > file system directly from the windows file system." They use software > called "NFS". Using NFS, we map a letter drive to our root directory on a > Unix server in Windows Explorer by clicking on <Tools> and then <Map Network > Drive>. After the drive is mapped, we may traverse our Unix directories as > if they were Windows directories. Our Windows SAS 8.2 programs can see the > Unix SAS data sets as long as we LIBNAME them correctly. Windows SAS > determines that the data sets are in a "foreign" format (Unix SAS data sets) > and uses CEDA engines as it sucks the data from the Unix SAS data sets, > across the network, and into PC SAS for processing. > > We have our Linux servers mapped to our Windows network via a product called > "Samba". So, if you were sitting beside me, here at SAS Mecca, and I were > navigating through "The Entire Network" in Windows Explorer, we would come > across the Linux servers. If I double-click on a Linux directory (in > Windows Explorer) and then double-click on a SAS data set, Windows SAS is > invoked on my desktop, and the Linux SAS data set is opened by CEDA engines > and has its observations sucked across the network and into my PC SAS > session. > > So, to make a long story endless: You should probably check with your > friendly systems engineers and determine whether your organization has > either NFS or Samba. If so, then you may be able to map your Unix file > system directly from the Windows file system as Peter suggested. > > Peetie, best of luck to you in your quest to process Unix SAS data on your > desktop! > > I hope that this suggestion proves helpful now, and in the future! > > Of course, all of these opinions and insights are my own, and do not reflect > those of my organization or my associates. All SAS code and/or methodologies > specified in this posting are for illustrative purposes only and no warranty > is stated or implied as to their accuracy or applicability. People deciding > to use information in this posting do so at their own risk. > > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Michael A. Raithel > "The man who wrote the book on performance" > E-mail: MichaelRaithel@westat.com > Author: Tuning SAS Applications in the MVS Environment > http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=55231 > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > No trumpets sound when the important decisions of our life > are made. Destiny is made known silently. - Agnes DeMille > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > <<Peter's entire original posting>> > > > two possibilities may exist > > If you use the v6 libname engine on unix, the SAS System > > Viewer "network open" option, can open the datasets if you > > give enough server, user and path details. Assuming the more > > normal scenario, you should be able to (binary) ftp the > > datasets to your windows environment, and then read them > > directly in SAS. The only other alternatives I can think of, > > require you to be able to address the unix file system > > directly from the windows file system. > > - probably as rare as using the v6 library engine in v8 ;-) > >

We also use the process you describe. I am planning to pursue the reverse in our shop: make unix aware of windoze file systems. This is better for me because I do the bulk of my processing on the unix side and periodically have to access sasfiles on the windoze side. Anyone have this functionality in place that is willing to share some insight into what is being used, what works and what doesn't?