Author Topic: Problem with ODWEK 8.4.1.7 with precision zero numbers  (Read 3041 times)

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1202
    • View Profile
Problem with ODWEK 8.4.1.7 with precision zero numbers
« on: November 10, 2011, 08:04:00 AM »
There is a problem with 8.4.1.7 and precision zero numbers generating malformed SQL.  The problem you'll see will be ***on the server*** something like this:

ARS0013E CBOLTAPI DB ERROR: {DB2 FOR OS/390}{ODBC DRIVER}{DSN10012}  990 
 DSNT408I SQLCODE = -104, ERROR:  ILLEGAL SYMBOL "=". SOME SYMBOLS       
 THAT MIGHT BE           LEGAL ARE: AT MICROSECONDS MICROSECOND           
 SECONDS SECOND MINUTES MINUTE             HOURS                 

The problem is not the server, but the SQL generated by ODWEK.

If you're running ODWEK on z/OS, install PM37226 or go to 8.4.1.8. 

If you're running ODWEK on any other platform, go to 8.4.1.8.

If you're running a precision zero definition because of some large number such as an ID number or tax identification number, perhaps a better solution if you're on DB2 V9 and above would be BIG INT support.

With DB2 Version 9 and newer you have three choices of integer values:             
                                                                         
Small Int whole numbers from               -32768 to               32767
                                                                         
Integer   whole numbers from          -2147483648 to          2147483647
                                                                         
Big Int   whole numbers from -9223372036854775808 to 9223372036854775807
#zOS #ODF