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.
Low priority, but I can see the use case.
Low priority change, but would like this implemented - AmEx.
We are also looking at implementing LCP. This seems like a good idea.
We are also looking at implementing LCP. This seems like a good idea (medium priority).
Does not apply to Worldpay.
we have a similar setup and this would be helpful for us
This would be good for us, but we probably won’t IPL from LCP copy very often so not a huge priority. Currently when we restore a capture we need to manually look up what volume we should be IPLing from.
Not directly applicable to our environment, so no vote, but in general we agree with the concept that LCP captures should be self-contained and include self-describing metadata like this. In a similar vein, for true immutability purposes, we feel that the expiry date of the capture should be set and stored internally at the time that it is created.
this seems to be a duplicate of I-210. Would be beneficial