<?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 find variables called in a data step? in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/How-to-find-variables-called-in-a-data-step/m-p/695302#M212164</link>
    <description>PROC SCAPROC may be an option but I'm not aware of anything that will tell you only variables references. The ability to use short cut references or macro variables also make it difficult to create a program scanner to do this as well though people have tried. You can find examples of code/log parsers on lexjansen.com</description>
    <pubDate>Thu, 29 Oct 2020 18:23:45 GMT</pubDate>
    <dc:creator>Reeza</dc:creator>
    <dc:date>2020-10-29T18:23:45Z</dc:date>
    <item>
      <title>How to find variables called in a data step?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-find-variables-called-in-a-data-step/m-p/695292#M212161</link>
      <description>&lt;P&gt;How would you find out the fields required by a data step without having to read the code line by line to see what variables are being called?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Oct 2020 17:35:07 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-find-variables-called-in-a-data-step/m-p/695292#M212161</guid>
      <dc:creator>juan1mario</dc:creator>
      <dc:date>2020-10-29T17:35:07Z</dc:date>
    </item>
    <item>
      <title>Re: How to find variables called in a data step?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-find-variables-called-in-a-data-step/m-p/695302#M212164</link>
      <description>PROC SCAPROC may be an option but I'm not aware of anything that will tell you only variables references. The ability to use short cut references or macro variables also make it difficult to create a program scanner to do this as well though people have tried. You can find examples of code/log parsers on lexjansen.com</description>
      <pubDate>Thu, 29 Oct 2020 18:23:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-find-variables-called-in-a-data-step/m-p/695302#M212164</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2020-10-29T18:23:45Z</dc:date>
    </item>
  </channel>
</rss>

