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
Workspace COBOL Compilers
Categories z/OS
Created by Guest
Created on Mar 14, 2024

JSON PARSE WITH DETAIL specified at run time

It would be helpful if WITH DETAIL phrase of JSON PARSE can be enabled/disabled at run time by application logic.

We continue to struggle with problem resolution when specific use cases cause unexpected results from web service calls, resulting in Parse failures. Displaying the payload during error processing is discouraged since it may contain sensitive data that should not be included in job logs. Modifying production source code for problem resolution is discouraged. Reproducing in a test environment is extremely challenging for large applications with many data dependencies.

The WITH DETAIL phrase displays too many messages in job output. Many of the messages are expected conditions for many applications. After testing, WITH DETAIL is removed for production code in order to reduce job logs and distracting LEMSG output.

Possible solution:

WITH DETAIL <data-name>

Where data-name references a variable that contains a value such as YES/NO; ON/OFF; TRUE/FALSE; T/F; Y/N

A Blank value would be interpreted as False or No.

In this way, the application has more options to gather additional information regarding the nature of the error.

External parms for debugging set in JCL input cards or parameter files can be leveraged to set WITH DEAIL on or off as needed and rerun the application.

Alternatively, when a JSON document fails to parse properly (according to error handling decisions in the application), the data-name variable can be set ON and the exact same parse statement re-executed automatically within the application to display the detail for this single JSON document.

Current work around is to code the exact same PARSE statement twice; once omitting WITH DETAIL, and once WITH DETAIL. Error handling executes the one WITH DETAIL when needed. This is risky due to needing to maintain two exact copies of code and ensure they are kept up to date with changes. It is very likely the WITH DETAIL copy will Not receive all the same code changes, resulting in misleading problem resolution.

Idea priority High
  • Admin
    Basil Kanneth
    Reply
    |
    Jun 2, 2024

    Thanks for the reply. We will focus on https://bigblue.aha.io/ideas/ideas/COBOLVUE-I-383 and updates will be made via that idea.

  • Guest
    Reply
    |
    Apr 10, 2024

    Yes, 383 does provide the details needed for better error handling.

    With this idea 382 it was thought that maybe this would be easier (and faster) to implement. And applications could flip the switch very easily for a quick diagnostic when needed. While 383 does provide more control within the application, it also requires more code to be written. Some teams will prefer solution 382, others will prefer 383.

    Either idea will be a great help for improved error handling when parsing JSON. Both would be great.

  • Admin
    Basil Kanneth
    Reply
    |
    Apr 10, 2024

    Hi, by implementing idea https://bigblue.aha.io/ideas/ideas/COBOLVUE-I-383 , may we know if it will also satisfy this idea (COBOLVUE-I-382) for you?