Ch. 2: Getting Your Data into SAS. At OSEDA we try to ease the burden of converting data by having data already in SAS data set format in the archive. But it is still important that you know how to convert your own.
PowerPoint Slideshow about 'Ch. 2: Getting Your Data into SAS' - bryce
An Image/Link below is provided (as is) to download presentation
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
An annoying “gotcha” is the default of truncating input lines at 256 bytes.
Easy to circumvent if you know to code lrecl=2000 (or some large value) as option on the infile statement. Sets up the buffer size - it does not mean the records have to really be that long. They just can’t be longer.
Starting with v7 you can code:data ‘c:\temp\boone_county’;
Before v7 this was heresy. You always had to define the data library separately and use a 2-level name to reference a data set within that directory:libname tempsas ‘c:\temp’; data tempsas.boone_county;