I would side with Paul here. You don't know exactly how the temporary file corresponds to the program that you are executing.

Four days of runtime sounds excessive today for processing datasets of GB scale. Perhaps this unfortunate event will motivate improvements in the program. Many SAS programmers have benefited from advice on how to streamline programs from Paul and others on the 'L.

While I strongly prefer to see a large program run in one stream, SAS does make it easy to segment programs into %INCLUDE blocks, save temporary files to permanent libraries, and delete temporary files in a subsequent %INCLUDE block. I'd program that safeguard before launching another program on a four-day journey. S

-----Original Message----- From: owner-sas-l@listserv.uga.edu [mailto:owner-sas-l@listserv.uga.edu] On Behalf Of kvasikonkav@gmail.com Sent: Wednesday, September 19, 2007 7:04 PM To: sas-l@uga.edu Subject: Large datastep interrupted, have a large data1.sas7bdat.lck file - any way to convert to usable data?

I was running a job on a server, and the server was rebooted.

Consequently, I have a partially completed datafile, which has the suffix .sas7bdat.lck

The ".lck" file is a 225,000,000kb file (I think that is 225gb, right?)

SAS was nearly done processing a datastep when the server was rebooted. My understanding is that the ".lck" extension is sort of a temporary dataset that will later be renamed once the datastep is fully finished.

I don't want to wait another 4 days for the program to run again, so I was hoping the nearly complete ".lck" data could be recovered into a regular dataset without too much effort?

is there any way to recover any of the data out of a ".sas7bdat.lck" file, or convert it into a sas7bdat file?

Thanks!

Thanks again!