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...
Support the ability for the JDBC Application name to be passed through TOR to PEER
We currently have a need to use the JDBC Application name to set schema values on virtual tables pointing to Db2 tables. This works fine for a single DVM, but when we have a DVM-to-DVM (TOR-to-PEER) situation, the application name is not being p...
Allow for the creation of UDTF without the cross memory constraint to Db2
Currently when I attempt to create a UDTF, I must have a Db2 subsystem defined to DVM that is running on the same LPAR and it cannot be a data-sharing Db2 behind a DVIPA. Step one would be to eliminate the need for a Db2 subsystem to be selected ...
Wile executing a RESTful API that uses a Data Virtualization Manager service, it is resulting with an AVZ7200E abend when a JWT token is used for authentication/authorization. The same API is executed properly with no abend when using Basic Auth...
Enable instances of a virtual table using a PSB/PCB using a PROCSEQ to use an alternate index (non-root)
Per IBM instances of a virtual table using a PSB/PCB using a PROCSEQ to use an alternate index are only supported for indexes on the ROOT segment.This severely impacts performance for DVM access to IMS data which performs well via IMS using second...
Server Trace profile values should be tied to a specific subsystem
While in the ISPF Server Trace, I can set profile values in order to limit the number of records being viewed. These profiles should be specific to the subsystem that I am currently connected to instead of a global variable that applies to the IS...
Ability to refresh a single Map and not the entire Maplib in batch
Modify the AVZMREFB REXX to allow for the refresh of a single VSAM MAP and not the entire Maplib. When controlling the refresh of VSAM maps in a batch environment where the VSAM files are reloaded frequently there is the need to control the refre...
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...
Support for AES_256 ciphers in DVM Studio secure connections
Currently with DVM Studio v1.1.53 it is not possible to establish a secure TLSv1.2 connection to the z/OS DVM server using AES_256 ciphers. Attempts to connect securely using an AES_256 cipher result in the following error:An error occurred while...
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.