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.
allow QM to EASILY search for SQL that does data changes
This idea belongs to both the ISPF QM interface and the CAE browser interface.
I would like some method to use QM to EASILY find SQL that is doing data changes.
Sometimes I am using QM to search for SQL that is doing data changes.
Why? I am trying to understand who is changing a table. I might use QM to search on a data object (or database) and only want to see the DML (ins/upd/del/merge). Today I might find the interesting object and have to visually scan all the SQL and ignore the SELECT. This situation has come up more than once. I think it might be useful
another search perspective might be to use QM to find a userid or jobname and I only want to see the DML from that perspective. Ignore the SELECT
Basically, my idea is that it would be more user friendly to add a button or search option to allow QM to focus on SQL that is doing data changes.
most simply, you could filter on SQL that begins with INSERT/UPDATE/DELETE/MERGE. Although this might miss some rarer cases like SELECT from INSERT or perhaps CALL that does INSERT... perhaps you have the IFCID info that the SQL is doing data changes (IFCID QXRWSINSRTD for example).
I do not know HOW this option should be implemented. But I do know it would be useful.
Do not place IBM confidential, company confidential, or personal information into any field.