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 Not under consideration
Workspace CICS Transaction Server for z/OS
Categories Other
Created by Guest
Created on Nov 4, 2021

RELATED IDEAS

Specify the CCSID in the DFHLS2JS utility so that the char data in the data structure can be encoded independently at runtime

We can use the DFHLS2JS utility in the CICS JSON assistant to create from a copybook a bundle that contains the JSON file. The JSON file is normally used again in a CICS transaction. Now it is the case that we want to reuse the utility for another procedure and have encountered the problem which was already described in this ticket (Document number: 6145221): https://www.ibm.com/support/pages/syntaxerror-jsonparse-unexpected-character-when-processing-json-files

We want the possibility to specify a target CCSID which does not map to code page 1047 from the native Java procedure by default. So this CCSID is not dependent at runtime.

Idea priority Low
  • Guest
    Reply
    |     Feb 8, 2022

    The CICS assistants already provide CCSID and JSON-SCHEMA-CODEPAGE parameters.

    CCSID specifies the CCSID that is used at run time to encode data between the application program and the JSON binding file.

    JSON-SCHEMA-CODEPAGE specifies the code page that is used to generate the JSON Schema documents.

    No further enhancements concerning codepages are planned.

  • Guest
    Reply
    |     Jan 21, 2022

    The goal is to work with the generated JSON schema in the encoding which I specified (e. g. 1140). The problem is the encoding of the generated JSON schema that is stored. If I add the parameter JSON-SCHEMA-CODEPAGE=UTF-8 then the JSON schema is generated in UTF-8. On the mainframe we work with codepage 1140. If I change the JSON-SCHEMA-CODEPAGE=1140 then the generated JSON schema is generated like before to the default encoding with the special symbols.

  • Guest
    Reply
    |     Jan 4, 2022

    Please could you clarify the requirement, because it is not clear what is being asked for.

    From the description we understand you are using DFHLS2JS to generate a JSON schema. However, what do you mean by "The JSON file is normally used again in a CICS transaction" ? The schema wouldn't normally be used at runtime.

    The RFE title says "Specify the CCSID in the DFHLS2JS utility so that the char data in the data structure can be encoded independently at runtime". This sounds like you are asking for what the CCSID parameter of DFHLS2JS already provides.

    The linked to support document refers to the encoding of the generated JSON schema itself. The simplest fix there would be to set the JSON-SCHEMA-CODEPAGE parameter of DFHLS2JS and have it generated in UTF-8.

    There appears to be confusion between the encoding of the schema with the encoding of the data at runtime, something that should be configured using the CCSID parameter.

    So either the existing CCSID or JSON-SCHEMA-CODEPAGE parameters should address the requirement depending upon what the requirement actually is.

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.