<?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: source code for session compiled macro in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/source-code-for-session-compiled-macro/m-p/163525#M31681</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It depends on how you compiled/stored the macro. "session compiled macro" is not specific enough for us to tell how you compiled it:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Did you just compile the macro (without the /store option) to the WORK.SASMACR catalog? If so, you might be in trouble.&lt;/LI&gt;&lt;LI&gt;Did you store it in a non-WORK catalog, using the MSTORED option, and %macro xyz / store option? If so you might be in luck.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Another thought - why did the Enhanced Editor close suddenly? If SAS crashed, it may not have cleared your WORK folder, so you might at least be able to retrieve the sasmacr.sasb7cat file and stick it somewhere where you could re-invoke the macro and examine the log (as explained in &lt;A __default_attr="255172" __jive_macro_name="user" class="jive_macro jive_macro_user" data-objecttype="3" href="https://communities.sas.com/"&gt;&lt;/A&gt;'s reply.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Other suggestions to avoid future repetition:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Set your SAS startup options to have an ALTLOG keep a copy of everything you generate. (But remember to purge it periodically..)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Keep your macros as *.sas files somewhere whilst developing&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;EM&gt;Anyone with other macro best-practice suggestions?&lt;/EM&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 29 Sep 2014 07:20:19 GMT</pubDate>
    <dc:creator>AndrewHowell</dc:creator>
    <dc:date>2014-09-29T07:20:19Z</dc:date>
    <item>
      <title>source code for session compiled macro</title>
      <link>https://communities.sas.com/t5/SAS-Programming/source-code-for-session-compiled-macro/m-p/163522#M31678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;session compiled macro&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Macro created and able to invoke and getting the result of&amp;nbsp; macro But enhance editor closed mistakenly.&lt;/P&gt;&lt;P&gt;Question:&amp;nbsp; How to get the source code of my macro&amp;nbsp; (As session not closed, entry in the catalog exists)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Sep 2014 06:06:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/source-code-for-session-compiled-macro/m-p/163522#M31678</guid>
      <dc:creator>rajeshm</dc:creator>
      <dc:date>2014-09-29T06:06:39Z</dc:date>
    </item>
    <item>
      <title>Re: source code for session compiled macro</title>
      <link>https://communities.sas.com/t5/SAS-Programming/source-code-for-session-compiled-macro/m-p/163523#M31679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;%Copy &lt;/P&gt;&lt;P&gt;See example in docs&lt;/P&gt;&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/mcrolref/61885/HTML/default/viewer.htm#a002582616.htm" title="http://support.sas.com/documentation/cdl/en/mcrolref/61885/HTML/default/viewer.htm#a002582616.htm"&gt;SAS(R) 9.2 Macro Language: Reference&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Sep 2014 06:58:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/source-code-for-session-compiled-macro/m-p/163523#M31679</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2014-09-29T06:58:27Z</dc:date>
    </item>
    <item>
      <title>Re: source code for session compiled macro</title>
      <link>https://communities.sas.com/t5/SAS-Programming/source-code-for-session-compiled-macro/m-p/163524#M31680</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Or call macro with mprint source symbolgen options. A bit of work to decipher but better than losing it all. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Sep 2014 07:02:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/source-code-for-session-compiled-macro/m-p/163524#M31680</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2014-09-29T07:02:31Z</dc:date>
    </item>
    <item>
      <title>Re: source code for session compiled macro</title>
      <link>https://communities.sas.com/t5/SAS-Programming/source-code-for-session-compiled-macro/m-p/163525#M31681</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It depends on how you compiled/stored the macro. "session compiled macro" is not specific enough for us to tell how you compiled it:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Did you just compile the macro (without the /store option) to the WORK.SASMACR catalog? If so, you might be in trouble.&lt;/LI&gt;&lt;LI&gt;Did you store it in a non-WORK catalog, using the MSTORED option, and %macro xyz / store option? If so you might be in luck.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Another thought - why did the Enhanced Editor close suddenly? If SAS crashed, it may not have cleared your WORK folder, so you might at least be able to retrieve the sasmacr.sasb7cat file and stick it somewhere where you could re-invoke the macro and examine the log (as explained in &lt;A __default_attr="255172" __jive_macro_name="user" class="jive_macro jive_macro_user" data-objecttype="3" href="https://communities.sas.com/"&gt;&lt;/A&gt;'s reply.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Other suggestions to avoid future repetition:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Set your SAS startup options to have an ALTLOG keep a copy of everything you generate. (But remember to purge it periodically..)&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Keep your macros as *.sas files somewhere whilst developing&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;EM&gt;Anyone with other macro best-practice suggestions?&lt;/EM&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Sep 2014 07:20:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/source-code-for-session-compiled-macro/m-p/163525#M31681</guid>
      <dc:creator>AndrewHowell</dc:creator>
      <dc:date>2014-09-29T07:20:19Z</dc:date>
    </item>
  </channel>
</rss>

