<?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: ERROR: Physical file does not exist, /opt/sasinside/SASConfig/Lev1/SASApp/car.dat. in SAS Studio</title>
    <link>https://communities.sas.com/t5/SAS-Studio/ERROR-Physical-file-does-not-exist-opt-sasinside-SASConfig-Lev1/m-p/246560#M179</link>
    <description>&lt;P&gt;Your INFILE statement specifies only a relative filename, so the SAS process automatically looks for the file in its working directory, which is the location where the SAS process was started.&lt;/P&gt;
&lt;P&gt;In a BI server environment, this is a place in the "configuration tree".&lt;/P&gt;
&lt;P&gt;To avoid this, you need to specify an absolute pathname, starting with a / (meaning that the path starts in the root directory and includes all subdirectory names up to where the file resides).&lt;/P&gt;
&lt;P&gt;Now, if you work with Enterprise Guide and the file resides locally on your PC, you either need to use the import wizard of EG (which automatically transfers the file to the server before running the import data step), or you need to transfer the file yourself to a suitable location on the server (most often your home directory).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To be more specific in helping you, we need further information about your SAS setup.&lt;/P&gt;</description>
    <pubDate>Thu, 28 Jan 2016 07:39:26 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2016-01-28T07:39:26Z</dc:date>
    <item>
      <title>ERROR: Physical file does not exist, /opt/sasinside/SASConfig/Lev1/SASApp/car.dat.</title>
      <link>https://communities.sas.com/t5/SAS-Studio/ERROR-Physical-file-does-not-exist-opt-sasinside-SASConfig-Lev1/m-p/246557#M178</link>
      <description>&lt;DIV class="dijitContentPane dijitBorderContainer-child dijitBorderContainer-dijitContentPane dijitBorderContainerPane dijitAlignCenter dijitContentPaneSingleChild"&gt;&lt;DIV class="dijitBorderContainer dijitContainer row-fluid dijitLayoutContainer"&gt;&lt;DIV class="dijitContentPane dijitAlignCenter dijitContentPaneSingleChild dijitBorderContainer-child dijitBorderContainer-dijitContentPane dijitBorderContainerPane"&gt;&lt;DIV class="tabs dijitBorderContainer dijitContainer dojoDndTarget dijitLayoutContainer sasStudioTabsParentContainer dojoDndContainerOver"&gt;&lt;DIV class="dijitTabContainer dijitTabContainerTop dijitContainer dijitLayoutContainer tabStrip-disabled sasStudioTabsTabContainer sasStudioTabsTabContainerVertical sasStudioTabsTop dijitBorderContainer-child dijitBorderContainer-dijitTabContainerTop dijitBorderContainerPane dijitAlignCenter"&gt;&lt;DIV class="dijitTabPaneWrapper dijitTabContainerTop-container dijitAlignCenter"&gt;&lt;DIV class="dijitTabContainerTopChildWrapper dijitVisible"&gt;&lt;DIV class="dijitBorderContainer dijitContainer sasStudioTabsTabContainerChild dijitTabPane dijitTabContainerTop-child dijitTabContainerTop-dijitBorderContainer dijitLayoutContainer"&gt;&lt;DIV class="dijitBorderContainer dijitContainer dojoDndTarget dijitBorderContainer-child dijitBorderContainer-dijitBorderContainer dijitBorderContainerPane dijitAlignCenter dijitLayoutContainer dojoDndContainerOver"&gt;&lt;DIV class="dijitTabContainer dijitTabContainerTop dijitContainer dijitLayoutContainer tabStrip-disabled sasSuiteTabs dijitBorderContainer-child dijitBorderContainer-dijitTabContainerTop dijitBorderContainerPane dijitAlignCenter"&gt;&lt;DIV class="dijitTabPaneWrapper dijitTabContainerTop-container dijitAlignCenter"&gt;&lt;DIV class="dijitTabContainerTopChildWrapper dijitVisible"&gt;&lt;DIV class="dijitBorderContainer dijitContainer dijitTabPane dijitTabContainerTop-child dijitTabContainerTop-dijitBorderContainer dijitLayoutContainer"&gt;&lt;DIV class="dijitContentPane dijitBorderContainer-child dijitBorderContainer-dijitContentPane dijitBorderContainerPane dijitAlignCenter"&gt;&lt;DIV&gt;&lt;DIV class="sasSource"&gt;1 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;55&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;56 data work.car;&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;57 infile 'car.dat';&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;58 input @ 1 Size&amp;nbsp;$3.&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;59 @ 4 City $15.&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;60 @19 Country $15.;&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;61 run;&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="sasError"&gt;&lt;FONT color="#FF0000"&gt;ERROR: Physical file does not exist, /opt/sasinside/SASConfig/Lev1/SASApp/car.dat.&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;NOTE: The SAS System stopped processing this step because of errors.&lt;/DIV&gt;&lt;DIV class="sasWarning"&gt;WARNING: The data set WORK.car may be incomplete. When this step was stopped there were 0 observations and 3 variables.&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;NOTE: DATA statement used (Total process time):&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;real time 0.01 seconds&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;cpu time 0.00 seconds&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;62&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;63 proc print data=work.car;&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;64 run;&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;NOTE: No observations in data set WORK.car.&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;NOTE: PROCEDURE PRINT used (Total process time):&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;real time 0.00 seconds&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;cpu time 0.00 seconds&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="sasNote"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;65&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;66&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;67&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;68 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;&lt;/DIV&gt;&lt;DIV class="sasSource"&gt;80&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class="dijitContentPane statusBar dijitBorderContainer-child dijitBorderContainer-dijitContentPane dijitBorderContainerPane dijitAlignBottom"&gt;&lt;SPAN&gt;&lt;SPAN class="statusBarMessage"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class="dijitContentPane statusBar dijitBorderContainer-child dijitBorderContainer-dijitContentPane dijitBorderContainerPane dijitAlignBottom"&gt;&lt;FONT color="#000000"&gt;&lt;SPAN&gt;&lt;SPAN class="statusBarMessage"&gt;Anyone knows how to fixed it? by the way, I use mac. I follow the guide to set up and add to myfolder to a share&amp;nbsp;&lt;SPAN&gt;folder.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 28 Jan 2016 07:12:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/ERROR-Physical-file-does-not-exist-opt-sasinside-SASConfig-Lev1/m-p/246557#M178</guid>
      <dc:creator>Anthonytien</dc:creator>
      <dc:date>2016-01-28T07:12:27Z</dc:date>
    </item>
    <item>
      <title>Re: ERROR: Physical file does not exist, /opt/sasinside/SASConfig/Lev1/SASApp/car.dat.</title>
      <link>https://communities.sas.com/t5/SAS-Studio/ERROR-Physical-file-does-not-exist-opt-sasinside-SASConfig-Lev1/m-p/246560#M179</link>
      <description>&lt;P&gt;Your INFILE statement specifies only a relative filename, so the SAS process automatically looks for the file in its working directory, which is the location where the SAS process was started.&lt;/P&gt;
