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 Delivered
Workspace z/OS Connect
Created by Guest
Created on Aug 17, 2016

Provide support to send DBCS characters in unescaped form in z/OS Connect EE using REST API

Currently z/OS Connect EE send DBCS data in unescaped form when using REST API , however the customer in Japan which we are currently trying to sell z/OS Connect EE will have C and Java programs as the REST client.
If the JSON data is sent in escaped form, they will need to develop some conversion routine for the escaped characters, which will increase their development cost, and could also adversely impact performance depending on the amount of DBCS characters, as well as the increase in size of the JSON data.

They also foresee future use of the REST API from other clients, and there could be cases where they use a product which cannot handle escaped DBCS characters.

It would be best if they can unify their JSON service access using API's without worrying about handling escaped DBCS characters in their programs.

Idea priority High
  • Guest
    Reply
    |
    Nov 2, 2016

    This requirement is addressed by z/OS Connect Enterprise Edition V2.0 APAR PI69668 (V2.0.4). For further details, refer to the APAR description:

    http://www-01.ibm.com/support/docview.wss?crawler=1&uid=swg1PI69668

  • Guest
    Reply
    |
    Aug 19, 2016

    there is UTF8 support in z/OS Connect EE. We'll investigate further to determine whether that would meet this requirement