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.

Add a new idea Subscribe
Status Delivered
Workspace COBOL Compilers
Created by Guest
Created on Mar 17, 2016

RELATED IDEAS

Cobol V6 - add "WITH ENCODING" option on JSON GENERATE statment

In new Enterprise Cobol V6, statment "JSON GENERATE" produce only UTF-8 or UTF-16 document, depending on PICTURE clause of receiving data.

Using UTF-8 / UTF-16 values on z/OS EBCDIC system is not very easy nor usual (and not human readable on EBCDIC system)...

JSON GENERATE statment need a "WITH ENCODING" option like XML GENERATE statment.
The defaut encoding should be the programme encoding (compiler option CODEPAGE(ccsid)).

Document can be converted later, with EDCICONV or other utility or system option (FTP : SBD=(fromccsid,toccsid), Apache web server CharsetSourceEnc / CharsetDefault, ).

Idea priority Medium
  • Admin
    Basil Kanneth
    Reply
    |     Aug 8, 2024

    This idea was re-evaluated and delivered in Enterprise COBOL for z/OS, V6.4 via the October 2023 PTF

  • Guest
    Reply
    |     Aug 7, 2024

    Delivered !

  • Guest
    Reply
    |     May 26, 2016

    Not sure anyone will read this, but it is worth noting that the IBM z/OS JSON parser callable services (see OA46757.pdf) support EBCDIC as default:

    "All input data into the JSON parser is assumed to be in EBCDIC encoding (codepage 1047) prior to making any z/OS JSON parsing service call. Any JSON text received by the application in another encoding format must first be converted to EBCDIC before it can be input into the parser via either the parse (HWTJPARS) or create (HWTJCREN) service calls."

  • Guest
    Reply
    |     Apr 5, 2016

    We believe that UTF-8 is required for exchanging JSON document, but not necessarily to build a JSON document.
    We did not wait Cobol V6 to produce JSON documents with Cobol. These documents are created in EBCDIC and are converted into UTF-8 at the time of dispatch (by CICS: EXEC CICS WEB SEND ... HOSTCODEPAGE (ebcdic) CharacterSet (utf-8))

  • Guest
    Reply
    |     Mar 24, 2016

    JSON by standard, is intended to generate UTF-8 only.

    The workaround is to generate a UTF-8 file and then use the MOVE function to convert it.

    Since it is currently following the standard, and since there is a workaround, we will be rejecting this RFE.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.