<?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: Unable to create dataset by using DATA-step (on UNIX folder) in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/421651#M67976</link>
    <description>&lt;P&gt;Step through the path and test each folder.&amp;nbsp; Perhaps the access and/or spelling error is not at the last foldername, but somewhere higher in the path.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are you sure you are testing using the same machine that the SAS process is using?&amp;nbsp; If you have a GRID installation of SAS the machine you use for command prompt is probably a different machine than the one(s) that are used to run the SAS process.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is the SYMLINK pointing to a different disk or the same disk?&amp;nbsp; I have seen issues with some processes where link to other disks are not followed. Never seen it for SAS though.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is the SYMLINK pointing to an absolute path? Or a relative path?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are any of the folders in question mount points?&amp;nbsp; If so are the disks actually mounted?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 15 Dec 2017 17:12:04 GMT</pubDate>
    <dc:creator>Tom</dc:creator>
    <dc:date>2017-12-15T17:12:04Z</dc:date>
    <item>
      <title>Unable to create dataset by using DATA-step (on UNIX folder)</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/420738#M67908</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm truying to create a dataset on a UNIX-folder which is available through a symbolic link.&lt;/P&gt;&lt;P&gt;SAS-code snippet :&lt;/P&gt;&lt;P&gt;libname TEST "/sas/prd/data/DIR_III_4/SHARE_INVORDERING/OUTPUT"; /*generates error*/&lt;BR /&gt;*libname TEST "/sas/prd/data/DIR_III_4/DIR_III_4"; -&amp;gt; works fine&lt;BR /&gt;data TEST.JLSSET3;&lt;BR /&gt;input name $ sales;&lt;BR /&gt;datalines;&lt;BR /&gt;Steven 40&lt;BR /&gt;Jurgen 100&lt;BR /&gt;David 150&lt;BR /&gt;;&lt;/P&gt;&lt;P&gt;Error generated :&lt;/P&gt;&lt;P&gt;26 libname TEST "/sas/prd/data/DIR_III_4/SHARE_INVORDERING/OUTPUT";&lt;BR /&gt;NOTE: Libref TEST was successfully assigned as follows:&lt;BR /&gt;Engine: V9&lt;BR /&gt;Physical Name: /sas/prd/data/DIR_III_4/SHARE_INVORDERING/OUTPUT&lt;BR /&gt;27 *libname TEST "/sas/prd/data/DIR_III_4/DIR_III_4";&lt;BR /&gt;28 data TEST.JLSSET3;&lt;BR /&gt;29 input name $ sales;&lt;BR /&gt;30 datalines;&lt;/P&gt;&lt;P&gt;ERROR: User does not have appropriate authorization level for library TEST.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The UNIX-user 'sasdir34' who actually writes to this UNIX-folder (linked to WorkSpaceServer) can create files via command line on the folder without any problem.&lt;/P&gt;&lt;P&gt;See UNIX-commands :&lt;/P&gt;&lt;P&gt;-bash-4.4$ pwd&lt;BR /&gt;/sas/prd/data/DIR_III_4&lt;BR /&gt;-bash-4.4$ ls -l&lt;BR /&gt;total 14&lt;BR /&gt;drwxr-xr-x 12 sasdir34 sastusers 15 Dec 5 10:07 DCU&lt;BR /&gt;drwxr-xr-x 49 sasdir34 sastusers 82 Dec 13 11:58 DIR_III_4&lt;BR /&gt;lrwxrwxrwx 1 sasdir34 sastusers 25 Nov 26 2012 SHARE_INVORDERING -&amp;gt; /sas/prd/data/invordering&lt;BR /&gt;lrwxrwxrwx 1 sasdir34 sastusers 27 Oct 28 2010 Shared_Data_Preparation -&amp;gt; ../Shared_Data_Preparation/&lt;BR /&gt;-bash-4.4$ touch SHARE_INVORDERING/OUTPUT/testfile.txt&lt;/P&gt;&lt;P&gt;-&amp;gt; file "test_file.txt" is created in&amp;nbsp;&lt;SPAN&gt;SHARE_INVORDERING/OUTPUT&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any idea why a dataset can't be directly written to UNIX-folder -&amp;gt; via symbol link available?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PS. creating the dataset in WORK and then export to this folder does work :&lt;/P&gt;&lt;P&gt;data work.JLSSET3;&lt;BR /&gt;input name $ sales;&lt;BR /&gt;datalines;&lt;BR /&gt;Steven 40&lt;BR /&gt;Jurgen 100&lt;BR /&gt;David 150&lt;BR /&gt;;&lt;/P&gt;&lt;P&gt;proc export data=JLSSET3&lt;BR /&gt;outfile="/sas/prd/data/DIR_III_4/SHARE_INVORDERING/OUTPUT/JLSSET3.xlsx"&lt;BR /&gt;dbms=xlsx&lt;BR /&gt;replace;&lt;BR /&gt;run;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2017 11:09:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/420738#M67908</guid>
      <dc:creator>jurlis</dc:creator>
      <dc:date>2017-12-13T11:09:13Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to create dataset by using DATA-step (on UNIX folder)</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/420741#M67910</link>
      <description>&lt;P&gt;Ask your IT group to look at security permissions, its likely the SAS system account has not been granted the correct permissions.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2017 11:19:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/420741#M67910</guid>
      <dc:creator>RW9</dc:creator>
      <dc:date>2017-12-13T11:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to create dataset by using DATA-step (on UNIX folder)</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/420754#M67911</link>
      <description>&lt;P&gt;Be careful with your tests.&lt;/P&gt;
