Accept timestamps which never really exists
In our installation we have a lot of java applications on Unix which access z/OS DB2 data and this area grows a lot.
Our application often use artifical timestamps ( target is not to save the time of something ) to create clustered and unique keys and we modify these timestamp to spread the rows, we insert, over the whole tablespace to get good performance and avoid reorgs. One modification e.g. is that we move the last four digits (micro-seconds ) to the beginning ( year ). So we get timestamps with dates like this: 1582-10-05-18.104.22.168456. When we want to process such a timestamp in Java, DB2 Java classes changes it to 1582-10-15.00.00.00.000000 because the
Gregorian Calendar has timegap between October the 4th and the 15th. To circumvent this we have to cast this values.
The requirement is, that it is possible, that the DB2 driver classes not check or worse change the timestamp values. Perhaps this changed behaviour can be controlled via a parameter or something like this. DB2 accept these timestamps ( it is also used via COBOL ), but the driver change the value without any notification. We demand the same behaviour of Java as in Cobol. In addition the time classes of the driver consume a lot of CPU for their check, which would also be reduced if the driver would remove these checks.
As a consequence we also have some other problems, see RFE 36635.
Finanz Informatik GmbH & Co. KG