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 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.