<?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: Macro Error -  Physical file does not exist, /sas/config/Lev1/SASApp/IN_DAT in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Macro-Error-Physical-file-does-not-exist-sas-config-Lev1-SASApp/m-p/409971#M100205</link>
    <description>&lt;P&gt;It is extremely likely that the macro code will need to be modified. Things like paths to files often should be parameters that can be changed as needed, such as this case.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You'll likely need to show the code for the macro for more specific suggestions.&lt;/P&gt;
&lt;P&gt;Paste the code from the SAS editor into a code box on the forum opened using the {I} menu icon.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The note you show is sometimes associated with opening a second SAS session when one is already active. Some of your configuration information is then unavailable. That could also be related to the issue at hand.&lt;/P&gt;</description>
    <pubDate>Thu, 02 Nov 2017 19:09:41 GMT</pubDate>
    <dc:creator>ballardw</dc:creator>
    <dc:date>2017-11-02T19:09:41Z</dc:date>
    <item>
      <title>Macro Error -  Physical file does not exist, /sas/config/Lev1/SASApp/IN_DAT</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Macro-Error-Physical-file-does-not-exist-sas-config-Lev1-SASApp/m-p/409961#M100204</link>
      <description>&lt;P&gt;This code is embedded inside of a macro, where the file location somehow changed from what the code states.&amp;nbsp; Is there a way to fix within the Toolbar -Options of SAS Enterprise Guide or something that will need to changed within the Management Console?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;EM&gt;&lt;STRONG&gt;CODE:&lt;/STRONG&gt; &lt;/EM&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;　&lt;/P&gt;&lt;P&gt;%&lt;I&gt;get_filenames&lt;/I&gt;(/sas/data/imports);&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;EM&gt;&lt;STRONG&gt;LOG:&lt;/STRONG&gt; &lt;/EM&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;　&lt;/P&gt;&lt;P&gt;NOTE: Unable to open parameter catalog: SASUSER.PARMS.PARMS.SLIST in update mode. Temporary parameter values will be saved to&lt;/P&gt;&lt;P&gt;WORK.PARMS.PARMS.SLIST.&lt;/P&gt;&lt;P&gt;ERROR: Physical file does not exist, /sas/config/Lev1/SASApp/IN_DAT.&lt;/P&gt;&lt;P&gt;ERROR: Import unsuccessful. See SAS Log for details.&lt;/P&gt;&lt;P&gt;NOTE: The SAS System stopped processing this step because of errors.&lt;/P&gt;&lt;P&gt;NOTE: PROCEDURE IMPORT used (Total process time):&lt;/P&gt;&lt;P&gt;real time 0.32 seconds&lt;/P&gt;&lt;P&gt;cpu time 0.03 seconds&lt;/P&gt;</description>
      <pubDate>Thu, 02 Nov 2017 18:42:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Macro-Error-Physical-file-does-not-exist-sas-config-Lev1-SASApp/m-p/409961#M100204</guid>
      <dc:creator>tobyfarms</dc:creator>
      <dc:date>2017-11-02T18:42:58Z</dc:date>
    </item>
    <item>
      <title>Re: Macro Error -  Physical file does not exist, /sas/config/Lev1/SASApp/IN_DAT</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Macro-Error-Physical-file-does-not-exist-sas-config-Lev1-SASApp/m-p/409971#M100205</link>
      <description>&lt;P&gt;It is extremely likely that the macro code will need to be modified. Things like paths to files often should be parameters that can be changed as needed, such as this case.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You'll likely need to show the code for the macro for more specific suggestions.&lt;/P&gt;
&lt;P&gt;Paste the code from the SAS editor into a code box on the forum opened using the {I} menu icon.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The note you show is sometimes associated with opening a second SAS session when one is already active. Some of your configuration information is then unavailable. That could also be related to the issue at hand.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Nov 2017 19:09:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Macro-Error-Physical-file-does-not-exist-sas-config-Lev1-SASApp/m-p/409971#M100205</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2017-11-02T19:09:41Z</dc:date>
    </item>
    <item>
      <title>Re: Macro Error -  Physical file does not exist, /sas/config/Lev1/SASApp/IN_DAT</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Macro-Error-Physical-file-does-not-exist-sas-config-Lev1-SASApp/m-p/409973#M100206</link>
      <description>&lt;P&gt;Given this error message:&lt;/P&gt;
&lt;PRE&gt;ERROR: Physical file does not exist, /sas/config/Lev1/SASApp/IN_DAT.&lt;/PRE&gt;
&lt;P&gt;Then most likely the current working directory for your SAS session is&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;/sas/config/Lev1/SASApp/&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;And your program tried to open a file named "IN_DAT".&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Perhaps you meant to reference a fileref that had been created with a FILENAME statement and accidentally added quotes around the name so that SAS thought you were providing a physical name instead of the logic fileref?&lt;/P&gt;
&lt;P&gt;If that is not it then give it a fully qualified path to the file and not just "IN_DAT".&lt;/P&gt;</description>
      <pubDate>Thu, 02 Nov 2017 19:19:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Macro-Error-Physical-file-does-not-exist-sas-config-Lev1-SASApp/m-p/409973#M100206</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2017-11-02T19:19:50Z</dc:date>
    </item>
    <item>
      <title>Re: Macro Error -  Physical file does not exist, /sas/config/Lev1/SASApp/IN_DAT</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Macro-Error-Physical-file-does-not-exist-sas-config-Lev1-SASApp/m-p/409979#M100207</link>
      <description>&lt;P&gt;You're working on a SAS server, somehow the path you're trying to use isn't recognized. Navigate to the path using the File Viewer in EG and then find the path it expects, I think it's under properties.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Nov 2017 19:33:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Macro-Error-Physical-file-does-not-exist-sas-config-Lev1-SASApp/m-p/409979#M100207</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2017-11-02T19:33:58Z</dc:date>
    </item>
  </channel>
</rss>

