INT function in 7.5x2 vs 8.0.1

TD_Chile · Post by **TD_Chile** » Mon Sep 01, 2008 10:46 pm

We're migrating from 7.5x2 to 8.0.1 and when doing the tests we found this problem: the INT () function doesn't return the same value!!! maybe because the value is null but in 7.5x2 a null value in a sequential file it's the same than empty and INT(emptyvalue)=0!!!... but in 8.0.1 a null value in a sequential file is null so INT(nullvalue)=NULL!!!!... We have more than 200 jobs using this function in diferent ways, someone has an idea for what to do?

Thanks in advance

ray.wurlod · Post by **ray.wurlod** » Mon Sep 01, 2008 11:25 pm

Have you specified different NULL mapping in the job? What is the default null mapping in each version (I don't have 8.0.1 where I am)?

TD_Chile · Post by **TD_Chile** » Mon Sep 01, 2008 11:34 pm

I don't know if I can specified a different NULL mapping, if yes that could affect the hash files in wich a NULL always it's a NULL, no?

ray.wurlod · Post by **ray.wurlod** » Tue Sep 02, 2008 12:04 am

In hashed file NULL is always NULL. Internally in hashed files NULL is represented as Char(128), but the translation is automatic. It is only in text files that you need to specify how NULL is represented. My question was whether the default handling is the same in version 8.0.1 as it is in 7.5x2, because I am not presently in a position to verify that for myself.

TD_Chile · Post by **TD_Chile** » Wed Sep 03, 2008 10:58 am

well, after doing a lot of tests the conclusion is that null values on DS7 are treated different (clearly it's a bug) and in DS8 null values are always treated as null, in both sequential files and hashed files.
I also checked the NULL mapping in the sequential files but it's the same, so all that we built assuming "empty = null" on seq files must be changed

thanks