<?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: One question about STORED COMPILED MACRO in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/One-question-about-STORED-COMPILED-MACRO/m-p/607559#M176653</link>
    <description>&lt;P&gt;You need to use a time window where no SAS session is running that has the sasmstore option set to this catalog. That's the disadvantage of using compiled macros. If you use the autocall library, you do not have that problem.&lt;/P&gt;</description>
    <pubDate>Wed, 27 Nov 2019 07:13:52 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2019-11-27T07:13:52Z</dc:date>
    <item>
      <title>One question about STORED COMPILED MACRO</title>
      <link>https://communities.sas.com/t5/SAS-Programming/One-question-about-STORED-COMPILED-MACRO/m-p/607554#M176649</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Recently, I encountered a problem about macro storage.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I generate a catalog with the following program:&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;libname MyMacros "&amp;amp;ProjDir.\&amp;amp;Deliver.\Data\SDTM\MetaData";
options mstored sasmstore=MyMacros;
data _null_;
    set MacroList;
    call execute('%include "'||strip(MacroList)||'";');
run; 

proc catalog cat=MyMacros.sasmacr;
    contents;
run;
quit;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Then the&amp;nbsp;sasmacr.sas7bcat was created at target path.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, whenever I want to update the catalog, if anyone opens sas and reads this catalog, it always reminds me that the file is locked and cannot be updated, which annoy me a lot. I won't be able to update until everyone turns sas off.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="catalog.png" style="width: 577px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/34266i0E340C021893907F/image-size/large?v=v2&amp;amp;px=999" role="button" title="catalog.png" alt="catalog.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So have anyone ever encountered this problem? How to update catalog when locked.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks~&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2019 06:39:47 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/One-question-about-STORED-COMPILED-MACRO/m-p/607554#M176649</guid>
      <dc:creator>Lee_wan</dc:creator>
      <dc:date>2019-11-27T06:39:47Z</dc:date>
    </item>
    <item>
      <title>Re: One question about STORED COMPILED MACRO</title>
      <link>https://communities.sas.com/t5/SAS-Programming/One-question-about-STORED-COMPILED-MACRO/m-p/607559#M176653</link>
      <description>&lt;P&gt;You need to use a time window where no SAS session is running that has the sasmstore option set to this catalog. That's the disadvantage of using compiled macros. If you use the autocall library, you do not have that problem.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2019 07:13:52 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/One-question-about-STORED-COMPILED-MACRO/m-p/607559#M176653</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2019-11-27T07:13:52Z</dc:date>
    </item>
  </channel>
</rss>

