topic Recover file in PG1 library in SAS Studio

Recover file in PG1 library

JohnWeyk — Sat, 15 Feb 2020 02:24:53 GMT

*How do I recover a file?

I am learning SAS using University SAS Studio and I came across the following problem. The eu_occ table that is part of the PG1 library of the Essentials 1 course is only showing the Country and Geo columns:

*Run pg1.eu_occ;
data pg1.eu_occ2;
	set pg1.eu_occ;
run;

Using statements suggested by Roger Dean:

*Statements by Roger Dean;
data WORK.EU_OCC;
   infile datalines dsd truncover;
   input Geo:$2. Country:$40.;
   label Geo="Country Code" Country="Reporting Country";
 datalines;
 AT Austria
 AT Austria
 AT Austria
 AT Austria
 AT Austria
 ;;;;

 NOTE: There were 5 observations read from the data set PG1.EU_OCC.
 NOTE: DATA statement used (Total process time):
       real time           0.00 seconds
       cpu time            0.00 seconds
       
 
 250        
 251        OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
 263

How can I recover the original file? It is necessary for other stages of the course.
I have tried to create a new library, called PG2 but it just makes a copy of PG1.

Any suggestions?

Re: Recover file in PG1 library

Reeza — Sat, 15 Feb 2020 03:11:21 GMT

Go back to the original setup code and run it again - but consider putting it in a different folder. Then replace the one file you want.

If you're on Windows you can try the Previous Versions trick via File Properties in Windows Explorer if you have it turned on.

Re: Recover file in PG1 library

ed_sas_member — Sat, 15 Feb 2020 08:39:39 GMT

Hi @JohnWeyk

In addition to @Reeza 's answer, you can put access=readonly in the libname statement to avoid this kind of issue.

libname pg1 "&path./data" access=readonly;

Re: Recover file in PG1 library

JohnWeyk — Sat, 15 Feb 2020 17:20:33 GMT

Thanks for the tip.

Re: Recover file in PG1 library

JohnWeyk — Sat, 15 Feb 2020 17:23:22 GMT

Thank you very much, I managed to recover the original file using Windows.

Re: Recover file in PG1 library

Reeza — Sat, 15 Feb 2020 21:40:12 GMT

@ed_sas_member wrote:

Hi @JohnWeyk

In addition to @Reeza 's answer, you can put access=readonly in the libname statement to avoid this kind of issue.
libname pg1 "&path./data" access=readonly;

I think the course requires you to write to that library periodically though?