<?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: How to create PROC SQL with conditional macro variables? in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340699#M77917</link>
    <description>Got it.</description>
    <pubDate>Tue, 14 Mar 2017 09:06:06 GMT</pubDate>
    <dc:creator>afiqcjohari</dc:creator>
    <dc:date>2017-03-14T09:06:06Z</dc:date>
    <item>
      <title>How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340686#M77905</link>
      <description>&lt;PRE&gt;%macro extract(condition=);
   proc sql;&lt;BR /&gt;         create table calculatedTable&amp;amp;condition. as
         select count(*) from table
         if &amp;amp;condition. is not null then where var = condition;
   quit;
%mend extract;

*the following should run proc sql count * with the condition;
%extract(condition='a');

*the following should just run a simple sql select count *  ;
%extract();&lt;BR /&gt;&lt;BR /&gt;The previous calls should give 2 tables in the end&lt;/PRE&gt;&lt;P&gt;The 'where' statement should only be available if the parametre condition is supplied with a value.&lt;/P&gt;&lt;P&gt;Is it possible to do this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a series of SQL statements which have a table as an output.&lt;/P&gt;&lt;P&gt;If there's no condition supplied, the SQL statements will have no 'where' condition.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, if a condition is supplied, the same series of SQL statements will run which will have a table as an ouput.&lt;/P&gt;&lt;P&gt;Naturally macro should be a solution but I can't get my head around macro and proc sql to work.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 08:27:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340686#M77905</guid>
      <dc:creator>afiqcjohari</dc:creator>
      <dc:date>2017-03-14T08:27:35Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340689#M77907</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You have to use the macro language %if.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;%macro extract(condition=);
   proc sql;
         create table calculatedTable&amp;amp;condition. as
         select count(*) from table
         %if &amp;amp;condition. ne %then %do;
               where var = &amp;amp;condition.;
         %end;
   quit;
%mend extract;
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 14 Mar 2017 08:33:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340689#M77907</guid>
      <dc:creator>gamotte</dc:creator>
      <dc:date>2017-03-14T08:33:39Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340690#M77908</link>
      <description>&lt;P&gt;Note that if you have several calls with no condition, the same output dataset name will be used and will thus be overwritten. You may want to add a suffix parameter to your macro.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You also made a mistake in the macro call&lt;/P&gt;
&lt;PRE&gt;%extract(condition='a');&lt;/PRE&gt;
&lt;P&gt;should be &lt;/P&gt;
&lt;PRE&gt;%extract(condition=a);&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 08:38:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340690#M77908</guid>
      <dc:creator>gamotte</dc:creator>
      <dc:date>2017-03-14T08:38:38Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340692#M77910</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/30622"&gt;@gamotte&lt;/a&gt; wrote:&lt;BR /&gt;
&lt;P&gt;Note that if you have several calls with no condition, the same output dataset name will be used and will thus be overwritten. You may want to add a suffix parameter to your macro.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You also made a mistake in the macro call&lt;/P&gt;
&lt;PRE&gt;%extract(condition='a');&lt;/PRE&gt;
&lt;P&gt;should be&lt;/P&gt;
&lt;PRE&gt;%extract(condition=a);&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Problem: the quotes are necessary if &lt;FONT face="courier new,courier" color="#3366FF"&gt;var&lt;/FONT&gt; is alphanumeric, so appending a dequoted version of &lt;FONT face="courier new,courier" color="#3366FF"&gt;condition&lt;/FONT&gt; to the dataset-name is recommended.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 08:46:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340692#M77910</guid>
      <dc:creator>andreas_lds</dc:creator>
      <dc:date>2017-03-14T08:46:41Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340695#M77913</link>
      <description>You're right. I thought "a" was the variable name,</description>
      <pubDate>Tue, 14 Mar 2017 08:48:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340695#M77913</guid>
      <dc:creator>gamotte</dc:creator>
      <dc:date>2017-03-14T08:48:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340696#M77914</link>
      <description>calculatedTable&amp;amp;condition. should cover the overwriting issue right? Could you explain what do you mean by suffix parameter here?</description>
      <pubDate>Tue, 14 Mar 2017 08:48:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340696#M77914</guid>
      <dc:creator>afiqcjohari</dc:creator>
      <dc:date>2017-03-14T08:48:31Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340697#M77915</link>
      <description>&lt;P&gt;I answered a bit too fast. Since your input dataset is always the same, there is no use to call&lt;/P&gt;
