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 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
Do not place IBM confidential, company confidential, or personal information into any field.