Data size limitations for running code

[Tom]

---

@J111 wrote:

Hello,

The administrator checked and the WORK space was fine during the run.

Seems like not a code problem either.

any idea ?

---

What "server" are you losing connection to?  Your code did not appear to be attempting to use SAS/Connect or SAS/Access to some external database.

Is it possible you are using some front end tool to submit your program, like SAS/Studio or Enterprise Guide, and it is the connection from that front end to the SAS server itself that is closing? 

Perhaps it is because the LOG file is just getting too big?

Try using PROC PRINTTO to route the log for that section of the code to another file.

Perhaps it is because the job is just taking too long?

[J111]

Thanks for the proc printo idea, yes we are using EGuide




8

[Kurt_Bremser]

---

@J111 wrote:
Thanks for the proc printo idea, yes we are using EGuide

---

Then you should reduce the log size; EG needs to keep the whole log in memory, and the nicely formatted text eats a lot of it.

Why do you need a complete listing of the created code in the log, when the later execution of it will be in the log anyway?

[J111]

Just updating that we plan to change the data structure and this might also solve this issue. I can check this in the next few days.

[J111]

Hello We solved the issue by changing the data structure Thanks everyone The topic can be closed

[Ksharp]

You could try to use CALL EXECUTE instead of "%include" .

data MATCHING_TABLE_FUNC ;
input  Target $ Formula & $20.;
cards;
v1  x1 + x2 /x3 + x4
v2  x1 + x2 + x4
v3  x1 + x2 + x3
v4  x1 + x2 
;

data TRNP_SERIES_LIST ;
input date :date9. x1 x2 x3 x4;
format date date9.;
cards;
01jan2010 1 2 3 4
01jan2010 4 3 2 1
;

data MATCHING_TABLE_FUNC2;
 set MATCHING_TABLE_FUNC;
 function=catx('=',target,formula)||';';
 keep function;
run;
data _null_;
set MATCHING_TABLE_FUNC2 end=last;
if _n_=1 then call execute('Data Formula_ ; set TRNP_SERIES_LIST ;');
call execute(strip(function));
if last then call execute('run;');
run;

[Ksharp]

I think ballardw was right.
There could be some error data at OBS=177.
For example:
obs x1 x2
177 1 0
when you have formula "target=x1/x2;" ,that could lead to an error.