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 Delivered
Workspace z/OS Connect
Created by Guest
Created on Jul 29, 2020
Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit ZCEE-I-100 Ability to specify the client side interface of an API, created in the API Editor.

Removing additional COBOL layer from API payload Merged

z/OS Connect API Toolkit
~~~~~~~~~~~~~~~~~~~
When COBOL copybook structures starting at levels greater than 01 are imported into the z/OS Connect tooling, an 01 level seems to be assumed and inserted into the Service and hence API structure with the file name of the copybook.

For example - 1 :
file - CPYBOOKA.cpy:
03 GROUP-A.
05 FIELD-A PIC X(1).
05 FIELD-B PIC X(1).
05 FIELD-C PIC X(1).

Results in JSON:
{
CPYBOOKA : {
GROUP_A: {
FIELD_A: "",
FIELD_B: "",
FIELD_C: ""
}
}
}


Related to this, fields included in the Service within group levels of a Service are controlled by the group level. So unchecking the Include flag from a group also unchecks the Include flag from all fields within the group. Including one of the fields within a group then subsequently places the Include check mark on the group.

Required:
~~~~~~~
Ability to suppress a Group Level field from an API structure while independently allowing fields within that group to be Included in the Service/API at the same level as the containing group.

Granted there are cases where this may not be doable (e.g. OCCURS, REDEFINES)


so for the above example, at a minimum we should be able to suppress CPYBOOKA from displaying in the API without affecting the underlying structure:
{
GROUP_A: {
FIELD_A: "",
FIELD_B: "",
FIELD_C: ""
}
}


And possibly remove both group levels resulting in:
{
FIELD_A: "",
FIELD_B: "",
FIELD_C: ""
}

Idea priority Low
  • Guest
    Reply
    |
    Aug 5, 2020

    Thank you for raising this requirement.

    The requirement being expressed here is a specific example of a more general need to "Defined the JSON schema structure independently of the copybook structure". This is already part of our long term delivery roadmap and as such It is being closed as a duplicate of existing RFE 88702:
    http://www.ibm.com/developerworks/rfe/execute?use_case=viewChangeRequest&CR_ID=88702

    Please add your support by voting and/or commenting on it.