|
See Garth Helf's paper ("Extreme Web Access: What to Do When FILENAME URL
Is Not Enough") from this week's SUGI conference.
http://www2.sas.com/proceedings/sugi30/100-30.pdf
On Thu, 14 Apr 2005 15:17:13 -0700, David L. Cassell
<cassell.david@EPAMAIL.EPA.GOV> wrote:
>Matt Pettis <matt.pettis@THOMSON.COM> sagely replied:
>> In fact, here is an example:
>> ----------------------------
>> filename test url
>> 'http://ichart.finance.yahoo.com/table.csv?
>> s=IBM&d=3&e=11&f=2005&g=d&a=0&b=2&c=1962&ignore=.csv'
>> proxy='http://<your_proxy_name>:<proxyport>';
>> data work;
>> infile test dsd dlm=',' firstobs=2;
>> input date:date9. open high low close volume close_adj;
>> format date date.;
>> run;
>> ----------------------------
>>
>> Two caveats:
>>
>> You may or may not need the proxy= option on the filename. I'd start
>by
>> leaving it off -- add it with the correct proxy info if you get a
>'winsock
>> 10060' error.
>>
>> You may get an error that referrs to 'httpd'. In that case, look at
>the
>> helpfile at: http://support.sas.com/techsup/unotes/V6/C/C065.html
>
>Both caveats emphasize the point I have made before. The SAS FILENAME
>engines are just not robust enough for a lot of uses. The URL engine
>really needs some manner of error-checking and error-handling,
>particularly
>when dealing with something as squirrely as scraping webpages.
>
>David
>--
>David Cassell, CSC
>Cassell.David@epa.gov
>Senior computing specialist
>mathematical statistician
| 
