<?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: How to treat delimiter in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/How-to-treat-delimiter/m-p/542215#M149813</link>
    <description>&lt;P&gt;It is the LENGTH and not the format is that will cause truncation for those two character variables. Formats just effect how a variable is displayed. Since no formats are attached the format cannot cause any truncation.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Perhaps you meant the informat?&amp;nbsp; But when reading using LIST mode SAS will ignore the width on the informat specification.&amp;nbsp; So even if there was too short a width on the informat it wouldn't cause truncation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However since no length for the variable has been set SAS will need to decide on its own how to define the length.&amp;nbsp; And since there is also no informat with its associated width for SAS to base its guess on it will use the default length of 8 characters (bytes actually).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 21:06:26 GMT</pubDate>
    <dc:creator>Tom</dc:creator>
    <dc:date>2019-03-11T21:06:26Z</dc:date>
    <item>
      <title>How to treat delimiter</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-treat-delimiter/m-p/541944#M149735</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have the data as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;data test;&lt;BR /&gt;infile datalines MISSOVER dlm='|' dsd;&lt;BR /&gt;input&amp;nbsp; YR_MTH_NBR YR_NBR MTH_NBR FAC_ID GST_TYP ENTERPRISE_ID STAY_GST_ID MEMBER_TYPE $&lt;BR /&gt;ENROLL_STY_IND $ SVY_SENT_DT mmddyy10. SVY_COMPLT_DT: mmddyy10. BRAND_MINOR_CD $&lt;BR /&gt;REGION_DESC $ MAIL_IND LANG_TYP $ CK_IN_DT: mmddyy10. CK_OUT_DT: mmddyy10.&lt;BR /&gt;VERB_1a_v: $ 100. Confirmation_number: HBR1_Region: $ HBR2_SubRegion: $ HBR3_Country: $&lt;BR /&gt;BK_SOURCE_CD: $ @;&lt;BR /&gt;format SVY_SENT_DT mmddyy10. SVY_COMPLT_DT mmddyy10. CK_IN_DT mmddyy10. CK_OUT_DT mmddyy10.;&lt;BR /&gt;datalines;&lt;BR /&gt;201612|2016|12|9278|1|640242220|2286593523|CLUB|N|12/31/2016|12/31/2016|HIIS|AMERICAS|1|ENU|12/28/2016|12/29/2016|The cooked breakfast option was wonderful. It was nice to order from a menu vs eat from a hot/cold breakfast buffet bar.Room was clean and comfortable and plenty of space. We had restful sleep.|62099040|Americas|North America|United States|CRO&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;201612|2016|12|10822|1||2274029967|SPRE|N|12/03/2016|12/31/2016|HEXS|AMERICAS|4|ENU|11/30/2016|12/01/2016|Better quality breakfast food.|60958042|Americas|North America|United States|LMNCO&lt;BR /&gt;;&lt;BR /&gt;run;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Concern:&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) I am not able to read the correct values.&lt;/P&gt;&lt;P&gt;2) The above code is not treating two consecutive delimiters as missing value.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kindly suggest a code which can read through above values&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:55:52 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-treat-delimiter/m-p/541944#M149735</guid>
      <dc:creator>Guptashwe</dc:creator>
      <dc:date>2019-03-11T10:55:52Z</dc:date>
    </item>
    <item>
      <title>Re: How to treat delimiter</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-treat-delimiter/m-p/541947#M149737</link>
      <description>&lt;P&gt;You forgot a colon after SVY_SENT_DT, that's all!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:08:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-treat-delimiter/m-p/541947#M149737</guid>
      <dc:creator>s_lassen</dc:creator>
      <dc:date>2019-03-11T11:08:23Z</dc:date>
    </item>
    <item>
      <title>Re: How to treat delimiter</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-treat-delimiter/m-p/542207#M149812</link>
      <description>&lt;P&gt;Also your example has much more than 100 characters for the variable VERB_1a_v.&lt;/P&gt;
&lt;P&gt;The variables HBR2_SubRegion and&amp;nbsp;HBR3_Country are also truncated because the &lt;STRONG&gt;&lt;U&gt;&lt;FONT color="#339966"&gt;in&lt;/FONT&gt;&lt;/U&gt;&lt;/STRONG&gt;format isn't long enough.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If your full data has more variables that appear incomplete you likely need to adjust the informat(s) to read more characters.&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:33:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-treat-delimiter/m-p/542207#M149812</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2019-03-11T22:33:11Z</dc:date>
    </item>
    <item>
      <title>Re: How to treat delimiter</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-treat-delimiter/m-p/542215#M149813</link>
      <description>&lt;P&gt;It is the LENGTH and not the format is that will cause truncation for those two character variables. Formats just effect how a variable is displayed. Since no formats are attached the format cannot cause any truncation.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Perhaps you meant the informat?&amp;nbsp; But when reading using LIST mode SAS will ignore the width on the informat specification.&amp;nbsp; So even if there was too short a width on the informat it wouldn't cause truncation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However since no length for the variable has been set SAS will need to decide on its own how to define the length.&amp;nbsp; And since there is also no informat with its associated width for SAS to base its guess on it will use the default length of 8 characters (bytes actually).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:06:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-treat-delimiter/m-p/542215#M149813</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2019-03-11T21:06:26Z</dc:date>
    </item>
    <item>
      <title>Re: How to treat delimiter</title>
      <link>https://communities.sas.com/t5/SAS-Programming/How-to-treat-delimiter/m-p/542240#M149814</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/159"&gt;@Tom&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;It is the LENGTH and not the format is that will cause truncation for those two character variables. Formats just effect how a variable is displayed. Since no formats are attached the format cannot cause any truncation.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Perhaps you meant the informat?&amp;nbsp; But when reading using LIST mode SAS will ignore the width on the informat specification.&amp;nbsp; So even if there was too short a width on the informat it wouldn't cause truncation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However since no length for the variable has been set SAS will need to decide on its own how to define the length.&amp;nbsp; And since there is also no informat with its associated width for SAS to base its guess on it will use the default length of 8 characters (bytes actually).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Correct and I mentioned the informat in the second bit. Edited above.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:32:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/How-to-treat-delimiter/m-p/542240#M149814</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2019-03-11T22:32:16Z</dc:date>
    </item>
  </channel>
</rss>

