![]() ![]() SAS justreleased a new Companion for Windows which is thorough, detailed, anduseful. A lot of the Mac-specific stuff is poorly documented.A handful of bug fixes (in the form of replacement executable files) have been made available on the Usage Notes CDs since the SAS 6.10 for the Mac was released. This means that bugson the Mac side take longer to get fixed, and-at least in version6.10-there are a fair number of bugs resulting from the fact that it's the first time it's been done. The first version ever was 6.10, there was no 6.11, and 6.12is forthcoming but will come out later than the PC version (my best guesswould be May '97 the PC version is already out). SAS does not develop SAS on the Mac as quickly as SAS on otherplatforms.For the handful of revised executables SAS has released as bug fixes, installation simply consists of dropping the file into the folder and having it replace the old file. The folder structure is straightforward, and I've never had a Mac refuse to run SAS because it failed to find a file. If you like knowing what your computer is doing and which files are where, the Mac is much easier to figure out.For example, you can set up SAS on the Mac so that double-clicking on a SAS data set opens that data set under PROC INSIGHT, if that's how you like to access your data. For each file type, you can control what happens if you tell SAS to open the file. SAS on the Mac can be customized in some interesting ways.On two different 486 machines (neither with as much memory as my Mac, one running OS/2 and the other running NT 4.0), the job failed to run, probably because of memory restrictions. On my Mac (a 7200/90, 40MB of memory), it took about 45 minutes. I did a little testingof a job I had running PROC MIXED on the Convex, this job took about 40CPU minutes (about 1 hour 20 minutes real time). ![]() In my (admittedly limited) experience, the Mac tends to be prettystable and reasonably powerful as a SAS machine. ![]() In contrast, as of version 6.12, Windows and OS/2 SAS does not read Mac/Unix data sets, and Unix SAS does not read Windows or OS/2 data sets. In addition, under version 6.12, the Mac will has an option in the LIBNAME statement permitting you to read and write Windows and OS/2 SAS data sets without needing a transport file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |