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.
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...
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 ...
LAT supports filtering on column level in detail reports, but the filter criteria is coded in a proprietary syntax that does not support SQL constructs (e.g. IN list). We use it to specify column level filters in SQL Syntax in our current tool. We...
Support for creating DB2 Load Data Sets in RECFM=VBS Format with embedded LOB data
DB2 LAT to support creation of load files in RECFM=VBS with embedded LOB/XML data. DB2 LAT supports log processing to create load files for tables with LOB/XML columns. At present DB2 LAT only allows LOB/XML columns to be extracted into PDS or PDS...
The "FastPath" option for detailed reports is very useful for avoiding costly roll forward or roll backward processing.However, for compressed tables the compressed data is shown and the user have no easy way to decompress the data.
We suggest an ...
Do not place IBM confidential, company confidential, or personal information into any field.