<?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: Read SAS log in current program in SAS studio in SAS Studio</title>
    <link>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/510139#M6492</link>
    <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/201978"&gt;@Rushikeshvm&lt;/a&gt;if you happen to find a nice way to read extremely long SAS log into SAS datasets let the rest of know.&amp;nbsp; I have been working with the same request and mining for words is a real pain.&amp;nbsp; I have ran into issue with memory overflow, and those tailored process that do seem to work at time don't always work on other log layouts,&lt;/P&gt;</description>
    <pubDate>Sat, 03 Nov 2018 11:34:39 GMT</pubDate>
    <dc:creator>VDD</dc:creator>
    <dc:date>2018-11-03T11:34:39Z</dc:date>
    <item>
      <title>Read SAS log in current program in SAS studio</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449861#M5038</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am working on SAS Studio and I have an issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I wish to create a SAS macro that will read the SAS log of the current program and check it for any issues. I have gone through various papers but all of them refer to the external file saved as *.log.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the option or procedure to read the SAS log of my current program and check for the issues?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rhushikesh&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Mar 2018 07:22:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449861#M5038</guid>
      <dc:creator>Rushikeshvm</dc:creator>
      <dc:date>2018-03-30T07:22:31Z</dc:date>
    </item>
    <item>
      <title>Re: Read SAS log in current program in SAS studio</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449864#M5039</link>
      <description>&lt;P&gt;None. But you can check the automatic macro variables &amp;amp;syscc, &amp;amp;syserr and so on.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Alternatively, you could configure the workspace server logging so that a more expanded logfile is written on the server, and read that. But that requires write permissions for the SAS configuration and in-depth knowledge for the changes in logconfig.xml. Or the cooperation of your SAS admin.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Mar 2018 07:51:14 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449864#M5039</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-03-30T07:51:14Z</dc:date>
    </item>
    <item>
      <title>Re: Read SAS log in current program in SAS studio</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449865#M5040</link>
      <description>&lt;P&gt;1) You can save the log of any part of your program or the whole log using PROC PRINTTO.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; Start with&amp;nbsp;&lt;STRONG&gt;proc printto log=&amp;lt;path and filename&amp;gt;; run;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; Close the log with:&amp;nbsp;&lt;STRONG&gt;rproc printto; run;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/STRONG&gt;then read the file and check it using text functions like: scan, index, find etc.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2) You can check, instream the program or by special step, are there any errors by&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;checking system macro variables: &amp;amp;sysrc, &amp;amp;syserr - and some more (check in SAS documentation).&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Mar 2018 07:53:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449865#M5040</guid>
      <dc:creator>Shmuel</dc:creator>
      <dc:date>2018-03-30T07:53:05Z</dc:date>
    </item>
    <item>
      <title>Re: Read SAS log in current program in SAS studio</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449871#M5041</link>
      <description>&lt;P&gt;The problem with the proc printto approach is that it redirects all log output, so you don't get it in the log window of SAS Studio.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Mar 2018 08:49:17 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449871#M5041</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-03-30T08:49:17Z</dc:date>
    </item>
    <item>
      <title>Re: Read SAS log in current program in SAS studio</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449889#M5042</link>
      <description>&lt;P&gt;Thank you very much for your inputs. So, we don't&amp;nbsp;have a procedure to extract the log of the current program.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Mar 2018 11:51:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449889#M5042</guid>
      <dc:creator>Rushikeshvm</dc:creator>
      <dc:date>2018-03-30T11:51:11Z</dc:date>
    </item>
    <item>
      <title>Re: Read SAS log in current program in SAS studio</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449890#M5043</link>
      <description>&lt;P&gt;Thank You,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But I am looking for a way to read the log of the current program the time it executes.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Mar 2018 11:51:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449890#M5043</guid>
      <dc:creator>Rushikeshvm</dc:creator>
      <dc:date>2018-03-30T11:51:57Z</dc:date>
    </item>
    <item>
      <title>Re: Read SAS log in current program in SAS studio</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449892#M5044</link>
      <description>&lt;P&gt;EG and SAS Studio check the log for ERRORs and WARNINGs by themselves, alerting you with a small red x or a yellow exclamation mark.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Inspecting the log and making sense of it (for all other NOTEs and messages) is still a job for us humans. Especially during development; once a job runs in production batch mode, checking the log automatically for certain phrases does make sense.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Mar 2018 12:01:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/449892#M5044</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-03-30T12:01:32Z</dc:date>
    </item>
    <item>
      <title>Re: Read SAS log in current program in SAS studio</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/510139#M6492</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/201978"&gt;@Rushikeshvm&lt;/a&gt;if you happen to find a nice way to read extremely long SAS log into SAS datasets let the rest of know.&amp;nbsp; I have been working with the same request and mining for words is a real pain.&amp;nbsp; I have ran into issue with memory overflow, and those tailored process that do seem to work at time don't always work on other log layouts,&lt;/P&gt;</description>
      <pubDate>Sat, 03 Nov 2018 11:34:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Read-SAS-log-in-current-program-in-SAS-studio/m-p/510139#M6492</guid>
      <dc:creator>VDD</dc:creator>
      <dc:date>2018-11-03T11:34:39Z</dc:date>
    </item>
  </channel>
</rss>

