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
Have the Queue Manager produce a read only message showing all the parameters its running with
A queue manager gets many of its characteristics from the qm.ini file. Environment variables set for the mqm ID also dictate how the Queue Manager behaves. Currently there is no way for an MQ Admin to know what all these values are with an MQ Client based tool. The MQ Admin is forced to log onto the server, or rely on a local agent to be installed on the MQ server that they then interact with.
This Request For Enhancement is to have the Queue Manager allow suitably authorized MQ Client based applications to read these attributes. A running Queue Manager knows what all the characterstics are for its logging details (type, size, number, buffer, etc). Could the Queue Manager dump all these attributes that are not available via runmqsc into a new queue (maybe SYSTEM.QM.INI.VALUES) upon start up and allow only suitably authorized apps to read the message(s) on this queue? If the messages are persistent and small, maybe keep old ones on the queue and just add a new one each time the QM restarts, to provide an Audit trail or History of what parameters this Queue manager ran with.
If the Queue Manager is aware of what environment variables are set, it would be helpful to have those values captured as well. For example, is MQS_REPORT_NOAUTH set to TRUE.
Since WMQ now stores these configuration setting consistently across all distributed platforms. being able to retrieve these using a PCF command would be beneficial. It would allow a configuration for a QM to be checked without the MQ admin having...
hi Sir, Currently MQ Manager doesn't have a mechanism to check with what value of MAX Channel Connection it running at? We can check qm.ini for the Max channel count specified or if no value is present in qm.ini we can assume a default value of 10...
Do not place IBM confidential, company confidential, or personal information into any field.