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 Functionality already exists
Workspace z/OS Connect
Created by Guest
Created on Mar 31, 2026

I’d like you to enable Base64 encoding.

I’d like you to make it possible to use Base64 encoding to prevent truncation, alteration, or garbling when setting values in JSON that may contain control characters or arbitrary bytes in the 0x00–0xFF range, and/or to embed (serialize) images, keys, certificates, and other binary attachment data into JSON “as strings” and send them over HTTP.

Idea priority Medium
  • Admin
    Beth Williams
    May 5, 2026

    This IDEA has been assessed by the team.
    The recommended approach would be that the base 64 encoding and decoding in the COBOL or PL/I application is performed prior to sending the data (for API requester) or upon receipt of the data (for API Provider). Using the recommended approach the customer can decide in their applications which JSON strings require special treatment. This link provides great examples of how to handle Base64 encoded data in both COBOL and PL/I: https://github.com/cicsdev/base64.
    There is also the ability to do this in JSONata by using the function $base64encode(), as a workaround. More information on this can be found here: https://docs.jsonata.org/string-functions#base64encode
    Whilst the solution available in the product today is slightly different to the approach suggested in this IDEA, it does enable you to convert an ASCII string to a base 64 representation. As such this IDEA is being closed. If you have any further requirements in addition to the capability that exists today, we would welcome another IDEA.

  • Guest
    Apr 1, 2026

    In addition, my customer is requesting API Provider to decode Base64-encoded data in the JSON payload prior to passing it to the SOR.