<?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: Getting ODS status information programmatically in ODS and Base Reporting</title>
    <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Getting-ODS-status-information-programmatically/m-p/108#M22</link>
    <description>Mike,&lt;BR /&gt;
&lt;BR /&gt;
  That question will be directly addressed at SUGI.  That's a definite interest of ours in Base/ODS R&amp;amp;D.&lt;BR /&gt;
&lt;BR /&gt;
  -- David Kelley, SAS</description>
    <pubDate>Tue, 14 Mar 2006 15:52:43 GMT</pubDate>
    <dc:creator>David_SAS</dc:creator>
    <dc:date>2006-03-14T15:52:43Z</dc:date>
    <item>
      <title>Getting ODS status information programmatically</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Getting-ODS-status-information-programmatically/m-p/107#M21</link>
      <description>One question that has come up periodically on SAS-L (e.g. Paul Walker posting of Jan 10 2006) is how a program can (or could in the future if there are enhancements) get information about the status of ODS.  Paul specifically wanted to be able to find out in a macro whether the LISTING destination was open or closed, so that he could restore it to its previous state at the end of his macro.  Certainly there are other items of information that would be useful to have.</description>
      <pubDate>Tue, 14 Mar 2006 14:05:07 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/Getting-ODS-status-information-programmatically/m-p/107#M21</guid>
      <dc:creator>MikeRhoads</dc:creator>
      <dc:date>2006-03-14T14:05:07Z</dc:date>
    </item>
    <item>
      <title>Re: Getting ODS status information programmatically</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Getting-ODS-status-information-programmatically/m-p/108#M22</link>
      <description>Mike,&lt;BR /&gt;
&lt;BR /&gt;
  That question will be directly addressed at SUGI.  That's a definite interest of ours in Base/ODS R&amp;amp;D.&lt;BR /&gt;
&lt;BR /&gt;
  -- David Kelley, SAS</description>
      <pubDate>Tue, 14 Mar 2006 15:52:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/Getting-ODS-status-information-programmatically/m-p/108#M22</guid>
      <dc:creator>David_SAS</dc:creator>
      <dc:date>2006-03-14T15:52:43Z</dc:date>
    </item>
    <item>
      <title>Re: Getting ODS status information programmatically</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Getting-ODS-status-information-programmatically/m-p/109#M23</link>
      <description>I'm also interested in this.  I remember having a discussion about it at a GeekFest with one of the developers, and it's pretty hard to do - there might be many output destinations open, each with different settings, including tagsets with loads of user variables. &lt;BR /&gt;
&lt;BR /&gt;
ODS is really an amazing system.  If you've looked at how other programs create multiple forms of output, SAS really stands out in its ease of use (yeah, tagsets are hard, but no harder than XML formatting).</description>
      <pubDate>Tue, 14 Mar 2006 17:04:33 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/Getting-ODS-status-information-programmatically/m-p/109#M23</guid>
      <dc:creator>JackHamilton</dc:creator>
      <dc:date>2006-03-14T17:04:33Z</dc:date>
    </item>
  </channel>
</rss>

