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.
We'd like this RFE to be re-considered .
I hadn't noticed it had been closed as Delivered . I provided no specific use cases, when I opened this RFE, and I'm not sure who provided the use case that had been referenced in the clarification that led to its close-as-delivered determination
We have many APIs that fall under large Umbrella base paths ..
For example we will have many APIs that need to share base path: "/provider/v1/zos"
Many others that need to share: /member/v1/zos
etc.
Thanks, Dave
Following further clarification of this use case, we have assessed that the capability requested by this RFE is currently available in z/OS Connect EE V3.
The use case has been clarified as follows:
API 1: Base Path = /v2/customers/
API 2: Base Path = /v2/branches/
API 3: Base Path = /v2/catalog/
The base paths for all 3 APIs above are unique, but share a common prefix. This is valid and supported in the product today and as such this RFE is being closed as delivered.