Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

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

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Db2
Components Security Monitoring
Created by Guest
Created on Dec 6, 2018
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit DB24LUW-I-551 implicit GRANT EXECUTE to SYSMON authority for all monitor routines(RIMS).

Introduce MON_ADM privilege for monitoring purposes Merged

A MON_ADM privilege will be useful for monitoring tasks, manually or automatically like through Data Server Manager or IBM ITM. Such a privilege will only enable the user to use the monitoring framework table functions and adjacent functionality required for monitoring purposes. (MON_GET, ADMIN_GET etc). This MON_ADM privilege should be able to handle monitoring cloud instances of Db2 into consideration as well, without getting in the domain of the DevOps teams that manage the cloud environments.
  • Guest
    Jul 1, 2019

    Without additional information on why MON_ADM is needed versus SQL_ADM, I will return this as a duplicate of idea

  • Guest
    Jun 6, 2019

    Paul Bird’s comment option #2 looks great for us: “revamp the SYSMON authority so that it is now relevant to the modern Db2 monitoring paradigm by giving it implicit execute privilege on the MON* monitoring functions.”

  • Guest
    Mar 19, 2019

    After review, we have a couple of questions on which we could use feedback to help us evaluate this request.

    #1 The original motivation behind the SQL Administration authority (SQLADM) was to provide a light-weight authority similar to what you request ( ).

     - Could you tell us what portions of this authority are considered to be too much or dangerous and thus require an introduction of a further subset authority?

    #2 Another request has suggested that we revamp the SYSMON authority so that it is now relevant to the modern Db2 monitoring paradigm by giving it implicit execute privilege on the MON* monitoring functions.

     - Would this approach also meet your requirement?