| Date: | Tue, 5 Aug 2003 22:00:29 +0000 |
| Reply-To: | Puddin' Man <pudding_man@POSTMARK.NET> |
| Sender: | "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU> |
| From: | Puddin' Man <pudding_man@POSTMARK.NET> |
| Subject: | Re: Access remote SAS lib. w/o CONNECT? |
|
| Content-Type: | text/plain; charset="iso-8859-1" |
|---|
Jack Hamilton wrote:
> "Peetie Wheatstraw" <peetie_wheatstraw@LYCOS.COM> wrote:
>
> >Michael Raithel wrote:
> >> > ................ 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.
> >
> >True or false: 'filename xx ftp ...' does this very nicely
> >for flat files. Is it possible that we don't have 'libname
> >xx ftp' primarily so SI can sell more 'connect' licenses?
>
> In this case I think it's a technical restriction. Native SAS
> libraries require direct (random) access, and FTP is sequential access
> only.
Native SAS libraries require direct (random) access
with use of the *native* SAS engine, fo' sho'.
If an FTP engine for LIBNAME existed, I think it would be "A
Whole 'Nother Kettle O' Beans". I'm not aware of any
material reasons why it couldn't do sequential access much
like the old TAPE engines, as mentioned by Kevin. Of course
it'd be subject to the same restrictions: NOBS= , POINT=,
etc wouldn't work.
Hells Bells, if they made it a READONLY engine, it'd be lots
better'n what we (don't) got now. <g>
Skoal,
Puddin'
*******************************************************
*** Puddin' Man *** Pudding_Man@postmark.net *****
*******************************************************;
"WAR IS PEACE"
"FREEDOM IS SLAVERY"
"IGNORANCE IS STRENGTH"
-from "1984", Geo. Orwell
"Black is White!"
"Day is Night!"
"The USA, in 2003, bears no semblance whatsoever to
Japan and/or Germany around 1939-1940!"
-MadMan
|