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 Functionality already exists
Created by Guest
Created on Jun 12, 2018

Db2 JCC drivers should have a unique and documented client_prdid for every JCC driver release

The client database manager product ID, or client_prdid, is (at least for now) the only way a Db2 DBA can identify the driver version of a JCC client application from the database server. All other methods for determining the Db2 JCC client version require file system access on the client machine, which DBAs often do not possess.

The client_prdid contains just a portion of the JCC driver's version/release number (e.g. JCC04190), which often results in several fix pack levels of the JCC driver sending the same client_prdid string to Db2.

Assigning and documenting a unique client_prdid string for each release of the JCC driver will make it just as easy for DBAs to unambiguously identify the client version of connected JCC applications as it is for connected CLI applications.
  • Guest
    Jun 8, 2021

    JDBC Driver sends the necessary details to Db2 servers. Its the Db2 Server needs to provide the outputs to the Admin commands. Please open a tickt for the MON_GET_CONNECTION or MON_GET_CONNECTION_DETAILS SP owners of Db2 Server.

    Db2 zos already handles the same through DISPLAY LOCATION command. The output for 4.24.92 driver is

    ::FFFF: JCC04240


  • Guest
    Jun 8, 2021


    also this idea not only talks about some method to retrieve the JDBC driver version on the client side, but especially retrieving it on the servers side by querying MON_GET_CONNECTION or MON_GET_CONNECTION_DETAILS.

    Kind regards

    Roland Schock

  • Guest
    Jun 8, 2021


    I noticed the status change of this idea to "Functionality already exists" but without comment.
    The idea above requires/suggests a unique version number for every release -- which is currently not implemented.

    If this functionality already exists, I'd rather like to get a pointer into documentation, where I can lookup how to retrieve this driver release specific id. Thanks.

    Kind regards

    Roland Schock