This is an IBM Automation portal for Integration products. 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 (https://ideas.ibm.com).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
firstname.lastname@example.org - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
For clarification, this "client compliance" discovery-information would be very useful to have in MQ SMF, but specifically with the MQ SMF 116 subtype 1 task identification information area.
Please consider that IBM DB2 z/OS provides a similar discovery/identification field in QLACPRLV - see IBM APAR PI74456 for additional details.
From a business justification perspective, "client connections" such as MQ, DB2, others, often provide remote-connection compliance (or non-compliance) for the enterprise's management and controls.
Thank you !!
This is a very reasonable request. However given our focus on other areas of SMF data I can't see us implementing this in the next year and a half or so, which means I have to decline this request.
However I will add this to my list of chinit SMF enhancements so we remember to do it in future.
I think this a fantastic idea to help identify client applications that are using an older and may be unsupported version of the MQ code on the distributed side. This is a huge challenge today since application can get the MQ Client code if a variety of ways (MQ Client install, redistributable client or even just copying the MQ Client JAR files). Some of this methods makes it impossible for a software detection product to scan the client environments to find all instances of the MQ Client installs. Would be better if you can capture this information from the QMGR side since it is already seeing the RVERSION when the channel connects and by putting it in the SMF it makes it easier to gather the information vs. having to create a realtime monitor.