Skip to Main Content

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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

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.

Status Future consideration
Created by Guest
Created on Dec 6, 2013

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.

Idea priority Low
RFE ID 42528
RFE Product IBM MQ
  • Guest
    Jun 3, 2016

    In today's Change Management culture, it's increasingly important to validate production changes through some validation step. The validation step is needed to decide if a backout is required.

    In this situation, the only validation tool available is IEBIBALL and wait to see if MaxChannels/MaxActiveChannels errors appear in AMQERR01.LOG under full prod load.

    Even though this change will go through all lower environments first, I cannot generate sufficient connections to max out the channels. SHARECNV(5) configured on the SVRCONNs makes it more impractical to max out the channels.

    I do vote for this RFE!

  • Guest
    Dec 15, 2015

    While we may not do a solution exactly as suggested here, we are considering mechanisms to show more of the attributes that are currently set in the ini file.

  • Guest
    Oct 15, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM MQ

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM MQ

  • Guest
    Sep 13, 2015

    z/OS queue managers show many of these parameters at startup, but even on z/OS there is no administrative interface to query many of them. I agree with other comments that there should be PCFs and runmqsc commands to inquire on all qm.ini and environment variables that can affect the operation of a qmgr.

  • Guest
    Feb 18, 2014

    I can see one new PCF command to display what are the current values in the qm.ini file.

    And a modification to the Inquire Queue Manager or Queue Manager Status PCF command to show what qm.ini setting the QM is currently running with.

    They could be different because the qm.ini file is not reread after the QM is started.

    And another new command to update the qm.ini file.

    The goal here is to give the MQAdmin the ability to truly manage the QM remotely.

    And then maybe a PCF command to instruct the QM to restart.

  • Guest
    Jan 3, 2014

    Perhaps this could be implemented as a new PCF type. Or as a retained publication on a system topic as suggested below

    I also agree that the ability to generate the qm.ini settings from the running Queue Manager (unix-like only?) would be useful. There are a lot of unpublished defaults so only populating a generated qm.ini with values that differ from the default would be more readable.

    One last suggestion would be where the Queue Manager detects an invalid qm.ini attribute and ignores it, write an entry in the Queue Manager's error log.

  • Guest
    Dec 20, 2013

    This RFE could be extended to embrace the broad subject of queue manager configuration.
    1. during startup
    - display all relevant environment variables encountered.
    - display all ini setting encountered.
    - just prior to 'AMQ8003 Queue manager XX started', display all configuration and runtime options in effect.
    2. runmqsc command 'display qmgrst' or other utility program:
    - display all these values
    - display all other statuses, such as number of open file descriptors, # channel connections, number of each object type (ql, qa, qr, qm, sdr, rcvr, topic, auth records, etc).
    - makes values available to all applications (client or otherwise)
    3. utility program to generate file qm.ini based on current values, to include all known values; file would be backed up by using along with other relevant queue manager files.

  • Guest
    Dec 6, 2013

    Rather than a special case of a message which can only be received, and the system has a way to overwrite it, perhaps it would make for a more consistent interface if it was implemented as a retained publication on a topic.

    Fantastically useful idea though.

    Neil C.


Max Channel Connection Count

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...
about 7 years ago in MQ, MQ Advanced & MQ Appliance 1 Future consideration

New PCF command to inquire qm.ini settings

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...
almost 9 years ago in MQ, MQ Advanced & MQ Appliance 2 Future consideration