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 was not the issue which was mentioned in this RFE. I used the CICS Connection name in the service as an example. I did not intend to suggest that this was a requirement.
The main issue is that if you have within one z/OS connect environment two CICS connections , then you need to create two different services , since service and cics connection aere 1-1 related.
Within the JSON request there is also this service name , so if you are testing the same request to 2 cics environments within one z/OS connect environment the JSON request will look different suing service1 then with service 2.
That is the issue I was addressing in this RFE
This requirement is addressed by z/OS Connect Enterprise Edition V3 (all versions)
There is no requirement for the name fo the service to contain the name of the CICS connection. You can use the CICS service project in the z/OS Connect EE API Toolkit to create services for which you can edit the root element name. You can use the same connection reference name for different CICS regions in different z/OS Connect EE servers, you can then use the same service across multiple z/OS Connect EE/CICS server pairs so there is no need to create multiple services.
For further details about creating CICS Services using the API Toolkit, refer to the “Creating a service” topic in the z/OS Connect EE V3.0 Knowledge Center:
https://www.ibm.com/support/knowledgecenter/SS4SVW_3.0.0/designing/service_create_edit.html
For further details about moving services between services without chaining the connection reference, refer to the “How to move services between environments for DevOps” topic in the z/OS Connect EE V3.0 Knowledge Center:
https://www.ibm.com/support/knowledgecenter/SS4SVW_3.0.0/designing/changing_connection.html