<?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 compilation by SASATUOS in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/macro-compilation-by-SASATUOS/m-p/679331#M205124</link>
    <description>&lt;P&gt;If only 2 out of the 20 macros are in DEV then assign option SASAUTOS so that DEV will be in priority:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;options mautosource sasautos=("x/global/dev" "y/global/prod" sasautos); &lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;if a macro is not in DEV sas will look in PROD, and if it is not neither there it will look for in in SASAUTOS.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A better way is, each debuged macro should be moved from DEV to PROD when upgrading is completed.&lt;/P&gt;</description>
    <pubDate>Wed, 26 Aug 2020 03:23:26 GMT</pubDate>
    <dc:creator>Shmuel</dc:creator>
    <dc:date>2020-08-26T03:23:26Z</dc:date>
    <item>
      <title>macro compilation by SASATUOS</title>
      <link>https://communities.sas.com/t5/SAS-Programming/macro-compilation-by-SASATUOS/m-p/679320#M205120</link>
      <description>&lt;P&gt;Hello Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am stuck with loading of macro ,which one is already located in another folder.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One of path ("/x/global/prod") have 20 macros are there and 2 macros are in another folder "Y/global/dev");&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need to first compile 20 macros and after compile 2 macros located in another folder .&lt;/P&gt;&lt;P&gt;Note: The 2 macros are in Dev folder are already in Prod folder , but i need to use 2 macros from dev folder because those ones are new one and i want use rest 18 macros from Prod folder.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;when i use SASAUTOS option it's not compile 2 macros located in Dev folder and it's coming from Prod folder only&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;my code :&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;options mautosource sasautos=("x/global/prod" "y/global/dev" sasautos); &lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2020 01:48:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/macro-compilation-by-SASATUOS/m-p/679320#M205120</guid>
      <dc:creator>raja777pharma</dc:creator>
      <dc:date>2020-08-26T01:48:44Z</dc:date>
    </item>
    <item>
      <title>Re: macro compilation by SASATUOS</title>
      <link>https://communities.sas.com/t5/SAS-Programming/macro-compilation-by-SASATUOS/m-p/679331#M205124</link>
      <description>&lt;P&gt;If only 2 out of the 20 macros are in DEV then assign option SASAUTOS so that DEV will be in priority:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;options mautosource sasautos=("x/global/dev" "y/global/prod" sasautos); &lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;if a macro is not in DEV sas will look in PROD, and if it is not neither there it will look for in in SASAUTOS.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A better way is, each debuged macro should be moved from DEV to PROD when upgrading is completed.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2020 03:23:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/macro-compilation-by-SASATUOS/m-p/679331#M205124</guid>
      <dc:creator>Shmuel</dc:creator>
      <dc:date>2020-08-26T03:23:26Z</dc:date>
    </item>
    <item>
      <title>Re: macro compilation by SASATUOS</title>
      <link>https://communities.sas.com/t5/SAS-Programming/macro-compilation-by-SASATUOS/m-p/679378#M205135</link>
      <description>&lt;P&gt;The first macro found is the one executed.&lt;/P&gt;
&lt;P&gt;Put the DEV path first in the SASAUTOS path list.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, please correct the typo in the thread title.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2020 08:39:07 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/macro-compilation-by-SASATUOS/m-p/679378#M205135</guid>
      <dc:creator>ChrisNZ</dc:creator>
      <dc:date>2020-08-26T08:39:07Z</dc:date>
    </item>
    <item>
      <title>Re: macro compilation by SASATUOS</title>
      <link>https://communities.sas.com/t5/SAS-Programming/macro-compilation-by-SASATUOS/m-p/679408#M205153</link>
      <description>&lt;P&gt;If both folders contain all 22 macros, you have a problem that SASAUTOS can't solve.&amp;nbsp; You would need to use a combination of tools:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;%include 'y/global/dev/first_dev_macro.sas';
%include 'y/global/dev/second_dev_macro.sas'
options sasautos=('x/global/prod' sasautos);&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;If the prod folder contains only 20 of the 22 macros, then your original approach is correct.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2020 12:06:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/macro-compilation-by-SASATUOS/m-p/679408#M205153</guid>
      <dc:creator>Astounding</dc:creator>
      <dc:date>2020-08-26T12:06:40Z</dc:date>
    </item>
    <item>
      <title>Re: macro compilation by SASATUOS</title>
      <link>https://communities.sas.com/t5/SAS-Programming/macro-compilation-by-SASATUOS/m-p/679458#M205178</link>
      <description>Also try append system optionlibname x v9 'c:\temp\';&lt;BR /&gt;options append=(sasautos=(x sasautos)) ;.&lt;BR /&gt;</description>
      <pubDate>Wed, 26 Aug 2020 13:31:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/macro-compilation-by-SASATUOS/m-p/679458#M205178</guid>
      <dc:creator>Ksharp</dc:creator>
      <dc:date>2020-08-26T13:31:57Z</dc:date>
    </item>
  </channel>
</rss>

