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
Reformat the SYSCOPY Report in INFOM ddname to be a single line instead of two lines
I would also like to see this on one line. Takes up too much vertical space. This would also be more readable with a columnized report.ICTYPE STYPE TTYPE OTYPE DSNUM LDSNUM HDSNUM LOGGED INSTANCE ------ ----- -------- ----- ----- ------ ------ ---...
Add Ability to Pick/Choose Which "Warnings" Are Considered Fatal VS Acceptable
We would like to be able to pick and choose which LAT warnings are acceptable vs which require additional attention. Today, all warnings will generate a return code 4; however, some warnings (like ALAA061W) will completely eliminate a tablespace f...
The tool currently does not support reporting on tables if they have a clone table defined on them. The job ends with a code of 8 and message - ALAA506E-Base/Clone tables not supported
This means that we cannot run a summary or detail report agai...
How can the objects be reported on when doing a QUIET TIME report using CORRID.
Using Quiet Time to recover objects for a CORRID. The report only has the available quiet times, but not the objects that were updated and need to be recovered. Need to run a summary report to get the objects.
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...
The default data set prefix is the current TSO user ID. This makes it hard to list all LAT data sets as there is no common element in the qualifier. If the prefix is changed (e.g. to USER.ALA) then it is easy to list the data sets, but in case of ...
Do not place IBM confidential, company confidential, or personal information into any field.