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.
Enable profile filtrering by connection type identifying remote requester
I need to pick up only the queries which come in from remote requesters thru DRDA and which is the remote requester. At the moment I can only identify through the DISTSERV plan and maybe DSNTIAUL . Query Monitor doesnt show from which remote reque...
Display in task log the current profile after refresh or start up
Nowadays when o profile is refreshed or changed , the message doesnt show the profile name in the STC joblog . In order to check it is necessary to enter the ispf interface. It would be nice if at least the profile name could be displayed in the S...
Confirmation Message Needed in ISPF When a QM Profile is Updated (or Not)
When using the ISPF interface of Query Monitor to update a QM profile, it is currently very difficult for a user to determine whether the profile was actually updated (and saved) or not as a result of their actions. The only indication that the us...
Report all SQL calls in native stored procedures in Query Monitor
See case# TS003954339. Sometimes Query monitor doesn't capture the SQL statement but gives the message: CQM145I - SQL TEXT NOT AVAILABLE, instead. IBM case states that these are internal SQL calls in native stored procedures. In my case they were ...
HOST Variable and SQL Text features cannot be used as the granularity is ON/OFF where what we need is granularity by application on a DB2 subsystem.
Sensitive data is not always masked so teams cannot view the data, this includes DBAs. Since bot...
Lower WLM capture Threashhold for elapstime to be under 10s
We use WLM to capture long running SQLs. The lowest threashhold for elapstime is set to 10s. This is too high for OLTP, we cannot afford to capture every SQL. But it would be nice to lower the 10s to 1 or 2s.
With introduction of APARs PH08708 and PH08431, messages DSNT376I are suppressed. These are the sentences: PH08708 -> When Timeout Exit is called, IRLM may flag that no DSNT376I message should be issued. In this situation IFCID 196 records will...
QM provides exceptions to collect certain details when we hit those thresholds. In my customer circle none of the customers are monitoring the system without multiple profiles. They simply define multiple lines to active profile with different fil...
Do not place IBM confidential, company confidential, or personal information into any field.