topic Re: libname defaulting to V6 and then not working in SAS Data Management

libname defaulting to V6 and then not working

dleduc — Mon, 17 May 2021 22:28:10 GMT

I am running version 9.4 of SAS on my Windows 10 desktop. When I use a libname statement as in

libname sss "C:\Users\dleduc\Documents\data\loblolly\sudden_sawlog";
run;

I get the following response:

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 SSS was successfully assigned as follows:
Engine: V6
Physical Name: C:\Users\dleduc\Documents\data\loblolly\sudden_sawlog

I then attempt to use this library to store a dataset and it acts like it says above. I cannot write to it.

ERROR: Write access to member SSS.NEW.DATA is denied.
NOTE: The SAS System stopped processing this step because of errors.

I have no interest in creating a V6 dataset like several of the other people I have read responses from. I just want a dataset that I can keep and then examine since I have something else funny going on in my analysis program. If V9 is supposed to be the default, why is my system defaulting to V6?

Thank you for any help that you can provide.

Re: libname defaulting to V6 and then not working

SASKiwi — Mon, 17 May 2021 22:48:23 GMT

The fact that you can't write to that folder means your Windows permissions on it is set to read-only. You can confirm this by opening the folder in Windows Explorer and checking the Properties. You have to fix this in Windows - it is not a SAS problem. Refer to your IT help desk if you can't fix it. IT often locks down some PC hard drive folders so staff can't delete anything by accident.

Try creating a brand-new folder and assigning a new LIBNAME to it. That should work as you expect.

Re: libname defaulting to V6 and then not working

JackHamilton — Tue, 18 May 2021 00:01:15 GMT

Is there a v6 data set, or something that SAS might think to be a v6 data set, in that directory? If so, SAS might think you don't want the default engine. You could try explicitly specifying an engine in the libname statement.

Re: libname defaulting to V6 and then not working

Kurt_Bremser — Tue, 18 May 2021 06:30:47 GMT

Inspect the directory. If there is a file with .ssd or .ssd01 extension in it, this causes the switch to V6.

In any case, force the engine:

libname sss v9 "C:\Users\dleduc\Documents\data\loblolly\sudden_sawlog";

Note that LIBNAME is a global statement, so no RUN is necessary.

Re: libname defaulting to V6 and then not working

dleduc — Tue, 18 May 2021 14:19:36 GMT

Being able to write to the folder is not the problem. I can write text files to it all day long. The problem is that I cannot write to a V6 file as the error message says.

Re: libname defaulting to V6 and then not working

Tom — Tue, 18 May 2021 14:27:02 GMT

You must have some version 6 datasets in that directory already.

Just change the LIBNAME statement to be explicit about which engine you want to use.

Use BASE engine to use the default for your current SAS version.

libname sss base "C:\Users\dleduc\Documents\data\loblolly\sudden_sawlog";

If you need to read those old V6 dataset point a different libref at that same directory and use that.

libname sssv6 v6 "C:\Users\dleduc\Documents\data\loblolly\sudden_sawlog" access=readonly;

Re: libname defaulting to V6 and then not working

dleduc — Tue, 18 May 2021 14:27:43 GMT

Actually the file that was in the folder had an extension of .sd2. I had last worked with this data about 25 years ago so I don't even know what version of SAS I was using then. Removing that file solves the problem.

Re: libname defaulting to V6 and then not working

Kurt_Bremser — Tue, 18 May 2021 14:40:20 GMT

That's also one of the filename extensions used for V6 datasets on Windows. If you have something likle that, you can preserve the data for future use:

libname sss v9 "C:\Users\dleduc\Documents\data\loblolly\sudden_sawlog";
libname sss_old v6 "C:\Users\dleduc\Documents\data\loblolly\sudden_sawlog";

proc copy inlib=sss_old outlib=sss;
run;

proc datasets nolist lib=sss_old kill;
quit;

libname sss_old clear;