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.
Make DVM JDBC driver publicly available via Maven-like repository
Currently, in order to make the latest JDBC driver available to our developers, we download the jar file from Fix Central, and then make a new entry in our company repository. Ideally, we would like our company repository to point to an IBM/Rocket...
Mac users are limited to installing the DVM plugin on their workstations. MacOS 10.14 is the last version that supports the current 32-bit application. The plugin will not install on an OS beyond 10.14.
In most cases, the collection of runstats requires access to the underlaying data. This access is typically not available to the DVM support team. Those with access to the data will likely not have access to modify global variables outside of Dev....
Preserve joins with accessing multiple underlying DVMs in a single SQL statement
I have a SQL statement that joins 3 tables from 1 PEER DVM with a single table from a different PEER DVM. Currently DVM is breaking this statement into 4 separate SQL statements before sending them to Db2. A better approach, when possible would be...
Do not place IBM confidential, company confidential, or personal information into any field.