&lt;P&gt;the macro twice with no condition. If you had an additional parameter for the input table,&lt;/P&gt;
&lt;P&gt;you would have to make sure that two distincts calls give distincts output datasets names,&lt;/P&gt;
&lt;P&gt;either by naming the output dataset according to the one given in input, or by adding a custom&lt;/P&gt;
&lt;P&gt;suffix when no condition is given&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 08:55:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340697#M77915</guid>
      <dc:creator>gamotte</dc:creator>
      <dc:date>2017-03-14T08:55:32Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340699#M77917</link>
      <description>Got it.</description>
      <pubDate>Tue, 14 Mar 2017 09:06:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340699#M77917</guid>
      <dc:creator>afiqcjohari</dc:creator>
      <dc:date>2017-03-14T09:06:06Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340700#M77918</link>
      <description>What's the best tips for if the condition here is a date variable.&lt;BR /&gt;&lt;BR /&gt;I want to pass 01JAN2017 as the starting date for example.</description>
      <pubDate>Tue, 14 Mar 2017 09:06:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340700#M77918</guid>
      <dc:creator>afiqcjohari</dc:creator>
      <dc:date>2017-03-14T09:06:48Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340701#M77919</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/130031"&gt;@afiqcjohari&lt;/a&gt; wrote:&lt;BR /&gt;What's the best tips for if the condition here is a date variable.&lt;BR /&gt;&lt;BR /&gt;I want to pass 01JAN2017 as the starting date for example.&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Depends on how you aquire that date. If you write it literally in your program, you can use the normal method&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;extract(condition='01jan2017'd)&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;If you determine it from some other values, you can pass it as the raw numerical value:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;%startdate=%sysfunc(today());

%extract(condition=&amp;amp;startdate)&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;or you set it from a data step:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data _null_;
set infile;
where /* condition */;
call symput('startdate',put(startdate,best.));
run;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 09:18:47 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340701#M77919</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-03-14T09:18:47Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340702#M77920</link>
      <description>I keep getting 'Apparent symbolic reference not resolved' if I literally put '01jan2017'd as the date variable.&lt;BR /&gt;</description>
      <pubDate>Tue, 14 Mar 2017 09:21:01 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340702#M77920</guid>
      <dc:creator>afiqcjohari</dc:creator>
      <dc:date>2017-03-14T09:21:01Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340703#M77921</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/130031"&gt;@afiqcjohari&lt;/a&gt; wrote:&lt;BR /&gt;I keep getting 'Apparent symbolic reference not resolved' if I literally put '01jan2017'd as the date variable.&lt;BR /&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;BR /&gt;Please post the log, including the macro definition and the macro call.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 09:25:52 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340703#M77921</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-03-14T09:25:52Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340704#M77922</link>
      <description>&lt;P&gt;What is it your&amp;nbsp;&lt;STRONG&gt;actually&lt;/STRONG&gt; trying to achieve here. &amp;nbsp;The reason I ask is that, firstly that code does not add any value to just a base SQL query (i.e. the macro code is totally redundant here), and secondly using the same paramter for a dataset name and where, both of which have very different restrictions on whwta can be put there, will make that code fall over every time it is run. &amp;nbsp;Not a good way to write code. &amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now you mention later that you want to put dates in dataset names, I always treat this as a bad idea for several reasons:&lt;/P&gt;
&lt;P&gt;First, you then need to know what the dataset names are - i.e. they are not fixed, so this makes programming more complex than necessary.&lt;/P&gt;
&lt;P&gt;Secondly, you often want to do calculations on dates, if these appear in the dataset name, you then have to get that, convert it, do the calculations, then convert it back again. &amp;nbsp;All of this again exponentiates the necessary code/maintenance.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So lets say, I need to extract 01jan2014 and 05feb2015 and print them, I could go through the hassel of creating a separate dataset for each, putting date in the name, then doing a mess of macro code to loop over each of the datasets, or I could just do:&lt;/P&gt;
&lt;PRE&gt;data want;
  set have (where=(date in ("01JAN2014"d,"05FEB2015"d)));
run;
proc print data=want;
  by date;
  title "#byval1";
