<?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 DI Error in SAS Studio</title>
    <link>https://communities.sas.com/t5/SAS-Studio/SAS-DI-Error/m-p/339252#M2035</link>
    <description>&lt;P&gt;By default your workspace server session runs with that location as current working dir. That will give you issues when you (or some underlying code) use relative pathnames as it is not a place any admin will gladly allow you write access, as &lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/35204"&gt;@JuanS_OCS&lt;/a&gt; rightly said.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have a look at &lt;A href="http://support.sas.com/kb/50/345.html" target="_self"&gt;SAS Note 50345&lt;/A&gt; that discusses this and proposes a way of dealing with this for once and for all. You will need your trusted SAS admin to implement this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Alternatively you can direct the bulkload files explicitly to a location of your choosing with the BL_* (BL_DATAFILE, BL_CONTROL etc.) dataset options. Refer to the online &lt;A href="http://support.sas.com/documentation/cdl/en/acreldb/69580/HTML/default/viewer.htm#n0amnbomcgx6jnn1o2wxytsii839.htm" target="_self"&gt;docs &lt;/A&gt;for details.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;/P&gt;
&lt;P&gt;- Jan.&lt;/P&gt;</description>
    <pubDate>Wed, 08 Mar 2017 14:30:17 GMT</pubDate>
    <dc:creator>jklaverstijn</dc:creator>
    <dc:date>2017-03-08T14:30:17Z</dc:date>
    <item>
      <title>SAS DI Error</title>
      <link>https://communities.sas.com/t5/SAS-Studio/SAS-DI-Error/m-p/339194#M2031</link>
      <description>&lt;P&gt;Dear Friends,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using Oracle Bulk Loader option for loading in to oracle, but getting following error.&lt;/P&gt;&lt;P&gt;Please help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;...ERROR: Insufficient authorization to access /sasconf/Config_Lev1/Lev1/SASApp/BL_STG_CUSTOMER_DTLS_1.ctl.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Prashant.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 12:30:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/SAS-DI-Error/m-p/339194#M2031</guid>
      <dc:creator>sas_pkc1</dc:creator>
      <dc:date>2017-03-08T12:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: SAS DI Error</title>
      <link>https://communities.sas.com/t5/SAS-Studio/SAS-DI-Error/m-p/339229#M2033</link>
      <description>&lt;P&gt;Dear&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/119705"&gt;@sas_pkc1&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would say&amp;nbsp;you need your SAS Admin to grant your user the required access on the filesystem... although I am a bit concerned that your code is writting&amp;nbsp;&lt;SPAN&gt;BL_STG_CUSTOMER_D&lt;/SPAN&gt;&lt;WBR /&gt;&lt;SPAN&gt;TLS_1.ctl in that location. You should probably write that file in a separate location that has the appropiate permissions.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 13:45:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/SAS-DI-Error/m-p/339229#M2033</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2017-03-08T13:45:40Z</dc:date>
    </item>
    <item>
      <title>Re: SAS DI Error</title>
      <link>https://communities.sas.com/t5/SAS-Studio/SAS-DI-Error/m-p/339252#M2035</link>
      <description>&lt;P&gt;By default your workspace server session runs with that location as current working dir. That will give you issues when you (or some underlying code) use relative pathnames as it is not a place any admin will gladly allow you write access, as &lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/35204"&gt;@JuanS_OCS&lt;/a&gt; rightly said.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have a look at &lt;A href="http://support.sas.com/kb/50/345.html" target="_self"&gt;SAS Note 50345&lt;/A&gt; that discusses this and proposes a way of dealing with this for once and for all. You will need your trusted SAS admin to implement this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Alternatively you can direct the bulkload files explicitly to a location of your choosing with the BL_* (BL_DATAFILE, BL_CONTROL etc.) dataset options. Refer to the online &lt;A href="http://support.sas.com/documentation/cdl/en/acreldb/69580/HTML/default/viewer.htm#n0amnbomcgx6jnn1o2wxytsii839.htm" target="_self"&gt;docs &lt;/A&gt;for details.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;/P&gt;
&lt;P&gt;- Jan.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 14:30:17 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/SAS-DI-Error/m-p/339252#M2035</guid>
      <dc:creator>jklaverstijn</dc:creator>
      <dc:date>2017-03-08T14:30:17Z</dc:date>
    </item>
  </channel>
</rss>

