Skip to Main Content
Integration

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to ideasibm@us.ibm.com for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.

ADD A NEW IDEA

FILTER BY CATEGORY

All ideas

Showing 1841 of 1841

Access to mqsisetdbparms identities

Read-only access mqsisetdbparm-set identities from code (JCN, .NET Compute, PHP Compute, ESQL) within a flow.
almost 10 years ago in App Connect 4 Future consideration

Default behaivor of HLQ when sending from z/OS to distributed

The design of the product when sending files from z/OS to distributed is to lose the first HLQ. Probably they were thinking about this HLQ is the USERID, but in production environments it is not common. The RFE is to change this default behavior t...
almost 10 years ago in MQ, MQ Advanced & MQ Appliance 3 Not under consideration

MQTT Device Daemon for ARM V7 and later

It is necessary to support more current versions of the ARM platform (V6,V7) and Linux kernels (V3) - most embedded systems currently in development or test are based on Cortex or Nvidia chip sets
almost 10 years ago in MQ, MQ Advanced & MQ Appliance 3 Not under consideration

WS-Security with specific providers

Enhancements in policy set editor to address the following things: In the policy set editor, it is hard to relate the GUI options to what will appear in the headers. The policy set editor affords no way to create custom fields where the WS-Securit...
almost 10 years ago in App Connect 3 Not under consideration

Help link on node

Each node would have a clickable property, accessible by right-clicking on the node, that would link to that node's Info Center article.
almost 10 years ago in App Connect 3 Future consideration

SCP suupport in File nodes

SCP support in FileInput and FileOutput nodes.
almost 10 years ago in App Connect 3 Future consideration

Support in EmailInput node for creation of custom folders and moving email to specified folders.

Support in EmailInput node for creation of custom folders and moving email to specified folders.
almost 10 years ago in App Connect 4 Future consideration

WMQ Support for MSCS Majority Node Cluster

Please see below which is a previous response to a RFE – we are basically following up this original query and trying to determine if/when support will be available for WMQ using MSCS Majority Node cluster. When queried last time we were told it w...
almost 10 years ago in MQ, MQ Advanced & MQ Appliance 3 Not under consideration

A requirement for larger messages to be supported in a future release of WMQ FTE.

The customer was unable to create large messages on z/OS queue using File to Queue .The state message is held on the SYSTEM.FTE.STATE. queue. This limits the maximum output message size that can be written to around 33MB as you observe. There is c...
almost 10 years ago in MQ, MQ Advanced & MQ Appliance 2 Not under consideration

Add SQL.HostName as a new Broker Property

Currently, one has to use a JCN or various schemes to get the hostName available in a message flow. Making it a standard Broker property would make a developer's life simpler.
almost 10 years ago in App Connect 4 Future consideration