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 Oct 7, 2015

Automatic standard naming & security controls @ define time

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 Product IBM MQ
  • Guest
    Oct 20, 2015

    we are considering designs that would help to satisfy this requirement for a future version of MQ

  • 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
    Oct 9, 2015

    This is connected to

    which was rejected without explanation.