<?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: Working with code and messages errors in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Working-with-code-and-messages-errors/m-p/6500#M2078</link>
    <description>To start with,&lt;BR /&gt;
&lt;BR /&gt;
various return and status codes for SAS are available through predefined macro variables:&lt;BR /&gt;
&lt;BR /&gt;
SYSERR, SYSFILRC, SYSLIBRC, SYSRC, SYSCC&lt;BR /&gt;
&lt;BR /&gt;
SYSERR = "Contains a return code status set by some SAS procedures and the DATA step"&lt;BR /&gt;
&lt;BR /&gt;
Check your SAS Macro Language Reference documentation for detailed descriptions.&lt;BR /&gt;
&lt;BR /&gt;
Email is more involved, but can be done, I believe via the ODS system.  I believe it requires an email account, password, access/knowledge of the email server. But, once set up , it is easy to compose and send an email from within SAS.

Message was edited by: Chuck</description>
    <pubDate>Wed, 23 Jan 2008 20:54:16 GMT</pubDate>
    <dc:creator>deleted_user</dc:creator>
    <dc:date>2008-01-23T20:54:16Z</dc:date>
    <item>
      <title>Working with code and messages errors</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Working-with-code-and-messages-errors/m-p/6499#M2077</link>
      <description>I have a process in SAS with many data steps. I want to check the return code (rc) after which data step processing and if the rc is different to 0 then the system sends a e-mail with the code and message of error. How may I do this?&lt;BR /&gt;
Thank you</description>
      <pubDate>Wed, 23 Jan 2008 17:43:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Working-with-code-and-messages-errors/m-p/6499#M2077</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2008-01-23T17:43:08Z</dc:date>
    </item>
    <item>
      <title>Re: Working with code and messages errors</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Working-with-code-and-messages-errors/m-p/6500#M2078</link>
      <description>To start with,&lt;BR /&gt;
&lt;BR /&gt;
various return and status codes for SAS are available through predefined macro variables:&lt;BR /&gt;
&lt;BR /&gt;
SYSERR, SYSFILRC, SYSLIBRC, SYSRC, SYSCC&lt;BR /&gt;
&lt;BR /&gt;
SYSERR = "Contains a return code status set by some SAS procedures and the DATA step"&lt;BR /&gt;
&lt;BR /&gt;
Check your SAS Macro Language Reference documentation for detailed descriptions.&lt;BR /&gt;
&lt;BR /&gt;
Email is more involved, but can be done, I believe via the ODS system.  I believe it requires an email account, password, access/knowledge of the email server. But, once set up , it is easy to compose and send an email from within SAS.

Message was edited by: Chuck</description>
      <pubDate>Wed, 23 Jan 2008 20:54:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Working-with-code-and-messages-errors/m-p/6500#M2078</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2008-01-23T20:54:16Z</dc:date>
    </item>
    <item>
      <title>Re: Working with code and messages errors</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Working-with-code-and-messages-errors/m-p/6501#M2079</link>
      <description>Hi:&lt;BR /&gt;
  Previous forum postings are available on the topic of ODS and email and email with the FILENAME email engine:&lt;BR /&gt;
&lt;A href="http://support.sas.com/forums/thread.jspa?messageID=6780᩼" target="_blank"&gt;http://support.sas.com/forums/thread.jspa?messageID=6780᩼&lt;/A&gt;&lt;BR /&gt;
&lt;A href="http://support.sas.com/forums/thread.jspa?messageID=4421ᅅ" target="_blank"&gt;http://support.sas.com/forums/thread.jspa?messageID=4421ᅅ&lt;/A&gt;&lt;BR /&gt;
&lt;A href="http://support.sas.com/forums/thread.jspa?messageID=5990ᝦ" target="_blank"&gt;http://support.sas.com/forums/thread.jspa?messageID=5990ᝦ&lt;/A&gt;&lt;BR /&gt;
 &lt;BR /&gt;
  and Tech Support has other examples posted. There is a documentation topic (listed in one of the above posts) that also outlines the various email methods.&lt;BR /&gt;
 &lt;BR /&gt;
cynthia</description>
      <pubDate>Wed, 23 Jan 2008 22:48:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Working-with-code-and-messages-errors/m-p/6501#M2079</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2008-01-23T22:48:58Z</dc:date>
    </item>
    <item>
      <title>Re: Working with code and messages errors</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Working-with-code-and-messages-errors/m-p/6502#M2080</link>
      <description>There are many resources to tell you how to send email from a SAS session, and you would do well to read widely among the available notes and papers.&lt;BR /&gt;
&lt;BR /&gt;
A couple of traps are out there however.  The first is that if you try to do something in a data step that causes a SAS error, like reference a file that doesn't exist, then SAS will set Obs to 0 and go into debugging mode.  As a result, any subsequent step that tries to process data; like a Data _NULL_  to send an email, will not work.  Be careful of the system return codes too, make sure you understand how each one works, and where it will not tell you what you think it does.  Carefully Read The Factual Material.&lt;BR /&gt;
&lt;BR /&gt;
The second issue to consider is the problem(s) caused by using an email client such as Outlook to send your email.  Not only will you probably encounter their puerile "A program is trying to send email" message box, but you are prone to have your email address "Interpreted" by the Outlook address book.  The general solution is to use SMTP to send the email but this opens some security issues with the Post Office, and is often not allowed by your system administrators.&lt;BR /&gt;
&lt;BR /&gt;
You can solve each of these problems, but be aware that it may not be, or remain simple.</description>
      <pubDate>Wed, 23 Jan 2008 23:43:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Working-with-code-and-messages-errors/m-p/6502#M2080</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2008-01-23T23:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: Working with code and messages errors</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Working-with-code-and-messages-errors/m-p/6503#M2081</link>
      <description>Hi Chuck, dkvj and Cynthia@sas&lt;BR /&gt;
&lt;BR /&gt;
Thanks for your help!&lt;BR /&gt;
&lt;BR /&gt;
Best Regards&lt;BR /&gt;
Fernando Santos

Message was edited by: FernandoSantos</description>
      <pubDate>Thu, 24 Jan 2008 10:47:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Working-with-code-and-messages-errors/m-p/6503#M2081</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2008-01-24T10:47:25Z</dc:date>
    </item>
  </channel>
</rss>

