The reason for that is to improve performance. The PROC stays in memory and "waits" for more statements as long as possible. That means, if you have more PROC GLMs you can possibly bring them together and save overhead. Normally that should be no problem, because SAS recognizes if another step follows (you can test that with adding a PROC PRINT after PROC GLM) and ends the PROC. If you have completed all sub-steps in PROC GLM (or any other resident PROC) you can end it with QUIT; If you need other GLM steps after that, you have to call the PROC again.

On Sat, 9 Sep 2000 01:37:24 GMT, GF <gfraley@EARTHLINK.NET> wrote:

>You need to use quit; instead of run;, since this is an interactive proc, >like sql. > >"Gail Rogers" <vanca@hnrc.tufts.edu> wrote in message >news:39B92E74.9CD25097@hnrc.tufts.edu... >> Hi All, >> This is probably a simple question so forgive my ignorance. >> When using SAS V8 the last proc in my program will produce the necessary >> output but the Enhanced editor title bar will say "proc XXX is running" >> and I need to break and cancel the submitted statements to get rid of >> the message and free up the memory. I can get around this by putting a >> second semicolon at the end of the last proc i.e. >> >> proc glm data=junk; >> class var1 ; >> model var3=var1 var2; >> run; >> ; >> >> which is fine except that I am usually calling a macro as the last part >> of my program (which should require no semicolons). I've tried adding >> semicolons to terminate the last call but this has not worked. I want to >> keep the windows open so I do not want to use the endsas command. >> >> Any suggestions or explanations? I am using SAS locally on an NT >> platform. >> -- >> Gail Rogers >> Programmer/Analyst >> Epidemiology Program >> USDA-HNRC at Tufts University >> email: vanca@hnrc.tufts.edu >> voice: 617-556-3338