Skip to Main Content
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
  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 (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.


ADD A NEW IDEA

MQ, MQ Advanced & MQ Appliance

Showing 172

Increase MQ Sender Channel CONNAME parm 48 Character Limitation on z/OS MQ.

Change the 48 character length limitation on the channel parameter CONNAME to increase to handle longer host names
almost 3 years ago in MQ, MQ Advanced & MQ Appliance 1 Future consideration

Allow dedicated separate storage on a queue level basis for MQ on Windows and Unix

Similar to z/OS, we would like the ability to have one or more queues use a separate and dedicated of storage on Windows and Unix MQ systems.
almost 11 years ago in MQ, MQ Advanced & MQ Appliance 7 Future consideration

Application Transaction Tracing through MQ Appliance

This is critical to give customers using MQ appliance the ability to have end-to-end observability for their application stacks. Currently, customers cannot trace transactions through the appliance, creating a 'black box' scenario. This is a sever...
almost 2 years ago in MQ, MQ Advanced & MQ Appliance 0 Future consideration

When using the v3 version of the MQ REST API’s Get Message service: GET /messaging/qmgr/{qmgrName}/queue/{queueName}/message we would like the MQ Put DateTime returned in one of the HTTP response headers which it currently is not.

We feel that this is a valuable piece of information to obtain when reading queued messages from MQ to know when a message was first written to the queue
over 1 year ago in MQ, MQ Advanced & MQ Appliance 2 Future consideration

MQ Webconsole: Ability to get messages via alias queue's with get Enabled

MQ users (developers, testers, administrators etc) could benefit from ability to view messages via alias queue's with get Enabled. Right now this feature is only for local queue's available. In some environments there is no browse permission for l...
8 months ago in MQ, MQ Advanced & MQ Appliance 1 Future consideration

Enhancements needed for MQ Web Console to rule out third party administration tools

We are planning to move away from MQExplorer and other third party administration tools and switch to MQ Web Console as the go-to utility, however most of the basic functionalities which we use on our day to day basis do not exist in the MQ Consol...
over 4 years ago in MQ, MQ Advanced & MQ Appliance 6 Future consideration

We would like a service that when given a queue, a list of messages in that queue including the headers: position, priority, put datetime, size, source, replayed, message id, and transaction id are returned. Currently we can only get the id of the messages.

We would like a service that when given a queue, a list of messages in that queue including the headers: position, priority, put datetime, size, source, replayed, message id, and transaction id are returned. Currently we can only get the id of the...
about 1 year ago in MQ, MQ Advanced & MQ Appliance 1 Future consideration

Add support for LDAPS in MQExplorer and JMSAdmin

When connecting to a remote JNDI repository via MQExplorer or JMSAdmin you can use LDAP. If LDAPS is not available (confirmed in Case TS011889627) we are forced to use LDAP and thus our data is unencrypted on the wire. MQExplorer and JMSAdmin shou...
almost 2 years ago in MQ, MQ Advanced & MQ Appliance 3 Future consideration

REST API for adminstration

in MQ 9.3.3 REST api for messaging was enhanced to run over CCDT; meaning to more SDR/RCV channel and REST endpoint would initiate the client conn connection. For admin API we need SDR/RCV channels; and in a large or small env; it is a pain settin...
over 1 year ago in MQ, MQ Advanced & MQ Appliance 3 Future consideration

Readonly access to MQ Console on CP4I

We are running EUS version of MQ on CP4I 2020.4.1 (Common services Operator version is 3.6.5) on Openshift 4.6.42 on Azure cloud. We require a way to configure Read-only access to MQ Console which seem to be missing. The login is facilitated by co...
about 3 years ago in MQ, MQ Advanced & MQ Appliance 2 Future consideration