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 RFE has been assessed by development as being no longer required due to enhancements for the service creation user experience delivered in the z/OS Connect EE API Toolkit for z/OS Connect EE V3.0.
IMS Service projects in the API Toolkit today include connection and interaction reference IDs, rather than actual configuration details, and these references match those definitions in the z/OS Connect EE server runtime. The runtime definitions are subject to the usual access restrictions for the zFS file system resources (server.xml in this case), and are not automatically available to the API or service developers using the tool. Hopefully this new usage pattern means that the division of roles is no longer a concern within the IMS service creation lifecycle.