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 for resolution. For more information about IBM's Ideas program visit

Status Not under consideration
Workspace App Connect
Created by Guest
Created on Nov 10, 2021

Native processing CICS Containers and Channels in mapping node.

Traditionally the api for communicating with a CICS program utilized a single COMMAREA for sending and receiving data. A COMMAREA has been limited to a single data structure passing no more than 32K of data. To address these limitations IBM introduced a new api utilizing Channels and Containers, in 2005, where a CICS program can be passed a Channel which contains 1-many Containers each having unique data structures. For most modern CICS programs this is now the preferred api to use. A typical pattern might include a single Container for input (but some will have more) and may return multiple containers for output. ACE supports the use of Channels and Containers with the CICS Request Node. The difficulty is that a CICS Channel is represented in ACE as a message collection. This poses a difficulty in that when a CICS Channel has more than one Container it cannot be natively mapped in the map node and must be mapped using an ESQL node or a Java node. This is a step back from WESB which allowed you to use the mapping node to address all of the CICS Containers within a CICS Channel. We are focused on driving reducing the use of the ESQL and Java nodes in order to simplify the programming experience and reduce the skill level needed for what should be simple mapping exercises. We would like to see the mapping node enhanced so that a CICS Channel with multiple CICS Containers (i.e. a message collection) can be created and parsed within a single mapping node. This will allow us to avoid using ESQL or Java nodes when there are more than one CICS Containers like we are currently constrained to. This will enhance programmer productivity and ease support bringing ACE more in line with features that WESB (WebSphere Enterprise Service Bus) used to have.
Idea priority Medium
  • Admin
    Ben Thompson
    Nov 25, 2021

    Idea / RFE Review. Thank you for taking the time to raise this enhancement request. We agree that being able to use the graphical mapping node to interact with Collection trees would enhance the product. In fact we already have this suggestion noted here:

    To consolidate support for this request, please vote / add comments of support to this idea. We will also post a cross-reference to this idea too, to ensure that the suggested use case is noted. Many thanks.