<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SAS EG &amp;quot;resumed from windows sleep and has disconnected from all servers&amp;quot; - constantly in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-EG-quot-resumed-from-windows-sleep-and-has-disconnected-from/m-p/643468#M18825</link>
    <description>&lt;P&gt;First of all, extend the time before your computer goes to sleep. You can find that in the energy options of Windows.&lt;/P&gt;
&lt;P&gt;EG loses network connections (and that includes "local" connections that utilize network sockets) as soon as the computer goes to sleep, and since "orphaned" workspace servers terminate, EG needs to start a new one.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Next, store intermediate datasets in a place aside from WORK. Create a directory in your Users directory, and define a libname called USER for it in your autoexec (eg in code sent to the workspace server when a connection is established).&lt;/P&gt;
&lt;P&gt;USER is some kind of "permanent WORK". When such a library is defined, all single-level datasets will be created (and searched for) there instead of WORK, but will not be deleted at end of session.&lt;/P&gt;</description>
    <pubDate>Tue, 28 Apr 2020 05:32:19 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2020-04-28T05:32:19Z</dc:date>
    <item>
      <title>SAS EG "resumed from windows sleep and has disconnected from all servers" - constantly</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-EG-quot-resumed-from-windows-sleep-and-has-disconnected-from/m-p/643462#M18823</link>
      <description>&lt;P&gt;Every time I have a tiny break, my needy SAS EG 8.2 session disconnects and forgets all the datasets I've created. So I have to rerun everything from the start. Seems unnecessary since I'm running everything on local computer with no server/profile selected. Please help.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2020 04:19:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-EG-quot-resumed-from-windows-sleep-and-has-disconnected-from/m-p/643462#M18823</guid>
      <dc:creator>Rafgotsas</dc:creator>
      <dc:date>2020-04-28T04:19:29Z</dc:date>
    </item>
    <item>
      <title>Re: SAS EG "resumed from windows sleep and has disconnected from all servers" - constantly</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-EG-quot-resumed-from-windows-sleep-and-has-disconnected-from/m-p/643468#M18825</link>
      <description>&lt;P&gt;First of all, extend the time before your computer goes to sleep. You can find that in the energy options of Windows.&lt;/P&gt;
&lt;P&gt;EG loses network connections (and that includes "local" connections that utilize network sockets) as soon as the computer goes to sleep, and since "orphaned" workspace servers terminate, EG needs to start a new one.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Next, store intermediate datasets in a place aside from WORK. Create a directory in your Users directory, and define a libname called USER for it in your autoexec (eg in code sent to the workspace server when a connection is established).&lt;/P&gt;
&lt;P&gt;USER is some kind of "permanent WORK". When such a library is defined, all single-level datasets will be created (and searched for) there instead of WORK, but will not be deleted at end of session.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2020 05:32:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-EG-quot-resumed-from-windows-sleep-and-has-disconnected-from/m-p/643468#M18825</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2020-04-28T05:32:19Z</dc:date>
    </item>
  </channel>
</rss>

