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
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 COMPARE is...
ANLPJCL - When line is blank, exiting and coming back into the product, + is generated on the JCL jobcard
When the jobcard line is blank, SQL/PA should store //*. The product is populating the blank line with + when the product is exited and then entered again. This would prevent JCL errors because + is generated in the first character on the jobcard.
Capture cost and path information for New SQL to help DBAs determine if there might be an access problem
There is a new release of application code. Currently SQL/PA does a COMPARE of current and previous access paths. There is a hole for NEW SQL that takes a bad access path. DBAs need to know if this is occurring.
Do not place IBM confidential, company confidential, or personal information into any field.