IBM Data and AI Ideas Portal for Customers


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

Post 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 product management 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 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.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Created by Guest
Created on Jun 9, 2020

Allow mapping of character fields > 254 Bytes in CDA

Currently Classic Data Architect (CDA) skips over any COBOL Copybook field greater than 254 Characters. It does not issue a warning or error it just skips the field and goes on to mapping the next field. This request will have CDA map character fields > 254 bytes to a target mapping. This is used with Optim Archive and Classic Federation when decommissioning applications from the mainframe.

Needed by Date Aug 28, 2020
  • Guest
    Jan 21, 2021

    Similar requirement for customer implementing VSAM to Kafka replication. Customer has many filler type of fields which larger than 254 bytes. Even if it does not support field length larger than 254, it will be nice to automatically generate fields of 254 bytes.