<?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 timeout Best Practices in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-timeout-Best-Practices/m-p/297846#M6008</link>
    <description>&lt;P&gt;What type of seesions are you referring to? My guess is SAS/Studio as there is a 1 hour default in the settings for this. Best practice would depend on a number of factors including how users work with SAS and also site security requirements. For example you can now run batch jobs from SAS/Studio - if SAS times out before the batch job completes then that isn't very convenient.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would suggest setting timeouts to at least cover a working day, say 8 hours. IT Security might have different ideas.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note also that SAS might also be affected by external network and communications related timeouts as well.&lt;/P&gt;</description>
    <pubDate>Mon, 12 Sep 2016 19:51:12 GMT</pubDate>
    <dc:creator>SASKiwi</dc:creator>
    <dc:date>2016-09-12T19:51:12Z</dc:date>
    <item>
      <title>SAS timeout Best Practices</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-timeout-Best-Practices/m-p/297784#M6006</link>
      <description>&lt;P&gt;Does anyone know of or have a "best practices" as far as SAS servers and the sesson timeout settings. &amp;nbsp;Ours is currently set to 60 mins and causes problems when people go for lunch and then have to sign back on to the session. &amp;nbsp;Looking for something around what the best practices are for balancing user requirements against network security.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Sep 2016 16:12:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-timeout-Best-Practices/m-p/297784#M6006</guid>
      <dc:creator>paulsparrow</dc:creator>
      <dc:date>2016-09-12T16:12:16Z</dc:date>
    </item>
    <item>
      <title>Re: SAS timeout Best Practices</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-timeout-Best-Practices/m-p/297846#M6008</link>
      <description>&lt;P&gt;What type of seesions are you referring to? My guess is SAS/Studio as there is a 1 hour default in the settings for this. Best practice would depend on a number of factors including how users work with SAS and also site security requirements. For example you can now run batch jobs from SAS/Studio - if SAS times out before the batch job completes then that isn't very convenient.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would suggest setting timeouts to at least cover a working day, say 8 hours. IT Security might have different ideas.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note also that SAS might also be affected by external network and communications related timeouts as well.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Sep 2016 19:51:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-timeout-Best-Practices/m-p/297846#M6008</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2016-09-12T19:51:12Z</dc:date>
    </item>
    <item>
      <title>Re: SAS timeout Best Practices</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-timeout-Best-Practices/m-p/298153#M6029</link>
      <description>&lt;P&gt;You can max it out at 240 hours. &amp;nbsp;That's what we use...&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2016 21:16:22 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-timeout-Best-Practices/m-p/298153#M6029</guid>
      <dc:creator>KenAanderud</dc:creator>
      <dc:date>2016-09-13T21:16:22Z</dc:date>
    </item>
  </channel>
</rss>

