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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Modern Change Management processes require all scripts to be both input format verified and peer reviewed. MQ Appliance shops running remote scripts to restore a Queue Managers or to add new MQ objects would use this feature. runmqsc -v -mq_appliance <input.file would verify all commands conform to the MQ Appliance format when executed on another platform (i.e. Linux, AIX, Windows etc.). Alternatively, if the MQ Appliance could be adapted to handle the -v (Verify) option (which Architecturally I do not believe is possible); then, that would be fine as well. Large customers who want to migrate to the MQ Appliance must be able to meet all of the requirements of modern change management processes when administering changes.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Thanks Mark.
We were able to successfully test MQSC configuration file Verification and output to the /tmp directory on the MQ Appliance (with the assistance from Glenn Gettman) and agree this is satisfactory for our company's DEVOPS change management process. This idea can be withdrawn.
Adding cross-platform verification is not something we would plan to do. It would not just be an appliance matter, but - for example - doing Linux verification on Windows. That cross-platform knowledge is not available in the MQSC processor.
You can already do MQSC verification on the appliance, but you have to be running it directly. Not via a client connection.