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.
Thank you for submitting this RFE.CICS CM development have given it considerable attention but are not able to address this at this time. Please see technical reasons for declining this RFE.
The current export/import method suffers shortcomings:
• Customers must implement exit programs and FTP JCL to do the cross LPAR movement – although samples aid this activity.
• The export/import is not immediate – it is subject to time delays.
• Feedback on outcomes processing on the remote (import) system may be poor,
either requiring users to connect to remote Servers for monitoring purposes, or implement more exits for return message (email?) sending.
However, the solution requires major product redesign and enhancement.
• CICS CM would require Server-to-Server intercommunications
• Respository records may require ServerName/LPAR image stamping to provide uniqueness
• Rules on synchronization, master/slave relationships, startup/shutdown/fallover/whatever need to be considered, coded and implemented
Really, to do this properly is a major, major undertaking.