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.
This requirement has been re-evaluated. We have no current plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server
After a discussion with Erich Hopfgarten and Tobias Leicher I want to add, that an automatic connection should be separated from other platforms.
In other words, if you have two plattforms using the same Cics Regions. the application A on platform A must be completely separated form aplication B on platform B. Only aplications on the same platforms are allowed to know each other.
I think this was not clear after my starting post.
It is assumed that the regions which comprise a Platform are interconnected in some way so that Application components deployed to different region types can successfully communicate using say DPL. It makes sense that this should be configured at the Platform level and expressed in terms of inter-region type communication as all regions within a region type are intended to be clones. That way regions can be added to a Platform or started within a region type in response to workload demand and connected without further configuration.
Attachment (Description): This should show, that when no MRO connection in a cloud Cics is needed, you can reuse a Cics Region in many Platforms very easy.