wkossack, from your posting and the verbiage in the log: ERROR: Rename of temporary member for WORK.TEMPP.DATA failed.                                   File may be found in C:\DOCUME~1\SAS\LOCALS~1\Temp\SAS Temporary Files\_TD5232.                I believe this is caused by latency on the disk versus the next thing SAS is doing with the file after writing to tempp.sas7bdat.lck and then trying to rename it from tempp.sas7bdat.lck to tempp.sas7bdat (thus the error in the rename operation).  I have been experiencing this same rename error for the past several weeks and have to come to realize that our IT Department activated BitLock on our Win-7 32-bit laptops (I have no control over the environment, just a user).  The nature of BitLocker is that it purposely "scatters" all of the data across the hard drive versus "concentric" writing in order to obfuscate would be drive hackers (among other techniques BitLocker employs), so with the added overhead in write operations, SAS, in its "need for speed" and opening, writing, closing, renaming, and going on to the next proc or data step, is moving too quickly for the system to keep pace, hence, the rename errors.  We probably don't get this problem with other office applications because we aren't moving along as quickl;y as batched statements in SAS do....  I've been toying with a macro to come behind the last data step (or proc) to test if the *.sas7bdat.lck" of &sysdsn(substring 9-32) is present, and if so to pause 2 sec then issue a DOS rename command.  I'm still testing, but if this is something you'd be interested in I can post the macro here when I think it's ready. thanks, John ... View more