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.
Apply Copybook when defining Db2 for z/OS virtual table
(This IDEA item was written based on a customer requirement revealed in DVM POC test at customer site.) So far, customer cannot apply COBOL copybook (assembler DSECT, PL/I DCL statements, etc. also) when defining DBMS (RDBMS) virtual table including Db2 for z/OS data source.
All the required metadata information are retrieved from "catalog" database, and there's no room for further modification by customer themselves to define DBMS (Db2 for z/OS) virtual table.
Consequently, DVM virtual table ("logical" table) always has the same record layout as its corresponding Db2 for z/OS table ("physical" table).
However, most Japanese customers, especially in financial sector, have a lot of copybooks per one Db2 table. They use different copybooks depending on the situation, and "logical" record layout much differs from "physical", Db2 for z/OS table record layout. But now, DVM cannot help such use scenario and less appealing to such large customers.
So, DVM should be enhanced to provide ability ("Use Copybook" button) to apply copybook when defining Db2 for z/OS virtual table.
With this enhancement, DVM would be more appealing to manufacturing customers also, because they could virtually have more than 750 columns per a table, which is the current upper limit of Db2 for z/OS.
Do not place IBM confidential, company confidential, or personal information into any field.