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

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Future consideration
Created by Guest
Created on Feb 1, 2021

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 requester the call originated . It would be very good If I could filter thru connection type DRDA and if i could trace the origin of the query ( remote db2 ) . i know that in the LUWID we have the communications database info (linkname, location maybe ) . We have a lot of remote queries and have lost track of where they come from also we cant send the remote queries to its proper owners to be fixed if we dont know the originating DB

Needed by Date May 2, 2021