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.
Add support for static SQL queries text storage in CQM_SUMM_TEXT
There is currently no support for the static SQL in CQM when one wants to store the SQLTEXT for such queries. Only dynamic SQL is supported. It is currently possible to see in the ISPF interface the static sql, but it is gone after a rollup of the...
We have 10 minute intervals. There are times I want to look at a 24 hour period. Today, you must manually select every interval. For a 24 hour period, that's 144 intervals that must be selected. If using the CAE, then it works great. But what abou...
Query Monitor CAE GUI - Add ability to Alert on -904 Resource Unavailable but exclude instances for specific reason codes
QM and CAE have been set up to use the ALERT feature for DB2 SQL error -904 with an email response. Please provide a solution on how to configure the email RESPONSE to NOT send the email if it is for a specific reason code 00C900D1 (Explanation: T...
Enhance the SQLCODE screen to show total SQLCODE counts as well as the existing counts for SQLCODEs with details
The SQLCODEs screen is useful for tracking down SQL issues but when you drill into the details for a specific SQLCODE or change the grouping to PLAN/PACKAGE/USER/etc the screen looses the total count of the SQL errors and only gives you the count ...
Accurate Aggregate SQLCODE Counts on SQL Code Summary for CORRNAME and JOBNAME
Counts for SQLCODE do not align between summary screens. Would also be nice to have SQLCODE GROUP BY JOBNAME See attached PDF for screen shots. These counts at CORRID/CORRNAME/JOBNAME should also be included in the CQM_SQLCODES table. We are being...
Provide option to offload VSAM files in DSNTIAUL format
We run query monitor across 4 plexes and 9 LPARS and many DB2 systems. We do 'not' load the QM performance data to each system, rather we offload the data from each LPAR, then consolidate the load of the data to one of our non-prod performance war...
CAE web-based activity browser should change default rows from 25 to something else
The CAE web-based activity browser defaults to displaying 25 rows. I almost always want to look at more then 25 rows. So I always click on the drop-down and change the nbr of rows to display. The problem is that we cannot change the default of 25 ...
LOAD card generated by CQM Unload Program CQM@WDB2 should also have NUMRECS
Presently the Load card generated by CQM Unload Program CQM@WDB2 does not have NUMRECS. This results in problem, when DB2 is not able to accurately estimate the number of records being loaded ( as suggested by IBM support itself in case TS00...
QM CAE web interface should remember the target CQM subsystem
When using the QM CAE web interface. When starting the QM CAE browser, the Activity Browser drop down list for "targets" always default initially to the alphabetical first target name. This is my dev DB2. I am usually using QM to look at prod. So ...
Do not place IBM confidential, company confidential, or personal information into any field.