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
In the z/OS Connect OpenAPI3 Designer, "JSONCHANNEL" is always used as a CICS channel name and there is currently no way to change CICS channel name when we invoke CICS Channel program via z/OS Connect.
It means if customer has CICS Channel programs which require other channel name than "JSONCHANNEL", he must modify them to invoke through z/OS Connect.
It may be a restriction for customer who is going to expose his channel program as REST APIs via z/OS Connect.
So CICS Channel Name should be configurable in the z/OS Connect OpenAPI3 Designer.
Idea priority | Medium |
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 this IDEA.
This is a strategic requirement that is part of our long term roadmap. As such we are accepting this IDEA for "Future Consideration" for OpenAPI 3