03-29-2012 04:12 PM
Program's running, I decide I want to cancel it so I ctrl-break and cancel submitted statements. After doing that a few times (twice or so), I no longer get updates in my SAS log. Any way to prevent that from happening or to reenable the log?
Base SAS 9.2
03-29-2012 11:21 PM
Did your code contain some statements such as ' ods listing close; ' ?
If it were true. Use ' ods listing; ' to open listing destination again.
03-30-2012 10:31 AM
You should try using the "!" icon to stop a running program:
(Second from the right).
Sometimes it takes a bit to recognize you pressed if the program is really busy at the time.
It seems to stop a running program al litle more cleanly.
03-30-2012 12:35 PM
I really don't know if it is different, but I use the "!" and I don't seem to have any problems with my log.
The only time my log is an issue is when there are upwards of 1 million lines in it. I tend not to close
my SAS session and sometimes I forget to clear the log between programs.
06-11-2013 10:59 AM
One would suggest that if you are using ctrl-break a lot, that determining why that is needed so frequently might be the issue. If it is accidentally (re)running code that you don't want, then highlight only the code wanted and run that. If the program is believed to be running incorrectly or taking "too long" is cause for the interruption then perhaps testing the code using options to limit the number of observations would help on testing.
06-12-2013 05:22 PM
I'm quite interested in seeing this solved too! Unfortunately, I end up needing to interrupt code a lot, even though I agree that it's not the best way to structure one's workflow.
Just for reference, I'm using Base SAS 9.2 on Windows Server 2008, and the submitted statements that I am cancelling are (most often) CREATE TABLE statements in PROC SQL.
06-18-2013 02:29 PM
I found this discussion because I recently started having the same problem and have not been able to resolve it. I often work with large files and frequently stop execution but I have always used the ! button. It has happened with a variety of coding so I can't pinpoint any particular pattern. I have used SAS for a number of years and only recently experienced this problem so I don't think it's inherent to SAS. The only change recently has been our conversion to Windows 7. I am running SAS 9.2 on a Win7 32-bit laptop. The recent code I ran that appears to have created a problem was a very basic SQL query on one table. I plan to email the SAS tech folks since I've had some good success with them in the past but any ideas would be helpful.
08-23-2013 05:40 AM
i found these steps
1) Realise the Log has died on your week old session forcing you to migrate the session or pull out all your hair in frustration
2) Proc export to xls a random dataset
3) Interupt execution before complete
4) Presto, Log is back to normal on the next step
As far as I am concerned I have launch any code and stop it before the end and i got back the log.
It seems that the problem arise when proc sql is stopped. So may be another procedure should be launched to get back the code.
I had a hard time with this problem. Hope it works for you.
03-07-2014 10:23 AM
I just used the method suggested by me on the listserv link above and it worked. It remains the only solution to this bug. I hope its fixed in 9.3!