<?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: Failing code in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300209#M60508</link>
    <description>&lt;P&gt;You still haven't told us what's not working.&lt;/P&gt;</description>
    <pubDate>Thu, 22 Sep 2016 20:17:48 GMT</pubDate>
    <dc:creator>Reeza</dc:creator>
    <dc:date>2016-09-22T20:17:48Z</dc:date>
    <item>
      <title>Failing code</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300195#M60502</link>
      <description>&lt;P&gt;create table work.OUTP2 as&lt;BR /&gt;select * , 'BLANK' as Completion_Status,&lt;BR /&gt;'BLANK COMPLETION STATUS' as ERROR_MESSAGE&lt;BR /&gt;&amp;nbsp; from &amp;amp;_INPUT1 (drop=Completion_Status)&lt;BR /&gt;&amp;nbsp;where Completion_status_no=0 ;&lt;BR /&gt;quit;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2016 19:40:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300195#M60502</guid>
      <dc:creator>YB1</dc:creator>
      <dc:date>2016-09-22T19:40:05Z</dc:date>
    </item>
    <item>
      <title>Re: Failing code</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300199#M60503</link>
      <description>&lt;P&gt;Ok. How does it fail?&lt;/P&gt;
&lt;P&gt;Post your code and log.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2016 19:46:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300199#M60503</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2016-09-22T19:46:35Z</dc:date>
    </item>
    <item>
      <title>Re: Failing code</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300200#M60504</link>
      <description>&lt;P&gt;Other than not seeing a Proc SQL; at the start&lt;/P&gt;
&lt;P&gt;what is the value of &amp;amp;_input1? Does it actually match an existing data set?&lt;/P&gt;
&lt;P&gt;Does that data set actually have any records where Completion_status_no=0?&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2016 19:50:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300200#M60504</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2016-09-22T19:50:26Z</dc:date>
    </item>
    <item>
      <title>Re: Failing code</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300202#M60505</link>
      <description>&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;/* ADM.HRSC.TRNG.TR.Fully */
%if (&amp;amp;_COST_OBJECT eq ADM.HRSC.TRNG.TR.Fully) %then
%do;
proc sql;
create table &amp;amp;_OUTPUT1 as
select distinct COST_OBJECT,
BUSINESS_LINE_CODE,
BUSINESS_LINE,
NEW_DIER_CODE,
'ADM.HR' as SourceDIER,
'# of Training Classes' as DriverName,
sum(Completion_status_no) as VOLUME,
Location
from &amp;amp;_INPUT1
where Completion_status_no=1
group by
COST_OBJECT,
BUSINESS_LINE_CODE,
BUSINESS_LINE,
NEW_DIER_CODE, Location;


create table work.OUTP2 as
select * , 'BLANK' as Completion_Status,
'BLANK COMPLETION STATUS' as ERROR_MESSAGE
from &amp;amp;_INPUT1 (drop=Completion_Status)
where Completion_status_no=0
quit;
%end;
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;BR /&gt;##- Please type your reply above this line. Simple formatting, no&lt;BR /&gt;attachments. -##&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2016 20:16:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300202#M60505</guid>
      <dc:creator>YB1</dc:creator>
      <dc:date>2016-09-22T20:16:16Z</dc:date>
    </item>
    <item>
      <title>Re: Failing code</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300209#M60508</link>
      <description>&lt;P&gt;You still haven't told us what's not working.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2016 20:17:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300209#M60508</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2016-09-22T20:17:48Z</dc:date>
    </item>
    <item>
      <title>Re: Failing code</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300219#M60510</link>
      <description>&lt;P&gt;The code is part of a macro program.&lt;/P&gt;&lt;P&gt;The problem could be somewhere else in the macro.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Better show the whole code and the log.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2016 20:52:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300219#M60510</guid>
      <dc:creator>Shmuel</dc:creator>
      <dc:date>2016-09-22T20:52:57Z</dc:date>
    </item>
    <item>
      <title>Re: Failing code</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300258#M60512</link>
      <description>&lt;P&gt;Create global macro variables such as&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;%let _INPUT1=MYDS;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;and test the SQL or DATA steps outside of your macro. You should be able to pinpoint the troublesome step by checking the log. If every step works as intended, then the problem is with macro logic.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Sep 2016 01:50:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Failing-code/m-p/300258#M60512</guid>
      <dc:creator>PGStats</dc:creator>
      <dc:date>2016-09-23T01:50:58Z</dc:date>
    </item>
  </channel>
</rss>

