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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
This requirement is addressed by z/OS Connect V3.0.55 / APAR PH43628: https://www.ibm.com/support/pages/apar/PH43628
For further details refer to the “ Developing APIs with the z/OS Connect Designer” topic in the z/OS Connect OpenAPI 3 Documentation:
https://www.ibm.com/docs/en/zosconn/zos-connect/3.0?topic=developing-apis-zos-connect-designer
Agreed. Our API Expert took one look at the channel and container response, and asked me to remove the extra layers, as they are unnecessary. Unfortunately I am unable to.
We do not want to move to comm area simply because the channel container approach gives us a more nested structure. Our Ask is to allow custom modification of the levels of Hierarchy one intends to have on the JSON, such that we can service our customers better with less compluicated structures and leverage the benefits of containers.
We do not want to move to comm area simply because the channel container approach gives us a more nested structure. Our Ask is to allow custom modification of the levels of Hierarchy one intends to have on the JSON, such that we can service our customers better with less compluicated structures and leverage the benefits of containers.