<?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 sql: conditional programming in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457148#M115878</link>
    <description>&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Is the 60 day interval any 60 days? That does make the problem a lot harder...&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Impeccable and can't agree more.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/129748"&gt;@Pooja2&lt;/a&gt;&amp;nbsp;does it have to be in proc sql? Coz in datastep it's far easier to take each row date as begin date for a 60 day period&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 25 Apr 2018 04:08:54 GMT</pubDate>
    <dc:creator>novinosrin</dc:creator>
    <dc:date>2018-04-25T04:08:54Z</dc:date>
    <item>
      <title>Proc sql: conditional programming</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457143#M115874</link>
      <description>&lt;P&gt;I have this data and i have to find out which customer purchased more than 40 items during any 60 day. I am unable to find the logic.. please help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;customer ID&lt;/TD&gt;&lt;TD&gt;date&lt;/TD&gt;&lt;TD&gt;no of items purchased&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2333A&lt;/TD&gt;&lt;TD&gt;24-May-07&lt;/TD&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2333A&lt;/TD&gt;&lt;TD&gt;27-Jun-07&lt;/TD&gt;&lt;TD&gt;5&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2333A&lt;/TD&gt;&lt;TD&gt;8-Jul-07&lt;/TD&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2333A&lt;/TD&gt;&lt;TD&gt;9-Jul-07&lt;/TD&gt;&lt;TD&gt;8&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2333A&lt;/TD&gt;&lt;TD&gt;20-Jul-07&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2333A&lt;/TD&gt;&lt;TD&gt;25-Jun-07&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2333A&lt;/TD&gt;&lt;TD&gt;30-Jun-07&lt;/TD&gt;&lt;TD&gt;7&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2333A&lt;/TD&gt;&lt;TD&gt;5-Jul-07&lt;/TD&gt;&lt;TD&gt;6&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2333A&lt;/TD&gt;&lt;TD&gt;7-Jul-07&lt;/TD&gt;&lt;TD&gt;1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;5643D&lt;/TD&gt;&lt;TD&gt;24-May-07&lt;/TD&gt;&lt;TD&gt;5&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;5643D&lt;/TD&gt;&lt;TD&gt;27-Jun-07&lt;/TD&gt;&lt;TD&gt;5&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;5643D&lt;/TD&gt;&lt;TD&gt;8-Jul-07&lt;/TD&gt;&lt;TD&gt;5&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;5643D&lt;/TD&gt;&lt;TD&gt;9-Jul-07&lt;/TD&gt;&lt;TD&gt;5&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;5643D&lt;/TD&gt;&lt;TD&gt;20-Jul-07&lt;/TD&gt;&lt;TD&gt;5&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;5643D&lt;/TD&gt;&lt;TD&gt;25-Jun-07&lt;/TD&gt;&lt;TD&gt;6&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;5643D&lt;/TD&gt;&lt;TD&gt;30-Jun-07&lt;/TD&gt;&lt;TD&gt;7&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;5643D&lt;/TD&gt;&lt;TD&gt;5-Jul-07&lt;/TD&gt;&lt;TD&gt;5&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;5643D&lt;/TD&gt;&lt;TD&gt;7-Jul-07&lt;/TD&gt;&lt;TD&gt;1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;5643D&lt;/TD&gt;&lt;TD&gt;18-May-07&lt;/TD&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;5643D&lt;/TD&gt;&lt;TD&gt;20-Jun-07&lt;/TD&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2287C&lt;/TD&gt;&lt;TD&gt;25-Jun-07&lt;/TD&gt;&lt;TD&gt;4&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2287C&lt;/TD&gt;&lt;TD&gt;30-Jun-07&lt;/TD&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2287C&lt;/TD&gt;&lt;TD&gt;5-Jul-07&lt;/TD&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Wed, 25 Apr 2018 03:05:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457143#M115874</guid>
      <dc:creator>Pooja2</dc:creator>
      <dc:date>2018-04-25T03:05:45Z</dc:date>
    </item>
    <item>
      <title>Re: Proc sql: conditional programming</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457144#M115875</link>
      <description>&lt;P&gt;How big is your data?&lt;/P&gt;
