reading ssd01 files
in [SAS]
|
From: Michael Raithel on 13 Nov 2009 08:13 Dear SAS-L-ers, Steve Wickham posted the following interesting question: > > I'm finally making the transition from v6.12 (Mac OS9/10.4) to v9.2 > (XP/Parallels 4/Mac OS10.6.2). > As a result I'm trying to read a bunch of data files with the .ssd01 > extension. What should work is: > > libname oldlib v6 'folder path'; > > but for some reason, SAS doesn't see the files. Files with a .sd2 > extension can be read and created > with the libname statement. JMP can open the .ssd01 files without > problem, so it doesn't appear that > they're corrupted. Any ideas how to force SAS to see these relicts of > the stone age? > Steve, wow; those old SAS data sets of yours probably have fond memories of listening to A Flock of Seagulls, Prince, the Cars, the Eurythmics, Men at Work, The Thompson Twins, the Smiths, the Talking Heads, Duran Duran, the Police, Tears for Fears, Journey, and Cyldi Lauper; to name a few:-) All nostalgia aside, it looks like you are doing everything right, and yet are still in the weeds. What is a bit odd to me is that .ssd01 is the SAS V6 extension for UNIX SAS data sets, while .sd2 is that for SAS V6 Windows SAS data sets. Because you are on a MAC, I can only assume that the V6 SAS file extensions is a bit different than what I would normally expect and that a mix of .ssd01 and .sd2 is common for that platform, right? If not, perhaps you have some UNIX SAS data sets mixed in with your MAC SAS data sets and that is causing SAS 9.2 to belch loudly in an uncouth, uncivilized manner. If you do not get a SAS-L smarty to give you a drop-dead clean answer on this problem, I have a workaround. That workaround is: Under SAS 6.12, use PROC CPORT to create a SAS transport data set. Then use PROC CIMPORT on your SAS 9.2 platform to import the SAS data set into a new directory on your new machine. You will have effectively migrated the data from one version of SAS to another and should not have any problem moving forward from there. A thought! Steve, best of luck in all of your SAS endeavors! 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(a)westat.com Author: Tuning SAS Applications in the MVS Environment Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=58172 Author: The Complete Guide to SAS Indexes http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=60409 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ if you fall I will catch you--I'll be waiting time after time - Cyndi Lauper, Time After Time +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
From: Mark Miller on 13 Nov 2009 16:06 The standard SAS format for SAS 6.12 on Mac is indeed .ssd01; same as sun SPARC. SAS v6.12 for Mac is actually for PowerMac which runs on Motorola 68K chips (big endian) It runs on some versions OS 10 under classic mac emulation. I don't believe it runs at all with Mac/Intel machines because the emulator is absent. If you do not still have SAS 6.12 running on the older machine, then this might be a good occasion to invest in a copy of Stat/Transfer if you can swing it. Tthat's what I would use ..YMMV. ....Mark Miller On Fri, Nov 13, 2009 at 8:13 AM, Michael Raithel <michaelraithel(a)westat.com>wrote: > Dear SAS-L-ers, > > Steve Wickham posted the following interesting question: > > > > > I'm finally making the transition from v6.12 (Mac OS9/10.4) to v9.2 > > (XP/Parallels 4/Mac OS10.6.2). > > As a result I'm trying to read a bunch of data files with the .ssd01 > > extension. What should work is: > > > > libname oldlib v6 'folder path'; > > > > but for some reason, SAS doesn't see the files. Files with a .sd2 > > extension can be read and created > > with the libname statement. JMP can open the .ssd01 files without > > problem, so it doesn't appear that > > they're corrupted. Any ideas how to force SAS to see these relicts of > > the stone age? > > > Steve, wow; those old SAS data sets of yours probably have fond memories of > listening to A Flock of Seagulls, Prince, the Cars, the Eurythmics, Men at > Work, The Thompson Twins, the Smiths, the Talking Heads, Duran Duran, the > Police, Tears for Fears, Journey, and Cyldi Lauper; to name a few:-) > > All nostalgia aside, it looks like you are doing everything right, and yet > are still in the weeds. What is a bit odd to me is that .ssd01 is the SAS > V6 extension for UNIX SAS data sets, while .sd2 is that for SAS V6 Windows > SAS data sets. Because you are on a MAC, I can only assume that the V6 SAS > file extensions is a bit different than what I would normally expect and > that a mix of .ssd01 and .sd2 is common for that platform, right? If not, > perhaps you have some UNIX SAS data sets mixed in with your MAC SAS data > sets and that is causing SAS 9.2 to belch loudly in an uncouth, uncivilized > manner. > > If you do not get a SAS-L smarty to give you a drop-dead clean answer on > this problem, I have a workaround. That workaround is: > > Under SAS 6.12, use PROC CPORT to create a SAS transport data set. Then > use PROC CIMPORT on your SAS 9.2 platform to import the SAS data set into a > new directory on your new machine. You will have effectively migrated the > data from one version of SAS to another and should not have any problem > moving forward from there. A thought! > > Steve, best of luck in all of your SAS endeavors! > > > 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(a)westat.com > > Author: Tuning SAS Applications in the MVS Environment > > Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second > Edition > http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=58172 > > Author: The Complete Guide to SAS Indexes > http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=60409 > > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > if you fall I will catch you--I'll be waiting > time after time - Cyndi Lauper, Time After Time > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >
From: Michael Raithel on 14 Nov 2009 12:16 Dear SAS-L-ers, Both Steve, the OP, and I heard from a little birdie regarding this posting. I am pasting the birdie's contribution here in case it is helpful to another SAS-L-er: Hello Michael and Steve, Thanks for the memories. UNIX and Mac datasets in version 6 shared a common disk format based on the "family". The digit in the dataset extension indicates the family and there were four possible families: ssd01 - big endian, 32 bit ssd02 - little endian, 32 bit ssd03 - big endian, 64 bit ssd04 - little endian, 64 bit Big endian systems are risc processors like Sun's SPARC, PowerPC and HP9000. Little endian systems included the X86 family and the DEC Alpha chip. All of the 6.12 systems were 32 bit, except for Alpha. You would not be able to read a dataset from another family. So, getting to Steve's problem. Proc CPORT/Import will certainly work if his Mac SAS 6.12 is still working. It might be possible to read the 6.12 mac dataset on a Solaris, HP or AIX 8.2 or 9.x system using the v6 engine. Good luck to you, Best of luck to all of you in your SAS endeavors! Take Care! ----MMMMIIIIKKKKEEEE (aka Michael A. Raithel)
From: Peter on 14 Nov 2009 13:29 On Nov 13, 9:06 pm, mdhmil...(a)GMAIL.COM (Mark Miller) wrote: > The standard SAS format for SAS 6.12 on Mac is indeed .ssd01; same as sun > SPARC. > > SAS v6.12 for Mac is actually for PowerMac which runs on Motorola 68K chips > (big endian) > It runs on some versions OS 10 under classic mac emulation. > I don't believe it runs at all with Mac/Intel machines because the emulator > is absent. > > If you do not still have SAS 6.12 running on the older machine, then this > might > be a good occasion to invest in a copy of Stat/Transfer if you can swing it. > Tthat's what I would use ..YMMV. > > ...Mark Miller > > On Fri, Nov 13, 2009 at 8:13 AM, Michael Raithel > <michaelrait...(a)westat.com>wrote: > > > > > Dear SAS-L-ers, > > > Steve Wickham posted the following interesting question: > > > > I'm finally making the transition from v6.12 (Mac OS9/10.4) to v9.2 > > > (XP/Parallels 4/Mac OS10.6.2). > > > As a result I'm trying to read a bunch of data files with the .ssd01 > > > extension. What should work is: > > > > libname oldlib v6 'folder path'; > > > > but for some reason, SAS doesn't see the files. Files with a .sd2 > > > extension can be read and created > > > with the libname statement. JMP can open the .ssd01files without > > > problem, so it doesn't appear that > > > they're corrupted. Any ideas how to force SAS to see these relicts of > > > the stone age? > > > Steve, wow; those old SAS data sets of yours probably have fond memories of > > listening to A Flock of Seagulls, Prince, the Cars, the Eurythmics, Men at > > Work, The Thompson Twins, the Smiths, the Talking Heads, Duran Duran, the > > Police, Tears for Fears, Journey, and Cyldi Lauper; to name a few:-) > > > All nostalgia aside, it looks like you are doing everything right, and yet > > are still in the weeds. What is a bit odd to me is that .ssd01is the SAS > > V6 extension for UNIX SAS data sets, while .sd2 is that for SAS V6 Windows > > SAS data sets. Because you are on a MAC, I can only assume that the V6 SAS > > file extensions is a bit different than what I would normally expect and > > that a mix of .ssd01and .sd2 is common for that platform, right? If not, > > perhaps you have some UNIX SAS data sets mixed in with your MAC SAS data > > sets and that is causing SAS 9.2 to belch loudly in an uncouth, uncivilized > > manner. > > > If you do not get a SAS-L smarty to give you a drop-dead clean answer on > > this problem, I have a workaround. That workaround is: > > > Under SAS 6.12, use PROC CPORT to create a SAS transport data set. Then > > use PROC CIMPORT on your SAS 9.2 platform to import the SAS data set into a > > new directory on your new machine. You will have effectively migrated the > > data from one version of SAS to another and should not have any problem > > moving forward from there. A thought! > > > Steve, best of luck in all of your SAS endeavors! > > > 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: MichaelRait...(a)westat.com > > > Author: Tuning SAS Applications in the MVS Environment > > > Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second > > Edition > >http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=58172 > > > Author: The Complete Guide to SAS Indexes > >http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=60409 > > > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > if you fall I will catch you--I'll be waiting > > time after time - Cyndi Lauper, Time After Time > > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++- Hide quoted text - > > - Show quoted text - try the sas system viewer That had internals that SAS6 referred to as sasSFio (a sas library engine, which could even read over ftp) When sas8 was introduced CEDA took the place of sassfio. That might help Good Luck PeterC
From: Arthur Tabachneck on 14 Nov 2009 13:51
MMMMIIIIKKKKEEEE, I've never worked with JMP but, since the OP mentioned that he can open the files in JMP, can't they be saved there as JMP files or SAS transport files, and then imported into his new version of SAS? Art ------- On Sat, 14 Nov 2009 12:16:27 -0500, Michael Raithel <michaelraithel(a)WESTAT.COM> wrote: >Dear SAS-L-ers, > >Both Steve, the OP, and I heard from a little birdie regarding this posting. I am pasting the birdie's contribution here in case it is helpful to another SAS-L-er: > > >Hello Michael and Steve, > >Thanks for the memories. > >UNIX and Mac datasets in version 6 shared a common disk format based on the "family". The digit in the dataset extension indicates the family and there were four possible families: > >ssd01 - big endian, 32 bit >ssd02 - little endian, 32 bit >ssd03 - big endian, 64 bit >ssd04 - little endian, 64 bit > >Big endian systems are risc processors like Sun's SPARC, PowerPC and HP9000. Little endian systems included the X86 family and the DEC Alpha chip. All of the 6.12 systems were 32 bit, except for Alpha. You would not be able to read a dataset from another family. > >So, getting to Steve's problem. Proc CPORT/Import will certainly work if his Mac SAS 6.12 is still working. It might be possible to read the 6.12 mac dataset on a Solaris, HP or AIX 8.2 or 9.x system using the v6 engine. > >Good luck to you, > > > >Best of luck to all of you in your SAS endeavors! > > >Take Care! > >----MMMMIIIIKKKKEEEE >(aka Michael A. Raithel) |