<?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: SAS Log doesn't update after repeated use of break function in Base SAS in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/SAS-Log-doesn-t-update-after-repeated-use-of-break-function-in/m-p/468189#M119557</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/38137"&gt;@DeepakSwain&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good question. You're not the only one who has run into this problem. Does it help to redirect the log (maybe back and forth) using PROC PRINTTO?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If it's just because of the WORK datasets (and possibly formats), this inelegant workaround might help:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;By setting&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;options noworkterm;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;you prevent SAS from erasing the existing work library on termination.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Then you could start a new SAS session and move datasets, the work format catalog and what else can be moved from the old work library to the new one. This should not take much time as long as both directories reside on the same disk partition (which depends on your environment and option settings), so that the data are not physically rewritten.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Remaining issues, however, might be that libnames, filenames, macro variables, option settings etc. need to be restored in the new session. (Some companies have macros to store/restore all that session-specific information.)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 06 Jun 2018 20:56:06 GMT</pubDate>
    <dc:creator>FreelanceReinh</dc:creator>
    <dc:date>2018-06-06T20:56:06Z</dc:date>
    <item>
      <title>SAS Log doesn't update after repeated use of break function in Base SAS</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Log-doesn-t-update-after-repeated-use-of-break-function-in/m-p/468160#M119548</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am working a dataset having more than 3 million records. Following use of break tab couple of times, I noticed that log doesn't update. I believe following restart of session, I will overcome the problem easily. As I am having number of temporary tables in WORK, I don't want to restart the session. Is there any way to overcome the issue without restarting SAS session.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance for your kind reply.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jun 2018 18:19:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Log-doesn-t-update-after-repeated-use-of-break-function-in/m-p/468160#M119548</guid>
      <dc:creator>DeepakSwain</dc:creator>
      <dc:date>2018-06-06T18:19:34Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Log doesn't update after repeated use of break function in Base SAS</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Log-doesn-t-update-after-repeated-use-of-break-function-in/m-p/468189#M119557</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/38137"&gt;@DeepakSwain&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good question. You're not the only one who has run into this problem. Does it help to redirect the log (maybe back and forth) using PROC PRINTTO?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If it's just because of the WORK datasets (and possibly formats), this inelegant workaround might help:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;By setting&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;options noworkterm;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;you prevent SAS from erasing the existing work library on termination.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Then you could start a new SAS session and move datasets, the work format catalog and what else can be moved from the old work library to the new one. This should not take much time as long as both directories reside on the same disk partition (which depends on your environment and option settings), so that the data are not physically rewritten.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Remaining issues, however, might be that libnames, filenames, macro variables, option settings etc. need to be restored in the new session. (Some companies have macros to store/restore all that session-specific information.)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jun 2018 20:56:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Log-doesn-t-update-after-repeated-use-of-break-function-in/m-p/468189#M119557</guid>
      <dc:creator>FreelanceReinh</dc:creator>
      <dc:date>2018-06-06T20:56:06Z</dc:date>
    </item>
  </channel>
</rss>

