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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Current implementation of DFDL parser doesn't support ICU's "fallback" mapping, whereas MRM parser does.
DFDL parser only supports "good one-way" mapping for Unicode -> CCSIDxxx single directional mapping. （Fallback mapping is denoted by a precision indicator value of '1' in a conversion map file, whereas "good one-way" mapping has a precision indicator value of '4'.）
This is an issue because DFDL parser uses conversion map file provided by ICU which includes lines with "fallback"(1) indicators when converting Japanese characters.. DFDL parser cannot perform conversion for these code points and cause conversion errors.
In order to perform comprehensive conversion with DFDL parser, customer needs to obtain conversion map file from ICU web site and change the indicator "fallback" to "good one-way" for each CCSID customer use. This will pose every customer who require such conversion functionality additional costs for investigations, implementation, and testing.
Lack of fallback mapping functionality can also be a road block for current WMB user to migrate MRM to DFDL.
Therefore DFDL parser should support fallback mapping of ICU as MRM does.
Do not place IBM confidential, company confidential, or personal information into any field.