BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
asimraja
Fluorite | Level 6

Hi,

 

I'm executing some SAS code where my log file is quite large. My job stops and SAS Enterprise Guide gives me a useless error after the log file reaches a certain size. I am able to work around that by using a "proc printto" to create a log file not within SAS Enterprise Guide but on the Linux machine.

 

Is there something I can do to increase the log size in SAS Enterprise Guide? What is the default log size?

 

 

SAS Grid Error Message.jpg

 

1 ACCEPTED SOLUTION

Accepted Solutions
CaseySmith
SAS Employee

Hi @asimraja,

 

"The server is disconnected" actually indicates that the server session was disconnected, which will happen if a large enough log is generated, such that the server session runs out of memory.  Proc printto is the suggested workaround.

 

Note: SAS 9.4M5 added log-streaming capability (can be turned on via internal "options iomlogautoflush;"), which will stream the log events back to the client as they occur, thus avoiding the buffering of the log events on the server leading to the out of memory condition.

 

Casey


Register today and join us virtually on June 16!
sasglobalforum.com | #SASGF

View now: on-demand content for SAS users

View solution in original post

4 REPLIES 4
nhvdwalt
Barite | Level 11

Have no idea. Generally it seem like people redirect the logs away from E Guide, like you did, rather than increasing the log size.

 

An old post about something similar....

https://communities.sas.com/t5/SAS-Enterprise-Guide/Increase-the-log-in-the-EG/td-p/57472

 

Kurt_Bremser
Super User

When logs grow that large, it's usually a sign of bad code. Either there are erroneous put steps that fill the log, or steps are unnecessarily repeated instead of by group processing.

CaseySmith
SAS Employee

Hi @asimraja,

 

"The server is disconnected" actually indicates that the server session was disconnected, which will happen if a large enough log is generated, such that the server session runs out of memory.  Proc printto is the suggested workaround.

 

Note: SAS 9.4M5 added log-streaming capability (can be turned on via internal "options iomlogautoflush;"), which will stream the log events back to the client as they occur, thus avoiding the buffering of the log events on the server leading to the out of memory condition.

 

Casey


Register today and join us virtually on June 16!
sasglobalforum.com | #SASGF

View now: on-demand content for SAS users

asimraja
Fluorite | Level 6
Thank you for the guidance!

SAS Innovate 2025: Save the Date

 SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!

Save the date!

SAS Enterprise Guide vs. SAS Studio

What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.

Find more tutorials on the SAS Users YouTube channel.

SAS Training: Just a Click Away

 Ready to level-up your skills? Choose your own adventure.

Browse our catalog!

Discussion stats
  • 4 replies
  • 5255 views
  • 3 likes
  • 4 in conversation