We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to firstname.lastname@example.org for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
In 2.6.4 of EclipeLink, parameter binding was selective in DatabasePlatform (Db2). On 10/23/2018, 1st problem occurred where arithmetic functions (SQRT, ABS, SUBSTR, etc) were not bound when they were used.
APAR PH06475 created and provided "eclipselink.jdbc.force-bind-parameters". In this property, both parameters and literals are bound regardless of the DatabasePlatform (Db2) selection.
After applying APAR PH06475, Some SQL errors occurred due to literals bound by force-bind that did not match Db2 rules.
On 2019/07/05, To resolve the situation, created and applied APAR PH14747, which does not bind literals. It is current level.
Parameters are bound even if they result in SQL errors because of binding forcely when using "eclipselink.jdbc.force-bind-parameters". - So, application modification is required.
Literals are not bound at all because of disable by PH14747. -no benefit of performance improvement.
Do not place IBM confidential, company confidential, or personal information into any field.