<?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: How to restric the ouput destination of a PROC EXPORT in Architecture</title>
    <link>https://communities.sas.com/t5/Architecture/How-to-restric-the-ouput-destination-of-a-PROC-EXPORT/m-p/640530#M228</link>
    <description>&lt;P&gt;You may need to describe your SAS environment in much more detail.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If everything goes through a server you should be able to restrict user permissions.&lt;/P&gt;
&lt;P&gt;If you are talking about stand alone PC with SAS loaded locally you are going to have a very hard time with this.&lt;/P&gt;</description>
    <pubDate>Thu, 16 Apr 2020 20:00:29 GMT</pubDate>
    <dc:creator>ballardw</dc:creator>
    <dc:date>2020-04-16T20:00:29Z</dc:date>
    <item>
      <title>How to restric the ouput destination of a PROC EXPORT</title>
      <link>https://communities.sas.com/t5/Architecture/How-to-restric-the-ouput-destination-of-a-PROC-EXPORT/m-p/640526#M227</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For security reasons, we are searching for a solution to restrict the destination path for proc export. We want to block the access to the local drive. Anyone have a solution?&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2020 19:47:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Architecture/How-to-restric-the-ouput-destination-of-a-PROC-EXPORT/m-p/640526#M227</guid>
      <dc:creator>NicolaG</dc:creator>
      <dc:date>2020-04-16T19:47:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to restric the ouput destination of a PROC EXPORT</title>
      <link>https://communities.sas.com/t5/Architecture/How-to-restric-the-ouput-destination-of-a-PROC-EXPORT/m-p/640530#M228</link>
      <description>&lt;P&gt;You may need to describe your SAS environment in much more detail.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If everything goes through a server you should be able to restrict user permissions.&lt;/P&gt;
&lt;P&gt;If you are talking about stand alone PC with SAS loaded locally you are going to have a very hard time with this.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2020 20:00:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Architecture/How-to-restric-the-ouput-destination-of-a-PROC-EXPORT/m-p/640530#M228</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2020-04-16T20:00:29Z</dc:date>
    </item>
    <item>
      <title>Re: How to restric the ouput destination of a PROC EXPORT</title>
      <link>https://communities.sas.com/t5/Architecture/How-to-restric-the-ouput-destination-of-a-PROC-EXPORT/m-p/640632#M229</link>
      <description>&lt;P&gt;To control where SAS writes to, consider to use LOCKDOWN:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://documentation.sas.com/?cdcId=bicdc&amp;amp;cdcVersion=9.4&amp;amp;docsetId=biasag&amp;amp;docsetTarget=n23000intelplatform00srvradm.htm&amp;amp;locale=en" target="_blank" rel="noopener"&gt;LOCKDOWN Statement&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;In a client/server environment, you can (and should) use the tools of the operating system (permissions) to control where users can write to; also use file system quotas to prevent users from wasting storage.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Apr 2020 07:56:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Architecture/How-to-restric-the-ouput-destination-of-a-PROC-EXPORT/m-p/640632#M229</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2020-04-17T07:56:09Z</dc:date>
    </item>
  </channel>
</rss>

