IBM Data & AI

 Welcome to the IBM Data & AI Ideas Portal for Clients! 

We welcome and appreciate your feedback on IBM Data & AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal.  If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
Clients:
  • Our team welcomes any feedback  and suggestions you have for improving our offerings / products!  This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.
  • If you have not registered on this portal please click on the following link and register.  To complete registration you will need to open the email you will receive from Aha to confirm your identity. http://ibm.biz/IBM-Data-and-AI-Portal-Register
Additional Information:
  • The shorter URL for this site is: https://ibm.biz/IBM-Data-and-AI-Ideas
  • To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps
  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases
  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

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-12.26.24.123456. 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.
  • Guest
  • Dec 28 2018
  • Needs review
Why is it useful?
Who would benefit from this IDEA?
How should it work?
Idea Priority Urgent
Priority Justification
Customer Name Finanz Informatik GmbH & Co. KG
Submitting Organization
Submitter Tags
  • Attach files
  • and 3 more

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions