SAS Universal Viewer unable to read table ".ssd01"

[Dallain]

I want to read table sas having an ".ssd01" extension. When forcing extension ".sas7bdat" to ".ssd01" it answer : Unable to load it. the most common cause is associated index not found. Can you help me ?

Dallain    

[ballardw]

Why do you care what the extension is? If the original file is Sas7bdat that should be readable by the Universal Viewer.

SAS used an extension of SSD for SAS some SAS 6 files more than 25 years ago. i don't remember an SSD01 extension. If the original file had an SSD01 extension I might try changing the extension to SSD and see if that is readable.

If you actually have a SAS install you might also try creating a library in the location of the file with the option V6 option on the libname statement.

[Dallain]

I have yet tried to change ssd01 to ssd but it doesn't work.

We have a V9 but libname V6 is not accepted

Thank you for the proposal

[ballardw]

---

@Dallain wrote:

I have yet tried to change ssd01 to ssd but it doesn't work.

We have a V9 but libname V6 is not accepted

Thank you for the proposal

---

We may have a suggestion or two if you share the LOG from submitting the LIBNAME statement and any notes or messages from submitting it. And just because you have a file in a library currently defined as V9 doesn't mean that you can't point the V6 engine to it:

1351  libname mylib1 "&drive2.";
NOTE: Libref MYLIB1 was successfully assigned as follows:
      Engine:        V9
      Physical Name: W:\WardB
1352  libname mylib2 v6 "&drive2.";
NOTE: The V6 engine on this host is limited to read-only access of SAS data files without index
      optimization.  V6 data files cannot be created or updated and V6 catalogs cannot be read.
NOTE: Libref MYLIB2 was successfully assigned as follows:
      Engine:        V6
      Physical Name: W:\WardB

You may have issues trying to write to a V6 library but you may be able to read there as shown in my log above.

[Tom]

---

@Dallain wrote:

I want to read table sas having an ".ssd01" extension. When forcing extension ".sas7bdat" to ".ssd01" it answer : Unable to load it. the most common cause is associated index not found. Can you help me ?

Dallain    

---

I do not think the Universal Viewer can open a Unix SAS version 6 dataset.

Do you still have a Unix version of SAS you could use to try and read the file?

Does Version 9 of SAS even still support reading version 6 datasets?  Or would you need to run version 8? (if you can get a valid setinit for it)

[Dallain]

I agree  the Universal Viewer can not open a Unix SAS version 6 dataset.

We have a version 9 but it can not accept V6 engine. I don't know if Version 8 is able to read it. I will ask to administrators But I am afraid not as they propose me to use The Universal Viewer which is not running for Unix SAS version 6.

Thank for your proposal

[ChrisHemedinger]

Pretty sure SAS 9 can read these via the V6 engine but maybe only the 32-bit version (which you probably do not have).  But there may be some tricks with encoding. .ssd01 files are Unix-platform SAS data sets and I think predate the CEDA capability (cross-environment data access). Anyway, Universal Viewer can be coerced to try and open these (though the filename wildcard is *.sas7bdat by default, just change it to *.*). But you may run into errors like you saw...Again, I think the advice is to try the 32-bit version of Universal Viewer -- bit architecture and encoding are intertwined.

[Dallain]

I used the 32bit version of theUniversal Viewer. But it don't work even when I change the file wildcard from.sas7bdat to *.* or *.ssd01

[SASKiwi]

I suggest you open a Tech Support track for your issue as they may have some other ideas.