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.
n/a
Useful for forensic recovery. Isn't something like this already in the pipeline with IzBR ? Either way, if restoring individual volumes, we'd have to ensure that they could only be varied online to an existing system for analysis and not inadvertently become part of a now-inconsistent recovery copy that we'd try to IPL from. Addressability of all these copies may also be a challenge.
It could be useful, if it work well with catalogs
N/A for LBG.
n/a
how would this work with catalogs and mixed SMS pools?
Nice to have, but it depends on the storage (sms) setup if it is useful or not.
For example what about consistency against data on other not restored volumes (multi-volume, catalogs, log files, overflow pool). It can be usefull for foreign systems.
I agree with this need. we retain LCP captures even if some volumes may be missing due to capacity issues because we believe that "half a loaf is better than no bread". In other words, a surgical recovery is probably a more likely scenario that a full DASD loss. This should be a med to high priority for LCP
I guess I do not see the benefit unless you have separate consistency groups. How will you know what volumes, if it is a multivolume dataset, and then the catalog restore to match? just recover everything into the "clean-room", and then selectively restore back into production what you would want.
Does this not mean you actually have different consistency groups?
Interested to prioritize
This sounds a very interesting idea. This will save time and space during a crisis
interested to prioritize
This would provide a useful hal-way house between all-or-nothing and true surgical recovery, and I can think of use cases too.....
would be interested to prioritize this idea, that enables more surgical recovery, instead of 'all or none'