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
Post 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 product management 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 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.
Missing reason code from JDBC connecting to DB2 on z/OS
I've written a Java class that uses JDBC to access multiple databases. When I'm using DB2 for z/OS and get an exception related to a stored procedure not running due to a WLM issue, the reason code is not returned to my application. That is, the reason code is not in the SQLException object, nor is it in the more detailed information provided by the IBM extensions. After some investigating, it was determined that the buffer that would have contained the reason code was being truncated. The documentation says that this might happen. The buffer is only 70 bytes. My contention is that the complete error information must always be available to the application. I understand that this is a design change. The buffer must somehow be extended or the IBM language extensions must be changed to return the complete information. There may be other ways to accomplish this. But it should be addressed!
Do not place IBM confidential, company confidential, or personal information into any field.