<?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 Unique row Identifier in distributed LASR Server. in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Unique-row-Identifier-in-distributed-LASR-Server/m-p/602632#M174487</link>
    <description>&lt;P&gt;I am trying to add a Unique row identifier to a large data set that is loaded into memory in the LASR server that is distributed over 32 nodes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When i use _N_ it counts the rows as it sees them in each thread but the end result is a non-unique row number.&amp;nbsp; Also it doesn't seem like _ThreadID_ is a valid variable in LASR server data steps like it is in CAS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;current program:&lt;/P&gt;&lt;P&gt;Data mylasr.out; set mylasr.in;&lt;/P&gt;&lt;P&gt;rownum=_N_;&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I searched and couldn't find this info anywhere...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thoughts?&lt;/P&gt;</description>
    <pubDate>Thu, 07 Nov 2019 21:31:00 GMT</pubDate>
    <dc:creator>Bromlem</dc:creator>
    <dc:date>2019-11-07T21:31:00Z</dc:date>
    <item>
      <title>Unique row Identifier in distributed LASR Server.</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Unique-row-Identifier-in-distributed-LASR-Server/m-p/602632#M174487</link>
      <description>&lt;P&gt;I am trying to add a Unique row identifier to a large data set that is loaded into memory in the LASR server that is distributed over 32 nodes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When i use _N_ it counts the rows as it sees them in each thread but the end result is a non-unique row number.&amp;nbsp; Also it doesn't seem like _ThreadID_ is a valid variable in LASR server data steps like it is in CAS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;current program:&lt;/P&gt;&lt;P&gt;Data mylasr.out; set mylasr.in;&lt;/P&gt;&lt;P&gt;rownum=_N_;&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I searched and couldn't find this info anywhere...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thoughts?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Nov 2019 21:31:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Unique-row-Identifier-in-distributed-LASR-Server/m-p/602632#M174487</guid>
      <dc:creator>Bromlem</dc:creator>
      <dc:date>2019-11-07T21:31:00Z</dc:date>
    </item>
    <item>
      <title>Re: Unique row Identifier in distributed LASR Server.</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Unique-row-Identifier-in-distributed-LASR-Server/m-p/602638#M174489</link>
      <description>&lt;P&gt;The only solution I can think of would be to go back to your non-distributed source table, add the unique row Identifier, then reload the table into distributed LASR.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Nov 2019 22:05:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Unique-row-Identifier-in-distributed-LASR-Server/m-p/602638#M174489</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2019-11-07T22:05:12Z</dc:date>
    </item>
    <item>
      <title>Re: Unique row Identifier in distributed LASR Server.</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Unique-row-Identifier-in-distributed-LASR-Server/m-p/602653#M174497</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/170533"&gt;@Bromlem&lt;/a&gt;:&lt;/P&gt;
&lt;P&gt;I am &lt;EM&gt;not sure&lt;/EM&gt; whether using CUROBS= option instead of _N_ will help in your situation. But I suspect that it quite possibly &lt;EM&gt;might&lt;/EM&gt; because while _N_ has nothing to do with the input data set per se (it's just populated at the top of the implied DATA step loop with the number of its current iteration from an internal counter), the variable assigned to CUROBS= is linked with the physical row numbers of the data set specified in the SET statement. In fact, it reflects them accurately even in the case there's a WHERE clause or observations marked for deletion. So, what the heck, give it a shot (the variable Q will be auto-dropped):&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;data mylasr.out ;                                                                                                                       
  set mylasr.in &lt;FONT color="#0000FF"&gt;&lt;STRONG&gt;curobs = q&lt;/STRONG&gt;&lt;/FONT&gt; ;                                                                                                       
  rownum = &lt;FONT color="#0000FF"&gt;&lt;STRONG&gt;q&lt;/STRONG&gt;&lt;/FONT&gt; ;                                                                                                                     
run ;
&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp; For the sake of curiosity, you can also try the MONOTONIC() function, though I'd be very surprised if it worked:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;data mylasr.out ;                                                                                                                       
  set mylasr.in ;                                                                                                       
  rownum = &lt;FONT color="#0000FF"&gt;&lt;STRONG&gt;monotonic()&lt;/STRONG&gt;&lt;/FONT&gt; ;                                                                                                                     
run ;&lt;/PRE&gt;
&lt;P&gt;It will be interesting to see what you will have discovered.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind regards&lt;/P&gt;
&lt;P&gt;Paul D.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Nov 2019 23:50:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Unique-row-Identifier-in-distributed-LASR-Server/m-p/602653#M174497</guid>
      <dc:creator>hashman</dc:creator>
      <dc:date>2019-11-07T23:50:24Z</dc:date>
    </item>
    <item>
      <title>Re: Unique row Identifier in distributed LASR Server.</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Unique-row-Identifier-in-distributed-LASR-Server/m-p/602658#M174498</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/21262"&gt;@hashman&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the ideas!&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately it seems like curobs= option in the set statement is not possible in the LASR engine.&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://attachment.outlook.live.net/owa/Bromley_mike@hotmail.com/service.svc/s/GetAttachmentThumbnail?id=AQMkADAwATZiZmYAZC05NTUAYS1hNThkLTAwAi0wMAoARgAAA03CTxb9AnlOoQTz6ulQoHoHAC%2F6lNiTNMtBgSaQBH%2Bqk%2B0AAAIBDAAAAC%2F6lNiTNMtBgSaQBH%2Bqk%2B0AAyTPQtIAAAABEgAQANXjZFmyrmdMgXFtyyDtB8M%3D&amp;amp;thumbnailType=2&amp;amp;owa=outlook.live.com&amp;amp;scriptVer=2019102702.17&amp;amp;isc=1&amp;amp;X-OWA-CANARY=paxCGp2l5kaxtQDPLULpSgCiE0bqY9cYAFpixkJwC6U9Kz_IuNaVKo9oi804Rjf68NUeu9DGpww.&amp;amp;token=eyJhbGciOiJSUzI1NiIsImtpZCI6IjA2MDBGOUY2NzQ2MjA3MzdFNzM0MDRFMjg3QzQ1QTgxOENCN0NFQjgiLCJ4NXQiOiJCZ0Q1OW5SaUJ6Zm5OQVRpaDhSYWdZeTN6cmciLCJ0eXAiOiJKV1QifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2subGl2ZS5jb20iLCJ2ZXIiOiJFeGNoYW5nZS5DYWxsYmFjay5WMSIsImFwcGN0eHNlbmRlciI6Ik93YURvd25sb2FkQDg0ZGY5ZTdmLWU5ZjYtNDBhZi1iNDM1LWFhYWFhYWFhYWFhYSIsImlzc3JpbmciOiJXVyIsImFwcGN0eCI6IntcIm1zZXhjaHByb3RcIjpcIm93YVwiLFwicHJpbWFyeXNpZFwiOlwiUy0xLTI4MjctNDQyMzY1LTI1MDU3NDU4MDVcIixcInB1aWRcIjpcIjE4OTk5NDU3MTM2NDA4NDVcIixcIm9pZFwiOlwiMDAwNmJmZmQtOTU1YS1hNThkLTAwMDAtMDAwMDAwMDAwMDAwXCIsXCJzY29wZVwiOlwiT3dhRG93bmxvYWRcIn0iLCJuYmYiOjE1NzMxNzYyMDYsImV4cCI6MTU3MzE3NjgwNiwiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQDg0ZGY5ZTdmLWU5ZjYtNDBhZi1iNDM1LWFhYWFhYWFhYWFhYSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50Lm91dGxvb2subGl2ZS5uZXRAODRkZjllN2YtZTlmNi00MGFmLWI0MzUtYWFhYWFhYWFhYWFhIn0.kGgiZhRS4azmeCpv-X-rvG1_UXRXfI6VuxCach5pKoslT1TUvwUaRD8_MgB84gedyLDwSLs3wK7mawmtmN_PCaaLgavj27QUCOTdX60OpKaDav59L-blMDZAp7GelTLTwWhonRLnalN6OmS2LY-uUVVbzYZUA6S1ly673Hv-ixgl0MGByiLmonsJFasP7EwycVc4peCBCVVnzlwfHh4Eq8XxICNNNb5wIZrTQU0GtWN5m1Fs1HCg2KJHsPJmaHE5LnVzLFCawKFPWdFnMDEK_qYWmyEnTVk761IkjmFveKcnW2m6pJmoesJFDvSht9K6qx6aj-xPk2T1hcDzNrkyCQ&amp;amp;animation=true" border="0" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also the monotonic() function is not recognized when attempting to execute in LASR, so brings back to grid work space and executes.&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://attachment.outlook.live.net/owa/Bromley_mike@hotmail.com/service.svc/s/GetAttachmentThumbnail?id=AQMkADAwATZiZmYAZC05NTUAYS1hNThkLTAwAi0wMAoARgAAA03CTxb9AnlOoQTz6ulQoHoHAC%2F6lNiTNMtBgSaQBH%2Bqk%2B0AAAIBDAAAAC%2F6lNiTNMtBgSaQBH%2Bqk%2B0AAyTPQtIAAAABEgAQALc3m%2BfGX9VHkSAiExztMcQ%3D&amp;amp;thumbnailType=2&amp;amp;owa=outlook.live.com&amp;amp;scriptVer=2019102702.17&amp;amp;isc=1&amp;amp;X-OWA-CANARY=paxCGp2l5kaxtQDPLULpSgCiE0bqY9cYAFpixkJwC6U9Kz_IuNaVKo9oi804Rjf68NUeu9DGpww.&amp;amp;token=eyJhbGciOiJSUzI1NiIsImtpZCI6IjA2MDBGOUY2NzQ2MjA3MzdFNzM0MDRFMjg3QzQ1QTgxOENCN0NFQjgiLCJ4NXQiOiJCZ0Q1OW5SaUJ6Zm5OQVRpaDhSYWdZeTN6cmciLCJ0eXAiOiJKV1QifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2subGl2ZS5jb20iLCJ2ZXIiOiJFeGNoYW5nZS5DYWxsYmFjay5WMSIsImFwcGN0eHNlbmRlciI6Ik93YURvd25sb2FkQDg0ZGY5ZTdmLWU5ZjYtNDBhZi1iNDM1LWFhYWFhYWFhYWFhYSIsImlzc3JpbmciOiJXVyIsImFwcGN0eCI6IntcIm1zZXhjaHByb3RcIjpcIm93YVwiLFwicHJpbWFyeXNpZFwiOlwiUy0xLTI4MjctNDQyMzY1LTI1MDU3NDU4MDVcIixcInB1aWRcIjpcIjE4OTk5NDU3MTM2NDA4NDVcIixcIm9pZFwiOlwiMDAwNmJmZmQtOTU1YS1hNThkLTAwMDAtMDAwMDAwMDAwMDAwXCIsXCJzY29wZVwiOlwiT3dhRG93bmxvYWRcIn0iLCJuYmYiOjE1NzMxNzYyMDYsImV4cCI6MTU3MzE3NjgwNiwiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQDg0ZGY5ZTdmLWU5ZjYtNDBhZi1iNDM1LWFhYWFhYWFhYWFhYSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50Lm91dGxvb2subGl2ZS5uZXRAODRkZjllN2YtZTlmNi00MGFmLWI0MzUtYWFhYWFhYWFhYWFhIn0.kGgiZhRS4azmeCpv-X-rvG1_UXRXfI6VuxCach5pKoslT1TUvwUaRD8_MgB84gedyLDwSLs3wK7mawmtmN_PCaaLgavj27QUCOTdX60OpKaDav59L-blMDZAp7GelTLTwWhonRLnalN6OmS2LY-uUVVbzYZUA6S1ly673Hv-ixgl0MGByiLmonsJFasP7EwycVc4peCBCVVnzlwfHh4Eq8XxICNNNb5wIZrTQU0GtWN5m1Fs1HCg2KJHsPJmaHE5LnVzLFCawKFPWdFnMDEK_qYWmyEnTVk761IkjmFveKcnW2m6pJmoesJFDvSht9K6qx6aj-xPk2T1hcDzNrkyCQ&amp;amp;animation=true" border="0" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Nov 2019 01:25:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Unique-row-Identifier-in-distributed-LASR-Server/m-p/602658#M174498</guid>
      <dc:creator>Bromlem</dc:creator>
      <dc:date>2019-11-08T01:25:53Z</dc:date>
    </item>
    <item>
      <title>Re: Unique row Identifier in distributed LASR Server.</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Unique-row-Identifier-in-distributed-LASR-Server/m-p/602659#M174499</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/170533"&gt;@Bromlem&lt;/a&gt;: Thanks. I wonder what else doesn't work there ;).&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Nov 2019 01:49:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Unique-row-Identifier-in-distributed-LASR-Server/m-p/602659#M174499</guid>
      <dc:creator>hashman</dc:creator>
      <dc:date>2019-11-08T01:49:27Z</dc:date>
    </item>
  </channel>
</rss>