&lt;P&gt;Is the 60 day interval any 60 days? That does make the problem a lot harder...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Essentially you do a SELF JOIN using the date interval and checking 60 day interval in either direction each time.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Apr 2018 03:09:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457144#M115875</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2018-04-25T03:09:26Z</dc:date>
    </item>
    <item>
      <title>Re: Proc sql: conditional programming</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457148#M115878</link>
      <description>&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Is the 60 day interval any 60 days? That does make the problem a lot harder...&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Impeccable and can't agree more.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/129748"&gt;@Pooja2&lt;/a&gt;&amp;nbsp;does it have to be in proc sql? Coz in datastep it's far easier to take each row date as begin date for a 60 day period&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Apr 2018 04:08:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457148#M115878</guid>
      <dc:creator>novinosrin</dc:creator>
      <dc:date>2018-04-25T04:08:54Z</dc:date>
    </item>
    <item>
      <title>Re: Proc sql: conditional programming</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457149#M115879</link>
      <description>Here's an idea  (that might kill your machine if your data is too big):&lt;BR /&gt;Create a multilabel format with all possible 60 day intervals that can reside in your data set.&lt;BR /&gt;Run PROC SUMMARY using that format&lt;BR /&gt;Filter out your top consumers.</description>
      <pubDate>Wed, 25 Apr 2018 04:14:18 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457149#M115879</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2018-04-25T04:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: Proc sql: conditional programming</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457159#M115883</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/129748"&gt;@Pooja2&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;Below code should return what you're asking for. If it will perform sufficiently depends very much&amp;nbsp;&lt;SPAN&gt;on the data volumes you're dealing with as well as the place where the data resides (SAS tables or data base).&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;
proc sql;
  create table want as
  select
    customer_id,
    max(n_items_sum60) as max_n_items_sum60
    from
      (
        select
          o.customer_id,
          (
            select sum(i.n_items_purchased)
            from have i
            where i.customer_id=o.customer_id and o.date between i.date-60 and i.date+60
          )
            as n_items_sum60
        from have as o
      )
    group by customer_id
    having max_n_items_sum60&amp;gt;40
  ;
quit;
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 25 Apr 2018 05:54:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457159#M115883</guid>
      <dc:creator>Patrick</dc:creator>
      <dc:date>2018-04-25T05:54:16Z</dc:date>
    </item>
    <item>
      <title>Re: Proc sql: conditional programming</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457200#M115901</link>
      <description>&lt;P&gt;Here is a way to do it. Not sure how well it scales. If you have large amounts of data, a data step solution may be faster:&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data have;
input customer_ID $/date date9./NoOfItems;
format date date9.;
cards;
2333A
24-May-07
3
2333A
27-Jun-07
5
2333A
8-Jul-07
3
2333A
9-Jul-07
8
2333A
20-Jul-07
9
2333A
25-Jun-07
9
2333A
30-Jun-07
7
2333A
5-Jul-07
6
2333A
7-Jul-07
1
5643D
24-May-07
5
5643D
27-Jun-07
5
5643D
8-Jul-07
5
5643D
9-Jul-07
5
5643D
20-Jul-07
5
5643D
25-Jun-07
6
5643D
30-Jun-07
7
5643D
5-Jul-07
5
5643D
7-Jul-07
1
5643D
18-May-07
2
5643D
20-Jun-07
2
2287C
25-Jun-07
4
2287C
30-Jun-07
2
2287C
5-Jul-07
3
;run;
proc sql;
  create table Sixty_sum
    as select Customer_id,date,(select sum(NoOfItems) from have
                                where Customer_id=outer.Customer_ID
                                  and date between outer.Date and outer.Date+59) as NoOfItems60
    from have as outer
    having calculated NoOfItems60&amp;gt;40
     ;

&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 25 Apr 2018 10:04:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457200#M115901</guid>
      <dc:creator>s_lassen</dc:creator>
      <dc:date>2018-04-25T10:04:51Z</dc:date>
    </item>
    <item>
      <title>Re: Proc sql: conditional programming</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457205#M115904</link>
      <description>&lt;P&gt;I m gonna try out the solutions mentioned here and would post whether i got the results or not. I do have 36000 obs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 25 Apr 2018 10:39:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457205#M115904</guid>
      <dc:creator>Pooja2</dc:creator>
      <dc:date>2018-04-25T10:39:06Z</dc:date>
    </item>
    <item>
      <title>Re: Proc sql: conditional programming</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457289#M115926</link>
      <description>&lt;P&gt;This solution represents an important recognition of the requirements.&amp;nbsp; You don't need to look backwards.&amp;nbsp; You only need to look forwards (date + 59).&amp;nbsp; The reason:&amp;nbsp; if looking backwards would find a set of days that totaled 40+ items, you would find that same set of days by looking forward only.&amp;nbsp; You would just find it based on an earlier observation for the same customer.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In a DATA step, you wouldn't need the full Cartesian product, although the programming becomes a bit messy.&amp;nbsp; If needed:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;proc sort data=have;&lt;/P&gt;
