topic Re: Stuck Status / Program in SAS Enterprise Guide

Stuck Status / Program

deleted_user — Tue, 25 May 2010 17:29:51 GMT

I'm running into a problem after I hit run for my code in EG, the program executes for a while and then becomes stuck (i.e., the status message stays the same) and I have to kill sas.exe or EG. The program doesn't appear to get stuck in the same spot.

I'm wondering if this is a memory issue of some sorts. My code essentially runs through a data set where at each row I perform a call execute to run a macro. The macro runs a GLMSELECT, REG and returns some summary stats. If I limit my number of calls, the code is fine. However, when I run my full list (about 200 calls to the macro), I run into trouble. Many times it get's stuck on "Collecting...".

I've tried turning off the ODS results and log file but still have it stalling. all of this is run locally.

Also, this code runs fine in SAS when I wanted to see if it was EG or a SAS issue.

thanks. Message was edited by: dr. x

Re: Stuck Status / Program

Doc_Duke — Tue, 25 May 2010 22:44:36 GMT

A couple of things that you could try:

--Watch the task manager's Performance screen to see if you are running out of memory.
--Explicitly declare your macro variables as "local" so they are freed at the end of the call.
--Check out http://support.sas.com/kb/33/007.html .

Re: Stuck Status / Program

deleted_user — Wed, 26 May 2010 12:58:45 GMT

Thanks. Unfortunately it still hangs. Via task manager, it doesn't look close to running out of memory.

I've even taken out all macro variables and placed the code directly in the call execute.

something like the following which call GLMSELECT about 200 times (even if I run it 50 times it may fail) and in the code below it is just being repeated on the same data:

data response_list2;
set response_list;
call execute(' ');
run;
quit;

Re: Stuck Status / Program

ChrisHemedinger — Thu, 27 May 2010 13:21:16 GMT

Can you work with SAS Technical Support on this? It would help if you can provide a sample program, plus the logging output from following these steps:

http://support.sas.com/kb/17/730.html

That will help us to see where things are hanging up.

Chris