<?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 Read-only macro variables in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Read-only-macro-variables/m-p/40441#M8220</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Unfortunately not &lt;img id="smileysad" class="emoticon emoticon-smileysad" src="https://communities.sas.com/i/smilies/16x16_smiley-sad.png" alt="Smiley Sad" title="Smiley Sad" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eric Sun and I looked into a number of protection issues not only for the macro variables, but also for the macros themselves.&amp;nbsp; We were able to come up with a few work arounds, but protecting the variables themselves is still not possible.&amp;nbsp; See the paper at: &lt;/P&gt;&lt;P&gt;&lt;A href="http://www.lexjansen.com/pharmasug/2011/ad/pharmasug-2011-ad17.pdf"&gt;http://www.lexjansen.com/pharmasug/2011/ad/pharmasug-2011-ad17.pdf&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Aug 2011 23:30:42 GMT</pubDate>
    <dc:creator>ArtC</dc:creator>
    <dc:date>2011-08-02T23:30:42Z</dc:date>
    <item>
      <title>Read-only macro variables</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Read-only-macro-variables/m-p/40440#M8219</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to create read only macro variables? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Right now some global macro variables are created in the appserver_autoexec_usermods.sas configuration files. Unfortunately those variables can me modified by all users, causing some trouble when it happens in a stored process ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Aug 2011 15:07:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Read-only-macro-variables/m-p/40440#M8219</guid>
      <dc:creator>andreas_lds</dc:creator>
      <dc:date>2011-08-02T15:07:09Z</dc:date>
    </item>
    <item>
      <title>Read-only macro variables</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Read-only-macro-variables/m-p/40441#M8220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Unfortunately not &lt;img id="smileysad" class="emoticon emoticon-smileysad" src="https://communities.sas.com/i/smilies/16x16_smiley-sad.png" alt="Smiley Sad" title="Smiley Sad" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eric Sun and I looked into a number of protection issues not only for the macro variables, but also for the macros themselves.&amp;nbsp; We were able to come up with a few work arounds, but protecting the variables themselves is still not possible.&amp;nbsp; See the paper at: &lt;/P&gt;&lt;P&gt;&lt;A href="http://www.lexjansen.com/pharmasug/2011/ad/pharmasug-2011-ad17.pdf"&gt;http://www.lexjansen.com/pharmasug/2011/ad/pharmasug-2011-ad17.pdf&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Aug 2011 23:30:42 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Read-only-macro-variables/m-p/40441#M8220</guid>
      <dc:creator>ArtC</dc:creator>
      <dc:date>2011-08-02T23:30:42Z</dc:date>
    </item>
  </channel>
</rss>