&lt;PRE&gt;touch SHARE_INVORDERING/OUTPUT/testfile.txt&lt;/PRE&gt;
&lt;P&gt;will work, even though you do not have write permission on the directory, when&lt;/P&gt;
&lt;P&gt;- the file already exists&lt;/P&gt;
&lt;P&gt;- you have write permission on the file&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2017 12:02:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/420754#M67911</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-12-13T12:02:11Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to create dataset by using DATA-step (on UNIX folder)</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/420831#M67926</link>
      <description>&lt;P&gt;Maybe different SAS options such as DLCREATEDIR?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://blogs.sas.com/content/sasdummy/2013/07/02/use-dlcreatedir-to-create-folders/" target="_blank"&gt;https://blogs.sas.com/content/sasdummy/2013/07/02/use-dlcreatedir-to-create-folders/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2017 15:23:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/420831#M67926</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2017-12-13T15:23:29Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to create dataset by using DATA-step (on UNIX folder)</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/421601#M67970</link>
      <description>&lt;P&gt;Thanks for your suggestions!&lt;/P&gt;&lt;P&gt;IT admins (of Solaris UNIX) states that if OK for UNIX-user 'sasdir34' to write/read files to OUTPUT-directory from console then OK for him... &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;drwxrwxr-x&amp;nbsp; 12 sasdir34 saspusers&amp;nbsp; &amp;nbsp; 1374 Dec 13 14:35 OUTPUT&lt;/P&gt;&lt;P&gt;User rights OK&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It remains a mistery why it's not possible to create dataset via DATA-step on this folder.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jurgen&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Dec 2017 15:28:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/421601#M67970</guid>
      <dc:creator>jurlis</dc:creator>
      <dc:date>2017-12-15T15:28:29Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to create dataset by using DATA-step (on UNIX folder)</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/421651#M67976</link>
      <description>&lt;P&gt;Step through the path and test each folder.&amp;nbsp; Perhaps the access and/or spelling error is not at the last foldername, but somewhere higher in the path.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are you sure you are testing using the same machine that the SAS process is using?&amp;nbsp; If you have a GRID installation of SAS the machine you use for command prompt is probably a different machine than the one(s) that are used to run the SAS process.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is the SYMLINK pointing to a different disk or the same disk?&amp;nbsp; I have seen issues with some processes where link to other disks are not followed. Never seen it for SAS though.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is the SYMLINK pointing to an absolute path? Or a relative path?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are any of the folders in question mount points?&amp;nbsp; If so are the disks actually mounted?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Dec 2017 17:12:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/421651#M67976</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2017-12-15T17:12:04Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to create dataset by using DATA-step (on UNIX folder)</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/421930#M68004</link>
      <description>&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;We aren't working in a GRID-setup. 1 Solaris server executes all SAS-tasks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;* In folder "/sas/prd/data/DIR_III_4" -&amp;gt; startfolder of this Workspace Server&lt;BR /&gt;lrwxrwxrwx 1 sasdir34 sastusers 25 Nov 26 2012 SHARE_INVORDERING -&amp;gt; /sas/prd/data/invordering&lt;BR /&gt;* In folder "/sas/prd/data" :&lt;BR /&gt;lrwxrwxrwx 1 root root 23 Nov 20 2012 invordering -&amp;gt; /nfs_mounts/invordering&lt;BR /&gt;* In file "/etc/vfstab" :&lt;BR /&gt;prod2.drsns02.finbel.intra:/landing_invordering - /nfs_mounts/invordering nfs - yes nodevices,vers=3,xattr,zone=zdmsrvp01,sharez&lt;BR /&gt;one=7&lt;BR /&gt;-&amp;gt; symlink (absolute path) is on a different disk (available via nfs)&lt;BR /&gt;-&amp;gt; these disks are mounted since creating files/writing to the disks via SAS is possible via&lt;BR /&gt;proc export data=JLSSET3&lt;BR /&gt;outfile="/sas/prd/data/DIR_III_4/SHARE_INVORDERING/OUTPUT/JLSSET3.xlsx"&lt;BR /&gt;dbms=xlsx&lt;BR /&gt;replace;&lt;BR /&gt;run;&lt;/P&gt;&lt;P&gt;-&amp;gt; writing through a DATA-step on this folder doesn't work&lt;/P&gt;</description>
      <pubDate>Mon, 18 Dec 2017 09:40:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Unable-to-create-dataset-by-using-DATA-step-on-UNIX-folder/m-p/421930#M68004</guid>
      <dc:creator>jurlis</dc:creator>
      <dc:date>2017-12-18T09:40:04Z</dc:date>
    </item>
  </channel>
</rss>

