Thanks. But I tried to submit the batch by right clicking and batch submit, then come back to UE and edit the file and save it, still locked. This batch submit has nothing to do with Ultraedit setting. So, this seems to be the SAS issue, not a UE issue.

-----Original Message----- From: Bolotin Yevgeniy [mailto:YBolotin@schools.nyc.gov] Sent: Tuesday, May 24, 2011 9:50 AM To: Huang, Ya Subject: RE: Source code locked during batch run

UE = ultraedit? Sounds like something that it's doing, rather than something SAS-specific... you can test by setting up something like submitting a job to cmd /k (this will open a command window and leave it open) - if the file won't save until you close the command window, it's UE, and you have to dig through its options to see if you can find one to change this behavior...

-----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