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.


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
    Reply
    |
    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:

    https://integration-development.ideas.ibm.com/ideas/APPC-I-382

    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.