Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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
Categories z/TPF
Created by Guest
Created on May 2, 2016

Support UTF-EBCDIC in the B2B Parser for JSON and SOAP

Recently UTF-EBCDIC was added functionality for the B2B Parser which has been very helpful. We recently determined that JSON and SOAP was not included in that support. We would like JSON and SOAP to be included in the support included under the B2B Parser.

Idea priority Medium
  • Guest
    Reply
    |
    May 8, 2017

    IBM does not intend to implement this request.
    UTF-EBCDIC was added to allow Unicode data to be handled by the XML parser. The JSON parser already handles Unicode data however. If any data is stored, it should really be converted back to a more standard Unicode format from UTF-EBCDIC using the tpf_convert_ebcdic_to_unicode API as UTF-EBCDIC is a XML parser only encoding. A more standard format of UTF-8 is supported by both JSON and DFDL parsers. DFDL can potentially be used to resolve having to worry about something that is in either JSON or XML format since very little code needs to change for it to handle either. In additional, DFDL will handle the differences in storing data in different encodings (EBCDIC v UTF-8) and make such processing invisible to the z/TPF application.