Hi @olabuh
Have you checked if the process is frozen, i.e. doing nothing, or actually running? - Find the SAS process in Task Manager, right-click on any column header and select the 3 I/O - byte columns, and follow it for 10 seconds to see if there are any movements in CPU or these columns. If not, the process is frozen, and you can (and should) kill it in task manager.
And free as many ressources as possible before you run your job. Close other memory-consuming apps like MS Office products.
You might have one or more "dead" sas processes holding ressources. besides the one you are working in. Kill them too to free ressources. If you put this line in your program before your Proc xxx, you get the PID written to the log before the session freezes, so you can identify the actual process in Task Manager, if there are more SAS processes running:
%put &=sysJobID;
And before you invest in more RAM, see if your SAS is configured to use all available ressources. Unfortunately that is beyond my knowledge, but I am sure there are many experts out there, if you start another thread with that topic.
... View more