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,
Post an idea
Upvote ideas that matter most to you
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.
Classic CDC to Support column-level CodePage selection
I work at a financial institution where we process mainframe information in EBCDIC CodePage 037, 838, 930 and 937. Currently we plan to work around a CodePage limitation by generating four separate subscriptions; one for each EBCDIC CodePage we want to support. It would be much more pleasant to have a single subscription where we can choose to transform each column of data according to one of the EBCDIC CodePages we require. This means we would be able to dynamically select an EBCDIC CodePage to transform at the column level rather than at the subscription level. I imagine this would also be more efficient.
Do not place IBM confidential, company confidential, or personal information into any field.