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.
Temporal Base Table SQLOUT INSERTS have generate always columns as part of the insert
The timestamp columns supporting temporal should not be part of the INSERT. Also anytime a generate always column is excluded as it should have been in this run, columns must be added to the INSERT statement.
--UNDO SQL FOR SUBSYSTEM: DAA1
Add Ability to Specify Archive Datasets as Input for LAT Scan
A user will run a scan to create an archive file, or several scans over time, each creating a file. When he wants to revisit these, he has found he is only able to specify the start and end times in his window. It seems that LAT will read through ...
We have tables with a large number columns. In the detailed report there are always the complete row images (all columns) printed which makes it hard to see the differences. There are signs in the column name header (#, !, -) that indicate a chang...
HiOur DBAs would like to have REDO statements for any RI-action generate by DB2 (e.g Delete Cascade). At the moment ALA is assuming that the RI defined on the source system also is defined on the target system. snip from the manual:As previously m...
Improve handling of tables with structure changes in Log Analyzer Tool
The current handling of tables that have had structure changes (alters, drop/recreate) is extremely cumbersome and difficult to pro-actively manage, requiring TVFILE entries for altered tables and duplicate structures for tables that have been dro...
Mapping Source Tables to Target Tables using Db2 Administration Tool masking principles
Using Db2 Log Analysis Tool, Classic Menu, option 5 "Execute dynamic SQL in batch", we are able to map from Source Table to Target Table. But table owner and table name of source and target name must be specified at full. If we have 50 tables, whe...
Do not place IBM confidential, company confidential, or personal information into any field.