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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Z/OS Connect to have an option to allow mainframe clients response body data to be returned to the calling program without going through JSON to copy code conversion. Currently there are two issues with how the JSON to copy code conversion is handled
Any change to the JSON reply has a risk of causing Z/OS Connect API call to fail. The change could be a new variable or bigger array. Non-Z/OS Connect consumers are resilient to small changes in JSON data, Z/OS Connect should also be so.
A second problem is due to Z/OS Connect requirement of a 100% match of JSON variable to copy code it means that large and varying replies can require huge amounts of program working storage. In the worst case, as we have found, it is not possible to use the copy code due to COBOL compiler limits. Non-Z/OS Connect consumers of JSON data use what is returned instead of theoretical maximum data.
Z/OS Connect is not the best place to process JSON data, this is better done in the client program which offer more flexibility. Z/OS Connect shouldn't be validation a reply, the client program should be doing that.
Idea priority | Low |
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.
Thank you for raising this Idea.
This requirement is now addressed by API requester for OpenAPI 3, available from V3.0.65, APAR PH51617: https://www.ibm.com/support/pages/apar/PH51617
For further details, see this section of the z/OS Connect Documentation: https://www.ibm.com/docs/en/zos-connect/zos-connect/3.0?topic=concepts-zos-connect-enhancements
This requirement has been re-evaluated and accepted into our future plans for z/OS Connect releases. This capability will be implimented into API Requester for OpenAPI 3.
This requirement has been evaluated. Looking at current plans, it is not likelythat this would be implemented in future zOS Connect EE releases, so correspondingly this requirement is being rejected. You have an opportunity to resubmit in twelve months time if you wish it to be considered then.
Could this be change to high priority? We have found that we are unable to use Z/OS Connect in its current form with external to the mainframe APIs due to failures in the JSON conversion which could be easily resolved in the calling mainframe client program.