Skip to Main Content
Cloud Platform

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 portals, 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.

Status Future consideration
Created by Guest
Created on Apr 23, 2019

Fix IMS Stub DFDL Schema Handling

Improve error handling in IMS transport stub code to support DFDL schema errors.

Currently due to the lack of multiple operation support in an IMS transport stub (enhancement request 132307) a single IMS transport stub cannot properly support DFDL message schema encodings. If the stub receives a message with a different DFDL schema, an error occurs and the stub does not continue with any additional processing, messaging steps/logic, or send any response (no error code, no passthrough, nothing).

Practically, this prevents applying a DFDL schema to any stub that receives mixed messages from a source system - and requires processing the encoded values directly or dispatching the message to a worker stub for processing based on type.

Please see support ticket number attached to this request for related files.

Idea priority High
RFE ID 132308
RFE URL
RFE Product Rational Test Workbench
  • Guest
    May 28, 2019

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.