<?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: PROC GENMOD ERROR  / In General Directing Errors into Macro Variables in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/PROC-GENMOD-ERROR-In-General-Directing-Errors-into-Macro/m-p/93235#M26508</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The success or failure (of most PROC or DATA steps) is stored in the automatic macro variable &amp;amp;SYSERR.&amp;nbsp; This macro variable can be interrogated to determine further processing.&amp;nbsp; Assuming that you are running the GENMOD within a macro loop, checking &amp;amp;SYSERR should be straightforward.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 14 Aug 2012 18:20:34 GMT</pubDate>
    <dc:creator>ArtC</dc:creator>
    <dc:date>2012-08-14T18:20:34Z</dc:date>
    <item>
      <title>PROC GENMOD ERROR  / In General Directing Errors into Macro Variables</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/PROC-GENMOD-ERROR-In-General-Directing-Errors-into-Macro/m-p/93234#M26507</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am running thousands of models in genmod in a search algorithm and I need to identify models that don't converge:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ERROR: The mean parameter is either invalid or at a limit of its range for some observations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And create a macro variable to do conditional statements based on the convergence status. How can I create an indicator macro variable based on the presence of this error?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, in general, if there is a standard methodology for creating macro variables from errors in the log that would be great.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2012 17:29:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/PROC-GENMOD-ERROR-In-General-Directing-Errors-into-Macro/m-p/93234#M26507</guid>
      <dc:creator>mercicle</dc:creator>
      <dc:date>2012-08-14T17:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: PROC GENMOD ERROR  / In General Directing Errors into Macro Variables</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/PROC-GENMOD-ERROR-In-General-Directing-Errors-into-Macro/m-p/93235#M26508</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The success or failure (of most PROC or DATA steps) is stored in the automatic macro variable &amp;amp;SYSERR.&amp;nbsp; This macro variable can be interrogated to determine further processing.&amp;nbsp; Assuming that you are running the GENMOD within a macro loop, checking &amp;amp;SYSERR should be straightforward.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2012 18:20:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/PROC-GENMOD-ERROR-In-General-Directing-Errors-into-Macro/m-p/93235#M26508</guid>
      <dc:creator>ArtC</dc:creator>
      <dc:date>2012-08-14T18:20:34Z</dc:date>
    </item>
    <item>
      <title>Re: PROC GENMOD ERROR  / In General Directing Errors into Macro Variables</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/PROC-GENMOD-ERROR-In-General-Directing-Errors-into-Macro/m-p/93236#M26509</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nice, that will work!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2012 18:28:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/PROC-GENMOD-ERROR-In-General-Directing-Errors-into-Macro/m-p/93236#M26509</guid>
      <dc:creator>mercicle</dc:creator>
      <dc:date>2012-08-14T18:28:53Z</dc:date>
    </item>
  </channel>
</rss>