&lt;P&gt;In a BI server environment, this is a place in the "configuration tree".&lt;/P&gt;
&lt;P&gt;To avoid this, you need to specify an absolute pathname, starting with a / (meaning that the path starts in the root directory and includes all subdirectory names up to where the file resides).&lt;/P&gt;
&lt;P&gt;Now, if you work with Enterprise Guide and the file resides locally on your PC, you either need to use the import wizard of EG (which automatically transfers the file to the server before running the import data step), or you need to transfer the file yourself to a suitable location on the server (most often your home directory).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To be more specific in helping you, we need further information about your SAS setup.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2016 07:39:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/ERROR-Physical-file-does-not-exist-opt-sasinside-SASConfig-Lev1/m-p/246560#M179</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2016-01-28T07:39:26Z</dc:date>
    </item>
    <item>
      <title>Re: ERROR: Physical file does not exist, /opt/sasinside/SASConfig/Lev1/SASApp/car.dat.</title>
      <link>https://communities.sas.com/t5/SAS-Studio/ERROR-Physical-file-does-not-exist-opt-sasinside-SASConfig-Lev1/m-p/246678#M180</link>
      <description>&lt;P&gt;If you set up the myfolders properly, you would not see a warning on the SAS Studio start up page, otherwise you see a warning. You should also be able to navigate to it on the left hand Folders menu.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Assuming&amp;nbsp;the above is true, you can change your infile statement as follows:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt; infile '/folders/myfolders/car.dat';&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;PS. It has to be myfolders, with the s, and I believe its also case sensitive.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jan 2016 16:27:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/ERROR-Physical-file-does-not-exist-opt-sasinside-SASConfig-Lev1/m-p/246678#M180</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2016-01-28T16:27:06Z</dc:date>
    </item>
  </channel>
</rss>

