• Print |
• E-mail  |
• Bookmark

DB2 doesn't allow integer values larger than 2147483647.  So if SAS
encounters a value larger than that it will convert it to a float.
In doing so, the integer values will be padded with 16 decimal places.
This might prevent DB2 from using any existing index on the field and
thus might result in slower performance.

  For example
              WHERE CODE2 in (1122334455,
                              2233445566.33,
                              3344556677.58384,
                              4455667788)

  would be passed as
              WHERE  ( ("CODE2" IN  (1122334455
 ,2233445566.3300000000000000 ,3344556677.5838400000000000
 ,4455667788.0000000000000000 ) ) )

The only current workaround is to switch to using SQL pass-thru.  The
WHERE clause will be passed as you typed it.


A Technical Support hot fix for Release 8.2 (TS2M0) for this
issue is available at:

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#013020


A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#013020

For customers running SAS with Asian Language Support (DBCS), this
fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#013020

Operating System and Release Information

A fix for Release 8.2 (TS2M0) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :