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.
Idea Review. Thank you for taking the time to raise this enhancement request and for the deeper discussion which you have had through our service channel in case (TS015490225). For the benefit of other readers, this case revolves around a small change to the output style of the mqsilist command between different mod releases of ACE 12. The mqsilist command provides different levels of detailed output depending on the options used. For example you can issue "mqsilist YOURNODENAME" or for more detailed output you can issue "mqsilist YOURNODENAME -e YOURSERVERNAME". In the latter case, response codes from the administration API call (which is made to the server but transmitted through the integration node process) can help the command indicate whether the server is fully running or is in the middle of the process of starting. This can be reported using BIP9364E ... for example:
BIP9346E: The request cannot be processed as the integration server 'default' has not completed startup.
An administration request has been made to the integration server 'default' but the request cannot be processed as the integration server is starting. Re-issue the request when the integration server has completed startup.
In the case of "mqsilist YOURNODENAME", we do not inspect the specific responses per server when reporting the node's status. The described behaviour which was discussed in the service case at version ACE 12.0.8.0 is correct, and is preferential compared to ACE 12.0.2.0 where we did not display indidivual info about the servers at all. Given this, we feel that as implemented at 12.0.8.0 and above, users already have good flexibility to either get more detailed status per server, or a node level summary from mqsilist. For automated processes outside of ACE which are designed to be checking on status, we recommend using the product's administration API directly as opposed to attempting to scrape the output from commands such as mqsilist, which as you've discovered may potentially change between releases when we feel that there is a chance to improve the level of detail provided by the command.