<?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: Need help locking down work tables in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Need-help-locking-down-work-tables/m-p/7727#M2420</link>
    <description>Yes it can be done.&lt;BR /&gt;
&lt;BR /&gt;
What kind of server are you dealing with?&lt;BR /&gt;
Each platform has its own things.&lt;BR /&gt;
&lt;BR /&gt;
The general guideline would be that each user has their own login and workspace, which is protected by OS level security features.&lt;BR /&gt;
&lt;BR /&gt;
SAS supports the concept of SASUSER, but you have to be careful, because SASUSER is typically a persistent library, unlike WORK.  But, it is possible to have a unique WORK directory/libary for each user.  For Windows and Unix, for each account, either set the SAS_User_Config environment variable, or have a sasV9.cfg file in the user's "$HOME" directory.  For a mainframe, control would be through RACF.</description>
    <pubDate>Thu, 27 Mar 2008 17:28:10 GMT</pubDate>
    <dc:creator>deleted_user</dc:creator>
    <dc:date>2008-03-27T17:28:10Z</dc:date>
    <item>
      <title>Need help locking down work tables</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Need-help-locking-down-work-tables/m-p/7726#M2419</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
Does anyone know if there is a way to lock down individual work tables on the SAS server side? We are trying to limit access to critical customer information so that person A cannot log into the server and look at person B's work files. Any help you could provide would be great! &lt;BR /&gt;
&lt;BR /&gt;
Thanks in advance!</description>
      <pubDate>Thu, 27 Mar 2008 17:12:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Need-help-locking-down-work-tables/m-p/7726#M2419</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2008-03-27T17:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: Need help locking down work tables</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Need-help-locking-down-work-tables/m-p/7727#M2420</link>
      <description>Yes it can be done.&lt;BR /&gt;
&lt;BR /&gt;
What kind of server are you dealing with?&lt;BR /&gt;
Each platform has its own things.&lt;BR /&gt;
&lt;BR /&gt;
The general guideline would be that each user has their own login and workspace, which is protected by OS level security features.&lt;BR /&gt;
&lt;BR /&gt;
SAS supports the concept of SASUSER, but you have to be careful, because SASUSER is typically a persistent library, unlike WORK.  But, it is possible to have a unique WORK directory/libary for each user.  For Windows and Unix, for each account, either set the SAS_User_Config environment variable, or have a sasV9.cfg file in the user's "$HOME" directory.  For a mainframe, control would be through RACF.</description>
      <pubDate>Thu, 27 Mar 2008 17:28:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Need-help-locking-down-work-tables/m-p/7727#M2420</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2008-03-27T17:28:10Z</dc:date>
    </item>
    <item>
      <title>Re: Need help locking down work tables</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Need-help-locking-down-work-tables/m-p/7728#M2421</link>
      <description>Thanks for the input Chuck! And now, I have come to find out, it was decided that we don't need to lock down our tables according to the powers-that-be. Oh well, still nice to know it can be done!</description>
      <pubDate>Fri, 28 Mar 2008 19:43:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Need-help-locking-down-work-tables/m-p/7728#M2421</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2008-03-28T19:43:08Z</dc:date>
    </item>
  </channel>
</rss>

