<?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: SAS Infile Statement in SAS Software for Learning Community</title>
    <link>https://communities.sas.com/t5/SAS-Software-for-Learning/SAS-Infile-Statement/m-p/919659#M1778</link>
    <description>&lt;P&gt;Show your code.&amp;nbsp; Do not attach WORD file.&amp;nbsp; Just copy and paste the actual text into the window that pops up when you click on the Insert SAS Code button.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The wording in the assignment is very imprecise (and hence potentially confusing).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I assume the first point is that you should have a COMMENT in your code that has your name.&amp;nbsp; Like writing your name on your homework or exam paper.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You do not use an INFILE statement to read from an existing SAS dataset.&amp;nbsp; So I assume the second point is talking about using an INFILE statement to point to the source text that will be read as part of a DATA STEP that will create a SAS dataset.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I assume the third point is talking about making sure to include the problem number in the title (or titles) on your OUTPUT.&amp;nbsp; Again to make it easier for the grader.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The text you posted does not look like something that a novice SAS user could read into a dataset.&amp;nbsp; I assume that its formatting has been destroyed by being pasted into this discussion forum.&amp;nbsp; That will mess up the formatting since it will try to flow the text into paragraphs.&amp;nbsp; If you want to share the text of the file then copy the text and paste it into the box that appears when you click on the Insert Code button.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 09 Mar 2024 20:44:21 GMT</pubDate>
    <dc:creator>Tom</dc:creator>
    <dc:date>2024-03-09T20:44:21Z</dc:date>
    <item>
      <title>SAS Infile Statement</title>
      <link>https://communities.sas.com/t5/SAS-Software-for-Learning/SAS-Infile-Statement/m-p/919658#M1777</link>
      <description>&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;Write your name in your program using a common statement.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Use infile statement to read the data set.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Assign a title with the problem number for each problem,&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Your output for each problem should contain only what is asked.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Please submit your programs and outputs.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Given Data/Code: From Separate Document&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;SPAN&gt;Employee_id &amp;nbsp; Name gender &amp;nbsp; years &amp;nbsp; dept &amp;nbsp; &amp;nbsp; salary01 salary02&amp;nbsp; salary03;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&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;1 Mitchell, Jane A&amp;nbsp; f&amp;nbsp; &amp;nbsp; 6 &amp;nbsp; &amp;nbsp; shoe &amp;nbsp; &amp;nbsp; 22,450&amp;nbsp; 23,000&amp;nbsp; 26,600&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2 Miller, Frances T&amp;nbsp; f&amp;nbsp; 8&amp;nbsp; appliance&amp;nbsp; &amp;nbsp; &amp;nbsp; . &amp;nbsp; &amp;nbsp; 32,500&amp;nbsp; 33,000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;3 Evans, Richard A&amp;nbsp; m &amp;nbsp; 9&amp;nbsp; appliance&amp;nbsp; &amp;nbsp; 42,900&amp;nbsp; 43,900&amp;nbsp; .&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;4 Fair, Suzanne K&amp;nbsp; f&amp;nbsp; &amp;nbsp; 3&amp;nbsp; clothing &amp;nbsp; &amp;nbsp; 29,700&amp;nbsp; 32,900 34,500&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;5 Meyers, Thomas D&amp;nbsp; m&amp;nbsp; 5&amp;nbsp; appliance &amp;nbsp; &amp;nbsp; 33,700&amp;nbsp; 34,400&amp;nbsp; 37,000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;6 Rogers, Steven F&amp;nbsp; m&amp;nbsp; 3&amp;nbsp; &amp;nbsp; shoe &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 27,000&amp;nbsp; 27,800&amp;nbsp; .&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;7 Anderson, Frank F&amp;nbsp; m&amp;nbsp; 5&amp;nbsp; clothing&amp;nbsp; &amp;nbsp; &amp;nbsp; 33,000&amp;nbsp; 35,100&amp;nbsp; 36,000&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;10 Baxter, David T&amp;nbsp; m&amp;nbsp; 2 &amp;nbsp; &amp;nbsp; shoe &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 23,900&amp;nbsp; &amp;nbsp; .&amp;nbsp; &amp;nbsp; 31,300&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;11 Wood, Brenda L&amp;nbsp; f&amp;nbsp; 3 &amp;nbsp; &amp;nbsp; clothing&amp;nbsp; &amp;nbsp; &amp;nbsp; 33,000&amp;nbsp; 34,000&amp;nbsp; 35,700&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;12 Wheeler, Vickie M&amp;nbsp; f&amp;nbsp; 7&amp;nbsp; appliance &amp;nbsp; &amp;nbsp; 31,500&amp;nbsp; 33,200&amp;nbsp; 35,600&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;13 Hancock, Sharon T&amp;nbsp; f&amp;nbsp; 1&amp;nbsp; clothing&amp;nbsp; &amp;nbsp; &amp;nbsp; 21,000 &amp;nbsp; . &amp;nbsp; &amp;nbsp; 22,500&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;14 Looney, Roger M&amp;nbsp; &amp;nbsp; m&amp;nbsp; 10 appliance &amp;nbsp; &amp;nbsp; 42,900 36,200 37,800&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;15 Fry, Marie E &amp;nbsp; &amp;nbsp; f&amp;nbsp; &amp;nbsp; 6&amp;nbsp; clothing&amp;nbsp; &amp;nbsp; &amp;nbsp; 29,700 30,500 31,200&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Problems:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;Apply both proc freq and proc chart to show the distribution of years of employment.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;Apply both proc freq and proc chart to show the number of employees in each department for each gender.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;Calculate the average of the two highest salaries for employees who have three salaries and average of two salaries if they have only two salaries. Print the names of employees who have the highest average in their department. Also, print their averages, their department names, and the department averages.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;Obtain a table that shows the average of salary01 for each gender in each department.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;For each department, use a two-way table to show both the number of employees whose salar01 is above 30,000 and also the number of employees whose salarie01 is not above 30,000.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;Print the name of employee whose salary01 is the highest among all employees.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;For each department find the employee whose salary01 is the highest in the department. Print the names of these employees and department names.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;SPAN&gt;I think I have the correct code but I don't understand the infile statement to pull data from another source&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 09 Mar 2024 20:17:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Software-for-Learning/SAS-Infile-Statement/m-p/919658#M1777</guid>
      <dc:creator>ccwrich</dc:creator>
      <dc:date>2024-03-09T20:17:00Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Infile Statement</title>
      <link>https://communities.sas.com/t5/SAS-Software-for-Learning/SAS-Infile-Statement/m-p/919659#M1778</link>
      <description>&lt;P&gt;Show your code.&amp;nbsp; Do not attach WORD file.&amp;nbsp; Just copy and paste the actual text into the window that pops up when you click on the Insert SAS Code button.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The wording in the assignment is very imprecise (and hence potentially confusing).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I assume the first point is that you should have a COMMENT in your code that has your name.&amp;nbsp; Like writing your name on your homework or exam paper.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You do not use an INFILE statement to read from an existing SAS dataset.&amp;nbsp; So I assume the second point is talking about using an INFILE statement to point to the source text that will be read as part of a DATA STEP that will create a SAS dataset.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I assume the third point is talking about making sure to include the problem number in the title (or titles) on your OUTPUT.&amp;nbsp; Again to make it easier for the grader.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The text you posted does not look like something that a novice SAS user could read into a dataset.&amp;nbsp; I assume that its formatting has been destroyed by being pasted into this discussion forum.&amp;nbsp; That will mess up the formatting since it will try to flow the text into paragraphs.&amp;nbsp; If you want to share the text of the file then copy the text and paste it into the box that appears when you click on the Insert Code button.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 09 Mar 2024 20:44:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Software-for-Learning/SAS-Infile-Statement/m-p/919659#M1778</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2024-03-09T20:44:21Z</dc:date>
    </item>
  </channel>
</rss>

