This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
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
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...
Increase the limit of tables that can be read in a single pass. RFE 123712
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=123712 Reading more 575 tables in a single pass results in the following error message:ALAA464E LOAD table limit exceeded, storageexhausted.Explanation: You have exceeded the...
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...
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 ...
When creating undo records there is the possibility, that the rows for an affected table could not be recreated, because an image copy is missing (ALAA107E). The job for the "DB2 LOG ANALYSIS TOOL" stops.
What we expect is, that to tool writes a ...
Time delimiters expanded for the from/to on the ALA panels - Accept '.' in addition to ':'.
The "Log range Start/End on the tools panels only accepts the colon(:) on the time delimiters. SDSF/JES indicates STARTED time on jobs with the dot(.) delimeter. Changing to allow the dot(.) would expedite the copy-paste filling in of these values...
LAT - Allow all parameters to be changed in the JCL without having to re-generate the syntax using the ISPF interface.
Currently in order to create a Log Analysis JCL, it is necessary to navigate through CLISTs. The proposed solution it to allow the user to create/edit the JCL directly, having a LA command syntax like the utilities.
Do not place IBM confidential, company confidential, or personal information into any field.