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
I would like to have an option of automatic naming and building of security controls at define time of objects, where applicable. For example, when defining a receiver channel for a certain qmgr QMX, at a qmgr QMY, there really is no need that examples like QMX_TO_QMY, QMX.QMY, QMX.TO.QMY, CH.QMX_QMY etc. are all allowed. I think one convention should be chosen and kept consistently, for future definitions of course. Plus, why not adding at the same time an appropriate CHLAUTH record of type QMGRMAP? That would allow only connections from sender from QMX, of course. Extrapolate this example to all applicable cases.
Idea priority | Medium |
RFE ID | 77988 |
RFE URL | |
RFE Product | IBM MQ |
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.
we are considering designs that would help to satisfy this requirement for a future version of MQ
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
This is connected to
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=67095
which was rejected without explanation.