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:
  • 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.
Additional Information:
  • The shorter URL for this site is:
  • To view our 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.

Batch Insert via SQLJ from Java and cast expression is not supported

We want to insert many rows from java applications on Unix in DB2 on z/OS via SQLJ with a good performance. Typically we do this with Batch-mode (execCtx.setBatching(true) inserts. But there are limitations concerning cast, which prohibit the usage of this technique.
The requirement is to remove these limitations.
In our environment we have to cast a lot of timestamp variables, because we don't use the orginal generated timestamp. We modify it, because it is used as a unique clustered key and not to save a time value. To avoid reorg and to spread the rows over the whole tablespace we modity the timestamps, means e.g. we move the last digits (micro-seconds ) to the beginning. Therefore we got artifical timestamps with dates like this: 1582-10-05- When we want to process such a timestamp in Java, DB2 Java classes changes it to 1582-10- because the
Gregorian Calendar has timegap between October the 4th and the 15th. To circumvent this we have to cast this values and this is not possible with Batch - mode insert.
  • Guest
  • Dec 28 2018
  • Future Consideration
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