<?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: keep &amp; drop in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18242#M3554</link>
    <description>A consideration is that the DROP= is honored over the KEEP=  when both parameters are coded for a specified SAS variable.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.</description>
    <pubDate>Tue, 17 Nov 2009 16:26:41 GMT</pubDate>
    <dc:creator>sbb</dc:creator>
    <dc:date>2009-11-17T16:26:41Z</dc:date>
    <item>
      <title>keep &amp; drop</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18240#M3552</link>
      <description>please tell me that there is any difference, when we write  keep &amp;amp; drop in option and procidure statement</description>
      <pubDate>Tue, 17 Nov 2009 16:07:33 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18240#M3552</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-11-17T16:07:33Z</dc:date>
    </item>
    <item>
      <title>Re: keep &amp; drop</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18241#M3553</link>
      <description>Except for their being opposites, there is no functional difference.   A decision about which to use is more about programming style than technical substance.</description>
      <pubDate>Tue, 17 Nov 2009 16:12:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18241#M3553</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2009-11-17T16:12:58Z</dc:date>
    </item>
    <item>
      <title>Re: keep &amp; drop</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18242#M3554</link>
      <description>A consideration is that the DROP= is honored over the KEEP=  when both parameters are coded for a specified SAS variable.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.</description>
      <pubDate>Tue, 17 Nov 2009 16:26:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18242#M3554</guid>
      <dc:creator>sbb</dc:creator>
      <dc:date>2009-11-17T16:26:41Z</dc:date>
    </item>
    <item>
      <title>Re: keep &amp; drop</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18243#M3555</link>
      <description>keep and drop options are specified in the datastep or proc  , the difference is when we write options in datastep it will be permanent to the dataset but where as in proc , it will not be permanent and stays affect fot that particular session only.

Message was edited by: reena</description>
      <pubDate>Tue, 17 Nov 2009 16:32:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18243#M3555</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-11-17T16:32:04Z</dc:date>
    </item>
    <item>
      <title>Re: keep &amp; drop</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18244#M3556</link>
      <description>Of course, this presumes the PROC and whether or not there is a permanent output file generated, not just a file going to the WORK or SASUSER allocation.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.</description>
      <pubDate>Tue, 17 Nov 2009 17:56:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18244#M3556</guid>
      <dc:creator>sbb</dc:creator>
      <dc:date>2009-11-17T17:56:38Z</dc:date>
    </item>
    <item>
      <title>Re: keep &amp; drop</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18245#M3557</link>
      <description>hi sbb,&lt;BR /&gt;
 I didn't get your answer.Could you explain it briefly.&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
regards,&lt;BR /&gt;
&lt;BR /&gt;
bina</description>
      <pubDate>Tue, 17 Nov 2009 18:06:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18245#M3557</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-11-17T18:06:44Z</dc:date>
    </item>
    <item>
      <title>Re: keep &amp; drop</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18246#M3558</link>
      <description>It is very much possible to affect a SAS permanent library when using the DROP= and/or KEEP= parameter, if you have WRITE authority to your SAS permanent database.  This capability will be dependent on the user's session and their authority permissions.  For example, consider this code:&lt;BR /&gt;
&lt;BR /&gt;
PROC SORT DATA=PERMIN.MASTER OUT=PERMOUT.MASTER (DROP=X Y Z);&lt;BR /&gt;
  BY ....;&lt;BR /&gt;
RUN;&lt;BR /&gt;
&lt;BR /&gt;
If the OUT=  &lt;LIBREF&gt;  (here PERMOUT) is a permanent library, not just for your session, the result is not going to be just for your session.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.&lt;/LIBREF&gt;</description>
      <pubDate>Tue, 17 Nov 2009 18:50:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18246#M3558</guid>
      <dc:creator>sbb</dc:creator>
      <dc:date>2009-11-17T18:50:29Z</dc:date>
    </item>
    <item>
      <title>Re: keep &amp; drop</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18247#M3559</link>
      <description>Thanks to all. I got my answer.</description>
      <pubDate>Wed, 18 Nov 2009 02:01:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/keep-drop/m-p/18247#M3559</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-11-18T02:01:16Z</dc:date>
    </item>
  </channel>
</rss>

