I have the same behavior when running WPS in batch mode. It's not a UE issue but I believe it's a SAS or WPS issue. You can download handle.zip from sysinternals and run the program handle.exe to determine what process has a lock on the file.

You can find the zip file at: http://technet.microsoft.com/en-us/sysinternals/bb896655

If you were running the program bigpgm5.sas using WPS, you would issue from a dos prompt:

handle -p wpsi -u

I would assume for SAS you would do:

handle -p sas -u

Phil

Philip Rack MineQuest, LLC WPS Consulting and WPS Reseller Tel: (614) 457-3714 Web: www.MineQuest.com Blog: www.MineQuest.com/WordPress

-----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Ya Huang Sent: Tuesday, May 24, 2011 12:30 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Source code locked during batch run

Hi there,

I've noticed this for long time, but never understand why. Basically, I use UE to run my SAS code in batch. Whenever a job is submitted and running, I can still edit the source code, but won't be able to save it until the job is done. I wonder why? Since the job is submitted already, all the source code should be in the memory (unless the source is is really really long?), why the source code need to be locked to prevent it from being changed?

Thanks

Ya