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.
Enable DVM Studio to be able to quickly capture environment data needed for problem resolution
We are sometimes asked to provide detailed information for a Case we have opened on DVM. Information includes the current build, IN00, trace browse, map definitions and sometimes the underlying data that is causing the issue. If functionality wa...
Currently creating package binds for Db2 z/OS is completely separated from the DVM subsystem. I can roll out the packages to all Db2 z/OS subsystems before any DVM subsystems are created. For Db2 LUW, in order to install the binds, I must first ...
Consistently handle unsupported Db2 datatypes when creating Virtual tables
When creating a Vitural Table for Db2 BLOB and CLOB with traditional access, the wizard prompts that these columns will be omitted. Executing selects against the created VT is successful. If direct access to Db2 is chosen, the same prompts occur,...
In our test environments we have the same Db2 tables on the same Db2 subsystem under different schemas. This allows for multiple teams to be testing against different sets of data, and potentially different version of table DDL at the same time. ...
Allow Source DVM to pass Virtual Target System name to target DVM over IDF
We would like the ability for the source DVM to pass information, such as the Virtual Target System name, to the target DVM and make this information available within the rules running on the target. This will allow us to reduce the number of DVM...
Remove the need to have SEF (Update) in order to create Web Service directories.
We want our application areas to control the creation of their own virtual tables/views and the web services structures. Currently SEF (Update) is required for the creation of Web Service directories. This access would also give them the ability...
Allow users to navigate to next zoom trace via a PF key
Currently, when looking at zoom information in multiple sequential trace entries, the user has to PF3 to back out of the current zoom, re-position the cursor on the next line and then press enter. After every PF3, the cursor returns to the top o...
Per IBM direction, we are currently working towards fully populating the IMS catalog. This catalog could be used in a similar manner to the Db2 catalog when creating DVM virtual tables. Instead of providing the DBD, PSB and copybooks when creati...
Utilize IMS Dynamic Allocation Library for IMS Direct access
Currently DVM requires that RECON datasets be utilized for IMS Direct access. RECON datasets are not used in our test environments since DBRC is not enabled. The same information can be pulled from the dynamic allocation libraries, which are typ...
Support for columns with names longer than 30 characters
DVM currently fails when attempting to create virtual tables over source tables with column names longer than 30 characters. DBMS's including Postgres, Oracle and DB2 LUW allow for longer column names.
Do not place IBM confidential, company confidential, or personal information into any field.