<?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 Limiting Data for the Proc Freq command in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15722#M2790</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I like Tom's suggestion, but think that the variables have to be separated by commas and that the condition isn't quite what you want.&amp;nbsp; I think the following comes closer:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data test;&lt;/P&gt;&lt;P&gt;&amp;nbsp; set sashelp.class;&lt;/P&gt;&lt;P&gt;&amp;nbsp; if _n_ eq 3 then call missing(age);&lt;/P&gt;&lt;P&gt;&amp;nbsp; if _n_ eq 5 then do;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; call missing(age);&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; call missing(height);&lt;/P&gt;&lt;P&gt;&amp;nbsp; end;&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data want;&lt;/P&gt;&lt;P&gt;&amp;nbsp; set test;&lt;/P&gt;&lt;P&gt;&amp;nbsp; where nmiss(age,height,weight) &amp;lt; 1;&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 27 Feb 2012 20:23:16 GMT</pubDate>
    <dc:creator>art297</dc:creator>
    <dc:date>2012-02-27T20:23:16Z</dc:date>
    <item>
      <title>Limiting Data for the Proc Freq command</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15712#M2780</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm trying to write a code for my professor that will limit the input data on a proc freq command based on the data that our proc genmod command uses.&amp;nbsp; The data set is too large to manipulate manually so I'm just wondering if there is any way to do this.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, our entire data set is roughly 10,000, our regression model uses about 7,000 of those.&amp;nbsp; I'm trying to write a proc freq command that will only use those 7,000 data points instead of the 10,000 from the whole data set.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 18:51:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15712#M2780</guid>
      <dc:creator>whitecj</dc:creator>
      <dc:date>2012-02-27T18:51:06Z</dc:date>
    </item>
    <item>
      <title>Limiting Data for the Proc Freq command</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15713#M2781</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It will be helpful for us to answer if you can post some kind of a scenario what you have and what you want....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 18:53:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15713#M2781</guid>
      <dc:creator>Hima</dc:creator>
      <dc:date>2012-02-27T18:53:30Z</dc:date>
    </item>
    <item>
      <title>Limiting Data for the Proc Freq command</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15714#M2782</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How do you identify them when you run proc genmod?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 18:54:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15714#M2782</guid>
      <dc:creator>art297</dc:creator>
      <dc:date>2012-02-27T18:54:59Z</dc:date>
    </item>
    <item>
      <title>Limiting Data for the Proc Freq command</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15715#M2783</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The scenario is that based on our model several values from the data set get left out so that our N varies based on the model.&amp;nbsp; We want to be able to run proc freq commands and see the frequencies of only those data points used in a given model.&amp;nbsp; As of now we can only run frequencies on the entire data set.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 18:59:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15715#M2783</guid>
      <dc:creator>whitecj</dc:creator>
      <dc:date>2012-02-27T18:59:32Z</dc:date>
    </item>
    <item>
      <title>Limiting Data for the Proc Freq command</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15716#M2784</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;data= (data set reference)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure if that's what you're asking for or not.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 19:01:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15716#M2784</guid>
      <dc:creator>whitecj</dc:creator>
      <dc:date>2012-02-27T19:01:08Z</dc:date>
    </item>
    <item>
      <title>Limiting Data for the Proc Freq command</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15717#M2785</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; How do you restrict the input to GENMOD to those 7000?&lt;/P&gt;&lt;P&gt;I would also investigate the OUTPUT option in GENMOD. You can get all of the input variables and additional information such as residuals and predicted values. Proc freq on that data might do what you're looking for. Or possibly allow a where statement to filter based on a diagnostic or other condition.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 19:01:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15717#M2785</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2012-02-27T19:01:12Z</dc:date>
    </item>
    <item>
      <title>Limiting Data for the Proc Freq command</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15718#M2786</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So you can run something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;proc genmod data=(data set reference);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why can't you then add to the same program:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;proc freq data=(data set reference);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Isn't it that simple?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 19:17:15 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15718#M2786</guid>
      <dc:creator>Astounding</dc:creator>
      <dc:date>2012-02-27T19:17:15Z</dc:date>
    </item>
    <item>
      <title>Limiting Data for the Proc Freq command</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15719#M2787</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here's an example of our code:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Courier New';"&gt;proc genmod;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Courier New';"&gt;title '92CATHOLIC/PROTESTANT COMPARISON MODEL WITH CATHOLIC INTERACTION VARS';&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Courier New';"&gt;model dv92n =dv1975 divsep92 widow92 nevermarr92 child92le18 income92 vcath92divsep92vcath92widow92 vcath92nevermarr92 vcath92child92le18 vcathprot92divsep92vcathprot92widow92 vcathprot92nevermarr92 vcathprot92child92le18/D=MULTINOMIAL;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Courier New';"&gt;run;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Courier New';"&gt;Based on the varibles we used for the model, it misses data points from the data set and produces this output:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Number of Observations Read&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10317&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Number of Observations Used&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 9089&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Missing Values&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1228&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What we want is for a proc freq command to use the exact same 9089 values that are used in the model.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 19:53:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15719#M2787</guid>
      <dc:creator>whitecj</dc:creator>
      <dc:date>2012-02-27T19:53:02Z</dc:date>
    </item>
    <item>
      <title>Limiting Data for the Proc Freq command</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15720#M2788</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you try:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where 0 &amp;lt; nmiss(&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Courier New'; font-size: 12px; background-color: #eef4f9;"&gt;dv92n dv1975 divsep92 widow92 nevermarr92 child92le18 income92 vcath92divsep92vcath92widow92 vcath92nevermarr92 vcath92child92le18 vcathprot92divsep92vcathprot92widow92 vcathprot92nevermarr92 vcathprot92child92le18) &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Courier New'; font-size: 12px; background-color: #eef4f9;"&gt;;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Courier New'; font-size: 12px; background-color: #eef4f9;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 19:55:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15720#M2788</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2012-02-27T19:55:23Z</dc:date>
    </item>
    <item>
      <title>Limiting Data for the Proc Freq command</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15721#M2789</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nope, I'll give it a try! Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 20:00:42 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15721#M2789</guid>
      <dc:creator>whitecj</dc:creator>
      <dc:date>2012-02-27T20:00:42Z</dc:date>
    </item>
    <item>
      <title>Limiting Data for the Proc Freq command</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15722#M2790</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I like Tom's suggestion, but think that the variables have to be separated by commas and that the condition isn't quite what you want.&amp;nbsp; I think the following comes closer:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data test;&lt;/P&gt;&lt;P&gt;&amp;nbsp; set sashelp.class;&lt;/P&gt;&lt;P&gt;&amp;nbsp; if _n_ eq 3 then call missing(age);&lt;/P&gt;&lt;P&gt;&amp;nbsp; if _n_ eq 5 then do;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; call missing(age);&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; call missing(height);&lt;/P&gt;&lt;P&gt;&amp;nbsp; end;&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data want;&lt;/P&gt;&lt;P&gt;&amp;nbsp; set test;&lt;/P&gt;&lt;P&gt;&amp;nbsp; where nmiss(age,height,weight) &amp;lt; 1;&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2012 20:23:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Limiting-Data-for-the-Proc-Freq-command/m-p/15722#M2790</guid>
      <dc:creator>art297</dc:creator>
      <dc:date>2012-02-27T20:23:16Z</dc:date>
    </item>
  </channel>
</rss>

