reading ssd01 files
in [SAS]
|
From: Peter Crawford on 15 Nov 2009 12:21 try the sas system viewer That had internals SAS6 referred to as, sasSFio (a sas library engine, which could even read over ftp). When sas8 was introduced, CEDA provided facilities that took the place of sassfio. CEDA might help Good Luck PeterC On Sat, 14 Nov 2009 13:51:14 -0500, Arthur Tabachneck <art297(a)NETSCAPE.NET> wrote: >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)
From: Michael Raithel on 16 Nov 2009 08:42 Dear SAS-L-ers, Art posted the following: > > 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, I knew you were BOUND to SPRING into action and JUMP right in on this thread, so I do not think it is a big LEAP of faith to say that the OP's HURDLEs might be resolved if he HOPS into using the much VAULTed JMP files. However, like you I do have any practical knowledge of JMP, so I can't JUMP to conclusions without further information from those who have:-) Art, 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 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Look before you leap. - Anonymous +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
From: Steve Wickham on 16 Nov 2009 09:51 Hi SAS-L'ers Thanks for the suggestions on how to read in v6 Mac files. I knew via JMP would work (either the individual files with the .ssd01 extension, or transport libraries with an .stx extension). SAS system viewer will allow me to read the files, but not save in .sas7bdat format, so not much help there. What I was hoping for was a subtle tweak to my libname statement that would allow me to do a multi-file find/replace to the program files, and bob's your uncle. Alas, that is not to be, for reasons no one can explain. Proc Cport/Cimport or Proc Copy does the job, if somewhat inelegantly. I have 6 months overlap in my v6/v9 licenses, so lots of time to transfer old files, but a nuisance all the same. Cheers, Steve Wickham -------------------------------------------------------------------- Dr. Stephen Wickham phone: +43 662 8044 5603 Organismic Biology fax: +43 662 8044 5698 University of Salzburg Hellbrunnerstr. 34 5020 Salzburg Austria email: steve.wickham(a)sbg.ac.at
From: Nathaniel Wooding on 16 Nov 2009 10:06 Steve There should be no issue with you V6 license. You should still be able to get a setinit for it and keep it functioning. Nat Wooding -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L(a)LISTSERV.UGA.EDU] On Behalf Of Steve Wickham Sent: Monday, November 16, 2009 9:52 AM To: SAS-L(a)LISTSERV.UGA.EDU Subject: Re: reading ssd01 files Hi SAS-L'ers Thanks for the suggestions on how to read in v6 Mac files. I knew via JMP would work (either the individual files with the .ssd01 extension, or transport libraries with an .stx extension). SAS system viewer will allow me to read the files, but not save in .sas7bdat format, so not much help there. What I was hoping for was a subtle tweak to my libname statement that would allow me to do a multi-file find/replace to the program files, and bob's your uncle. Alas, that is not to be, for reasons no one can explain. Proc Cport/Cimport or Proc Copy does the job, if somewhat inelegantly. I have 6 months overlap in my v6/v9 licenses, so lots of time to transfer old files, but a nuisance all the same. Cheers, Steve Wickham -------------------------------------------------------------------- Dr. Stephen Wickham phone: +43 662 8044 5603 Organismic Biology fax: +43 662 8044 5698 University of Salzburg Hellbrunnerstr. 34 5020 Salzburg Austria email: steve.wickham(a)sbg.ac.at CONFIDENTIALITY NOTICE: This electronic message contains information which may be legally confidential and or privileged and does not in any case represent a firm ENERGY COMMODITY bid or offer relating thereto which binds the sender without an additional express written confirmation to that effect. The information is intended solely for the individual or entity named above and access by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
From: augustine on 30 Nov 2009 11:30
On Nov 13, 11:41 am, steve.wick...(a)SBG.AC.AT (Steve Wickham) wrote: > Hello > > 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? > > Thanks, > > Steve Wickham Open in JMP and you can simply use the 'save as' option to produce a sas7dat file. I have just successfully converted 2 such files myself, both had been writtten by an rs6000 engine - you can read the originating engine using any hex editor to open the ssd01. |