<?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: calling on a column that breaks SAS rules in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/calling-on-a-column-that-breaks-SAS-rules/m-p/708778#M217864</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/217720"&gt;@axescot78&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;Thanks Tom. Looking at it again, the error is related to the format:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ERROR: The format MOD was not found or could not be loaded.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Looking at the proc contents, the column is named MOD and the format is MOD. Must be a custom format!&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;You can change the behavior of missing formats as errors by setting:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Options nofmterr;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Or create a temporary format that does nothing:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Proc format;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; value mod;&lt;/P&gt;
&lt;P&gt;run;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;would find a format but treat the values as the BEST format.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Or find the definition for the MOD format and run it in your session.&lt;/P&gt;</description>
    <pubDate>Wed, 30 Dec 2020 15:46:52 GMT</pubDate>
    <dc:creator>ballardw</dc:creator>
    <dc:date>2020-12-30T15:46:52Z</dc:date>
    <item>
      <title>calling on a column that breaks SAS rules</title>
      <link>https://communities.sas.com/t5/SAS-Programming/calling-on-a-column-that-breaks-SAS-rules/m-p/708676#M217826</link>
      <description>&lt;P&gt;I have a dataset that I want to subset by column name. One of the columns I am interested in keeping is named 'MOD'. SAS returns an error when I call on this column; probably because it violates this rule:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SAS reserves a few names for automatic variables and variable lists, SAS data sets, and librefs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How can I call on this column? I have to use 'keep' rather than 'drop' because there are 78 columns in this dataset.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Dec 2020 00:10:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/calling-on-a-column-that-breaks-SAS-rules/m-p/708676#M217826</guid>
      <dc:creator>axescot78</dc:creator>
      <dc:date>2020-12-30T00:10:19Z</dc:date>
    </item>
    <item>
      <title>Re: calling on a column that breaks SAS rules</title>
      <link>https://communities.sas.com/t5/SAS-Programming/calling-on-a-column-that-breaks-SAS-rules/m-p/708681#M217829</link>
      <description>&lt;P&gt;Show us the log of this step, complete, unedited, with nothing chopped out, and in the sequence that it appears in the log. Please click on the &amp;lt;/&amp;gt; icon and paste the log as text into the window that appears. &lt;STRONG&gt;DO NOT SKIP THIS STEP&lt;/STRONG&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Dec 2020 00:58:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/calling-on-a-column-that-breaks-SAS-rules/m-p/708681#M217829</guid>
      <dc:creator>PaigeMiller</dc:creator>
      <dc:date>2020-12-30T00:58:26Z</dc:date>
    </item>
    <item>
      <title>Re: calling on a column that breaks SAS rules</title>
      <link>https://communities.sas.com/t5/SAS-Programming/calling-on-a-column-that-breaks-SAS-rules/m-p/708684#M217830</link>
      <description>&lt;P&gt;There are very few (if any) names that SAS will not allow as a variable name.&amp;nbsp; MOD is definitely a valid variable name.&lt;/P&gt;
&lt;P&gt;Example:&lt;/P&gt;
&lt;PRE&gt;123  data test;
124    do mod=1 to 5; output; end;
125  run;

NOTE: The data set WORK.TEST has 5 observations and 1 variables.
NOTE: DATA statement used (Total process time):
      real time           0.09 seconds
      cpu time            0.03 seconds


126  proc print data=test;
127    where mod=3;
128  run;

NOTE: There were 1 observations read from the data set WORK.TEST.
      WHERE mod=3;
NOTE: PROCEDURE PRINT used (Total process time):
      real time           0.12 seconds
      cpu time            0.00 seconds
&lt;/PRE&gt;</description>
      <pubDate>Wed, 30 Dec 2020 01:23:33 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/calling-on-a-column-that-breaks-SAS-rules/m-p/708684#M217830</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2020-12-30T01:23:33Z</dc:date>
    </item>
    <item>
      <title>Re: calling on a column that breaks SAS rules</title>
      <link>https://communities.sas.com/t5/SAS-Programming/calling-on-a-column-that-breaks-SAS-rules/m-p/708686#M217832</link>
      <description>&lt;P&gt;Thanks Tom. Looking at it again, the error is related to the format:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ERROR: The format MOD was not found or could not be loaded.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Looking at the proc contents, the column is named MOD and the format is MOD. Must be a custom format!&lt;/P&gt;</description>
      <pubDate>Wed, 30 Dec 2020 01:56:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/calling-on-a-column-that-breaks-SAS-rules/m-p/708686#M217832</guid>
      <dc:creator>axescot78</dc:creator>
      <dc:date>2020-12-30T01:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: calling on a column that breaks SAS rules</title>
      <link>https://communities.sas.com/t5/SAS-Programming/calling-on-a-column-that-breaks-SAS-rules/m-p/708701#M217834</link>
      <description>&lt;P&gt;To use the data without access to the format set the option NOFMTERR.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Dec 2020 04:37:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/calling-on-a-column-that-breaks-SAS-rules/m-p/708701#M217834</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2020-12-30T04:37:51Z</dc:date>
    </item>
    <item>
      <title>Re: calling on a column that breaks SAS rules</title>
      <link>https://communities.sas.com/t5/SAS-Programming/calling-on-a-column-that-breaks-SAS-rules/m-p/708778#M217864</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/217720"&gt;@axescot78&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;Thanks Tom. Looking at it again, the error is related to the format:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ERROR: The format MOD was not found or could not be loaded.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Looking at the proc contents, the column is named MOD and the format is MOD. Must be a custom format!&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;You can change the behavior of missing formats as errors by setting:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Options nofmterr;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Or create a temporary format that does nothing:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Proc format;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; value mod;&lt;/P&gt;
&lt;P&gt;run;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;would find a format but treat the values as the BEST format.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Or find the definition for the MOD format and run it in your session.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Dec 2020 15:46:52 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/calling-on-a-column-that-breaks-SAS-rules/m-p/708778#M217864</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2020-12-30T15:46:52Z</dc:date>
    </item>
  </channel>
</rss>

