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 PL/I Compilers
Created by Guest
Created on May 22, 2018

Simplify Json builtin routines

1) We tried the json commands in PL/I, but sorry, they are programmer unfriendly.

If I want to use them well I have to write a program around them and this is really not what I want.

2) a variable type json would be interesting ...

sample json get:

{ "passes" : 3,
"data" :
[
{ "name" : "Mather", "elevation" : 12100 }
, { "name" : "Pinchot", "elevation" : 12130 }
, { "name" : "Glenn", "elevation" : 11940 }
]
}

dcl name char(20);
name = jsonget(jsonstring,"data->1->name")

--> if this is not matchable, then return a null value

dcl namearray[5] char(20);
name = jsonget(jsonstring,"data->name")

--> if this is not matchable, then return a null value, empty elements can be filled with a null value; too many elements should result in an exception

dcl passes bin fixed(15);
passes = jsonget(jsonstring,"passes")

-> if passes not in json, then return a null value

sample json put:

jsonput(json, variable, path*) -> * path is the way to the jsonelement, where the new tag should be inserted, if it is not in the current json, it should be inserted. If not there, then root is used.

sample:

dcl jsonstring char(2000); -> here maybe a varialbe type json would be better, to optimize pl/1 working with json.

dcl name char(20) init('peter');
dcl number bin fixed(15) init (200);

jsonput (json, name);
jsonput (json, number);
jsonput(json, name, "data"

result:

{ "name" : "peter",
"number" : 200,
"data" : { "name" : "peter",
"number" : 200
}
}

Hope I described it in a good way. Main thing is: as simple as possible to use as much optional as possible.

Idea priority Medium
  • Guest
    Reply
    |
    Dec 8, 2020

    This requirement has been re-assessed.  It is not likely that this will be implemented in the next 12-24 months and so it is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

  • Guest
    Reply
    |
    Jun 27, 2018

    This will take some redesign etc, but it is a good idea