&lt;P&gt;by custid date;&lt;/P&gt;
&lt;P&gt;run;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Then take advantage of the order to the observations.&amp;nbsp; (This does not necessarily mean that it runs faster than SQL ... only testing would reveal that):&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;data want (where=(bought_40_flag = 1));&lt;/P&gt;
&lt;P&gt;set have nobs=n_obs;&lt;/P&gt;
&lt;P&gt;by custid date;&lt;/P&gt;
&lt;P&gt;if first.custid then do;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; total_items = n_items;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; if n_items &amp;lt; 40 then bought_40_flag = 0;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;else do;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; bought_40_flag=1;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; output;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; end;&lt;/P&gt;
&lt;P&gt;end;&lt;/P&gt;
&lt;P&gt;retain bought_40_flag;&lt;/P&gt;
&lt;P&gt;if bought_40_flag=0 and _n_ &amp;lt; n_obs then do next_obs = _n_+1 to n_obs;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; set have (rename=(custid = next_custid date = next_date)) point=next_obs;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; if custid = next_custid and (next_date - date) &amp;lt; 60 then do;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; total_items + n_items;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; if total_items &amp;gt;= 40 then do;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; bought_40_flag=1;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; output;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; return;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; end;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; end;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; else return;&amp;nbsp; /* now at next customer or beyond 60 day limit */&lt;/P&gt;
&lt;P&gt;end;&lt;/P&gt;
&lt;P&gt;run;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Like I said, it's messy.&amp;nbsp; It's also untested, so I hope I got it right but it might need a little tweaking.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Apr 2018 13:59:01 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457289#M115926</guid>
      <dc:creator>Astounding</dc:creator>
      <dc:date>2018-04-25T13:59:01Z</dc:date>
    </item>
    <item>
      <title>Re: Proc sql: conditional programming</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457761#M116101</link>
      <description>&lt;P&gt;it doesn't have to be sql. it could be datastep. So far none of the solutions suggested worked.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Apr 2018 14:20:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457761#M116101</guid>
      <dc:creator>Pooja2</dc:creator>
      <dc:date>2018-04-26T14:20:38Z</dc:date>
    </item>
    <item>
      <title>Re: Proc sql: conditional programming</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457765#M116103</link>
      <description>&lt;P&gt;my dataset has almost 36k obs and it would be helpful if you could give me the logic in he form of code so that I can test first before running my original data.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Apr 2018 14:27:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457765#M116103</guid>
      <dc:creator>Pooja2</dc:creator>
      <dc:date>2018-04-26T14:27:45Z</dc:date>
    </item>
    <item>
      <title>Re: Proc sql: conditional programming</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457766#M116104</link>
      <description>&lt;P&gt;also it is any 60 day period.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Apr 2018 14:28:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457766#M116104</guid>
      <dc:creator>Pooja2</dc:creator>
      <dc:date>2018-04-26T14:28:30Z</dc:date>
    </item>
    <item>
      <title>Re: Proc sql: conditional programming</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457971#M116187</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/129748"&gt;@Pooja2&lt;/a&gt; wrote:&lt;BR /&gt;
&lt;P&gt;it doesn't have to be sql. it could be datastep. So far none of the solutions suggested worked.&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;How do they not work?&lt;/P&gt;</description>
      <pubDate>Thu, 26 Apr 2018 21:36:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/457971#M116187</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2018-04-26T21:36:38Z</dc:date>
    </item>
    <item>
      <title>Re: Proc sql: conditional programming</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/458147#M116241</link>
      <description>&lt;P&gt;This should be working. I will update in a day or two.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 27 Apr 2018 14:38:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Proc-sql-conditional-programming/m-p/458147#M116241</guid>
      <dc:creator>Pooja2</dc:creator>
      <dc:date>2018-04-27T14:38:08Z</dc:date>
    </item>
  </channel>
</rss>