run;&lt;/PRE&gt;
&lt;P&gt;Which code woul you prefer to maintain?&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 09:26:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340704#M77922</guid>
      <dc:creator>RW9</dc:creator>
      <dc:date>2017-03-14T09:26:13Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340706#M77924</link>
      <description>I caught it. It's because i'm trying to run the macro in rsubmit. I've written it so that the SAS server can read the macro.</description>
      <pubDate>Tue, 14 Mar 2017 09:29:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340706#M77924</guid>
      <dc:creator>afiqcjohari</dc:creator>
      <dc:date>2017-03-14T09:29:23Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340707#M77925</link>
      <description>Basically it ends up like this. But it makes me wonder if the rsubmit is a bit redundant..&lt;BR /&gt;&lt;BR /&gt;rsubmit;&lt;BR /&gt;%macro test(mydate=);&lt;BR /&gt;proc sql outobs = 10;&lt;BR /&gt;create table test as&lt;BR /&gt;select * from tablea where&lt;BR /&gt;dTran = &amp;amp;mydate.&lt;BR /&gt;;quit;&lt;BR /&gt;%mend test;&lt;BR /&gt;endrsubmit;&lt;BR /&gt;rsubmit;&lt;BR /&gt;%test(mydate='01jan2017'd);&lt;BR /&gt;endrsubmit;</description>
      <pubDate>Tue, 14 Mar 2017 09:30:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340707#M77925</guid>
      <dc:creator>afiqcjohari</dc:creator>
      <dc:date>2017-03-14T09:30:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340711#M77928</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/130031"&gt;@afiqcjohari&lt;/a&gt; wrote:&lt;BR /&gt;Basically it ends up like this. But it makes me wonder if the rsubmit is a bit redundant..&lt;BR /&gt;&lt;BR /&gt;rsubmit;&lt;BR /&gt;%macro test(mydate=);&lt;BR /&gt;proc sql outobs = 10;&lt;BR /&gt;create table test as&lt;BR /&gt;select * from tablea where&lt;BR /&gt;dTran = &amp;amp;mydate.&lt;BR /&gt;;quit;&lt;BR /&gt;%mend test;&lt;BR /&gt;endrsubmit;&lt;BR /&gt;rsubmit;&lt;BR /&gt;%test(mydate='01jan2017'd);&lt;BR /&gt;endrsubmit;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;rsubmit;

%macro test(mydate=);
proc sql outobs = 10;
create table test as
select * from tablea
where dTran = &amp;amp;mydate.
;
quit;
%mend test;

%test(mydate='01jan2017'd);

endrsubmit; &lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;should also work&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 09:34:18 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340711#M77928</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-03-14T09:34:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340713#M77929</link>
      <description>&lt;P&gt;&lt;IMG src="https://communities.sas.com/t5/image/serverpage/image-id/7724i253DEA294437A7B9/image-size/original?v=1.0&amp;amp;px=-1" border="0" alt="Capture.PNG" title="Capture.PNG" /&gt;&lt;/P&gt;&lt;P&gt;The table above is what I'm trying to achieve. Basically it's just a simple pivot table with the months on the column and some variables on the left. Note that some of the variables can be broken down. For example, variable Spend can be broken into LCY and FCY.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The reason for MACRO is that, I'd need to recreate the same table for another `types`.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can imagine that above table is about FRUITS in general. I'd like then to recreate the same table but for APPLE.&lt;/P&gt;&lt;P&gt;So far, I've been using PROC SQL to calculate the sum(), count(), etc and then use PROC TRANSPOSE to get the time series or pivot table as above.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Though, I like to believe that SAS would have somthing more simpler to generate this kind of report :). Would be very glad if you know how.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2017 09:38:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340713#M77929</guid>
      <dc:creator>afiqcjohari</dc:creator>
      <dc:date>2017-03-14T09:38:24Z</dc:date>
    </item>
    <item>
      <title>Re: How to create PROC SQL with conditional macro variables?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340724#M77930</link>
      <description>&lt;P&gt;Ah, so your imitating some Excel output. &amp;nbsp;Ok, then yes having a macro variable, or macro call is fine, but you don't need to change the internal dataset then:&lt;/P&gt;
&lt;PRE&gt;%macro report (type=);
  
  data want;
    set have (where=(type="&amp;amp;type."));
  run;
 
  proc transpose data=want out=tran_want;
    ...;
  run;

  proc report data=tran_want...;
  run;

%mend report;

%report (type=Apple);
%report (type=Pear);
&lt;/PRE&gt;</description>
      <pubDate>Tue, 14 Mar 2017 10:11:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-create-PROC-SQL-with-conditional-macro-variables/m-p/340724#M77930</guid>
      <dc:creator>RW9</dc:creator>
      <dc:date>2017-03-14T10:11:26Z</dc:date>
    </item>
  </channel>
</rss>

