Consider the following code. a = b and yet SAS determines that a < b. Why?
data x;
a = 11*10;
b = (11/10)*100;
if a = b then put 'equal';
if a > b then put 'greater';
if a < b then put 'less';
output;
run;
Do a google search for "sas numeric precision", and you will find the answer.
In short: decimal fractions cannot be exactly represented as binary data, so you introduce minimal aberrations during the calculation. When testing for equality, always use the ROUND() function before you compare.
BTW 11/10 can't even be represented exactly as a decimal value, as it resolves to 1.1 periodic.
Do a google search for "sas numeric precision", and you will find the answer.
In short: decimal fractions cannot be exactly represented as binary data, so you introduce minimal aberrations during the calculation. When testing for equality, always use the ROUND() function before you compare.
BTW 11/10 can't even be represented exactly as a decimal value, as it resolves to 1.1 periodic.
Hello @SAS1ns1ghts,
See this 2020 post for a detailed explanation why for SAS (under Windows) 0.07*100>7 (!). Your example, 1.1*100>110, is quite similar. The length of the period in the binary (periodic) fraction representing the decimal fraction 1.1 is 4, not 20 as in the case of 0.07, but the basic pattern is the same: a periodic fraction is rounded internally and the rounding error propagates in calculations.
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.