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.
SQL/PA COMPARE - add Statement matching option 2 - match like "1", but also compare the SQL statement text
This should be added as it exists in the TEST function. I believe this is more important in COMPARE than in TEST. TEST is taking a package from the catalog and just rebinding it. I don't see how any queryno should change value. But when COMPAR...
Add capability to run TEST with APREUSE(WARN) added to the REBIND
ADP is rebinding packages with APREUSE(WARN). This attempts to use the same access path for each SQL statement. Since SQL/PA TEST is not running with this, the product will produce more changes which is not true when APREUSE(WARN) is used.
SQL/PA - TEST with Explain Type D, VERSION, New Version is PH37648.51 and not Package version
When Explain Type is D, New Version is on report is populated with latest APAR instead of the package version. New Package version should be the from the package being explained. New version should be RLSE2142 not PH37648.51 | ...
Create a new report in additional to ANLDELTA, one line per SQL statement meeting the filtering requirements
Need new report to make it easy to see queries easily which have increased costs, decreased costs and new statements. This is based on filters. ANLDELTA has alot of detail which makes it very difficult to determine what queries with increase cos...
Using the TEST function, Need to Filter by Index Name or Table Name
Looking to convert an NPI to DPSI. Need a way to compare access paths of all SQLs that are currently using the NPI to What-if the NPI was not there (aka Virtual Index Delete). The TEST function (Dynamic Explain) currently does not allow filt...
Include option to always report access path changes.
Reporting access path changes should be independent of cost filtering. Some access paths can be detrimental even if little to no cost change is reported by an explain. For instance, the move to a hybrid join from a nested loop join can cause detri...
Do not place IBM confidential, company confidential, or personal information into any field.