<?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: Iterate over %EM_NOMINAL_INPUT, %EM_ORDINAL_INPUT and %EM_BINARY_INPUT in SAS Data Science</title>
    <link>https://communities.sas.com/t5/SAS-Data-Science/Iterate-over-EM-NOMINAL-INPUT-EM-ORDINAL-INPUT-and-EM-BINARY/m-p/386154#M5710</link>
    <description>&lt;P&gt;These macros were defined as macros rather than as macro variables due to their (potentially) excessive length. &amp;nbsp; They are computed from the metadata passed to the SAS Code node when the SAS Code node runs so you would not be able to iterate within the SAS Code node and expect those values to change; however, those values would be defined and updated for any node the SAS Code node was connected to. &amp;nbsp; Using them allows you to use generic code that will work in a wide variety of places. &amp;nbsp; Most of the iterative methods available from using the Group Processing nodes in SAS Enterprise Miner would not likely benefit from these differences, however, so it really depends on what you are trying to do. &amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Cordially,&lt;/P&gt;
&lt;P&gt;Doug&lt;/P&gt;</description>
    <pubDate>Mon, 07 Aug 2017 21:25:32 GMT</pubDate>
    <dc:creator>DougWielenga</dc:creator>
    <dc:date>2017-08-07T21:25:32Z</dc:date>
    <item>
      <title>Iterate over %EM_NOMINAL_INPUT, %EM_ORDINAL_INPUT and %EM_BINARY_INPUT</title>
      <link>https://communities.sas.com/t5/SAS-Data-Science/Iterate-over-EM-NOMINAL-INPUT-EM-ORDINAL-INPUT-and-EM-BINARY/m-p/348123#M5190</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How can I capture the variables returnd by %EM_NOMINAL_INPUT, %EM_ORDINAL_INPUT and %EM_BINARY_INPUT and insert them (the names) in a DATASET.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can't iterate with scan because the length of the string returned by those macros is larger than &lt;SPAN&gt;65534.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Apr 2017 14:33:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Science/Iterate-over-EM-NOMINAL-INPUT-EM-ORDINAL-INPUT-and-EM-BINARY/m-p/348123#M5190</guid>
      <dc:creator>rmlmrmlm</dc:creator>
      <dc:date>2017-04-07T14:33:24Z</dc:date>
    </item>
    <item>
      <title>Re: Iterate over %EM_NOMINAL_INPUT, %EM_ORDINAL_INPUT and %EM_BINARY_INPUT</title>
      <link>https://communities.sas.com/t5/SAS-Data-Science/Iterate-over-EM-NOMINAL-INPUT-EM-ORDINAL-INPUT-and-EM-BINARY/m-p/386154#M5710</link>
      <description>&lt;P&gt;These macros were defined as macros rather than as macro variables due to their (potentially) excessive length. &amp;nbsp; They are computed from the metadata passed to the SAS Code node when the SAS Code node runs so you would not be able to iterate within the SAS Code node and expect those values to change; however, those values would be defined and updated for any node the SAS Code node was connected to. &amp;nbsp; Using them allows you to use generic code that will work in a wide variety of places. &amp;nbsp; Most of the iterative methods available from using the Group Processing nodes in SAS Enterprise Miner would not likely benefit from these differences, however, so it really depends on what you are trying to do. &amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Cordially,&lt;/P&gt;
&lt;P&gt;Doug&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2017 21:25:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Science/Iterate-over-EM-NOMINAL-INPUT-EM-ORDINAL-INPUT-and-EM-BINARY/m-p/386154#M5710</guid>
      <dc:creator>DougWielenga</dc:creator>
      <dc:date>2017-08-07T21:25:32Z</dc:date>
    </item>
  </channel>
</rss>

