Integration
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 updates on 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
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.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
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!
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.
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
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.
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.
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.
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.
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.