@AlainX wrote:
THERE IS A TERMINATION REPORT WITH A DATE/TIME, BUT NOTHING HAPPENED IN TERMS OF RESOURCES CRASH. ALL MY TASKS PROCESSED WITH NO PROBLEM. SO IT IS A SAS BUG. CAN U SOLVE IT OR NOT?
Yelling won't help.
It might be that you submitted code that did not "crash" but also did not terminate properly and the system terminated it. Common examples are use of Proc SQL the you end with RUN: instead of Quit; That can create the intended desired data set, for example, BUT the procedure is still running.
For example:
156 Proc sql;
157 create table example as
158 select *
159 from sashelp.class
160 where sex='F'
161 ;
NOTE: Table WORK.EXAMPLE created, with 9 rows and 5 columns.
162 run;
NOTE: PROC SQL statements are executed immediately; The RUN statement has no effect.
No error, data set created but do see the NOTE. 'Has no effect' means the procedure was not terminated.
In the local Display Manager system I run this code on the Editor window actually shows a message: Proc SQL running.
After posting the above example and typing the sentences above I submit a separate Quit statement and now my log includes the diagnostics about how long the Proc SQL step took:
163 quit;
NOTE: PROCEDURE SQL used (Total process time):
real time 2:35.43
cpu time 0.54 seconds
Try running the example program I show above and see how much "real time" is taken when you do not provide a Quit statement.
Then execute a quit.
I am not saying this is exactly what happened to your system but is an example of something that might have occurred. We do not have all of the code or data sets you ran code against. We don't have logs. We only have your statement: "A few days ago, after experimenting and running various tasks with some of my data sets, a new folder appeared in my dashboard, under the name "my_system_notices" ."
Something that only shows a "termination report" sounds like it stopped something that was left running, perhaps that you did not realize was running.
Did you attempt to remove the "termination report" before attempting to delete the folder? It is not uncommon for tools to refuse to delete folders that contain files if the proper approach is not chosen. Windows Explorer by default won't delete a folder with a file in it for example. Which behavior goes back to the days of DOS 2.1 IIRC.
No promise that will work but I've never created one of these folders to test against.
... View more
