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).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
MQ Application Activity Trace - Filtering by Queue Name
RFE 55753 allows additional options for controlling the activity events produced. However, while mentioned, tracking by queue was not part of the implementation. Filtering by specific queue name is vital to any production tracing environment.
In this case, other trace events which may not be known can be omitted. That is, when tracing by queue, only events between MQopen and MQclose for that queue are required. For example, MQConnect is not relevant to this request nor requests to other queues. The key business objective is to determine who created the message and who read it. As such, it could be implemented as a post collection phase when being written to the buffer for processing, even though at an increase in overhead, some messages would be collected and discarded as not relevant.
The option should be available for both mqat.ini and subscriptions.
Do not place IBM confidential, company confidential, or personal information into any field.