Date:         Fri, 10 Feb 2006 14:35:38 -0800
Reply-To:     "donchanger@yahoo.com" <donchanger@YAHOO.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "donchanger@yahoo.com" <donchanger@YAHOO.COM>
Organization: http://groups.google.com
Subject:      Re: Switch to log window
Comments: To: sas-l@uga.edu
Content-Type: text/plain; charset="iso-8859-1"

Thanks for all the suggestions!  Mark's suggestion may be great but
seemed like a bit much just to know when my code was done!  However, I
may also want to automatically store the log file so perhaps it will
save me grief on that one ....

Paul's suggestion was *very* close.  When I used it as-is, I got an
open Editor window, in addition to my already open Enhanced Editor
window.  I remembered that happening before and I figured out then how
to fix, wrote the code, and promptly forgot what it was or how it
worked.  So, looking at that, I tried a few permutations of Paul's code
mashed with mine and stumbled upon this that seems to work for me:

dm wpgm 'log;'

I don't really understand dm commands and (surprise!) the docs I have
available are, to put it gently, 'lacking', so this was just blundering
and probably will fail when I can least afford it, but it's working for
now.

Combining this with a sound statement, I can happily work elsewhere and
know when my awful long programs are done.

data blah; set blah;
  run way too much other code;
  run;

%put ;
%put ***** Done *****;
%put ;
data _null_;
 call sound(440,200); run;    *memories of good-old DOS days....;
dm wpgm 'log;' *no trailing semi -- adding it opens 2nd editor (why?)
run;

Anyway, thanks all!

Don