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.
n/A not using CC
n/A not using CC
low - a 'planned unplanned' will achieve most of this requirement. A planned HS will fail if there are any active CC, as it should
We also would like this...
We'd like this............
Medium
Medium priority. Right now we manage things through TWS, but it's safer to handle it via GDPS since GDPS is better fit to request the status of the background copy inside the box.
Would be useful to us. Medium Priority.
Could potentially be very useful. high priority.
medium
FI is also affected by this uncomfortable CC handling for planned HS.
However:
We are wondering what "Quiesce HS, Abort HS" means. Is "Quiesce CC, Abort CC" meant? What does each such action imply? We would not want to wait from script start until all CC-jobs have ended before the PHS can be performed. A GDPS option to "quiesce CC" about 1-2 hours before script start could maybe be interesting.
Currently we solve this problem by having all CC-jobs connected to a certain "TWS Special Resource" for this purpose. By stopping this TWS Special Resource 1-2 hours before a PHS no new CC-job is started and all running CC-jobs have a chance to end smoothly.
N/A - We are satisfied with the current CC handling with GDPS/PPRC
Would be useful for us - high priority
This is a very helpful functions and make planned HS much easier. High priority.
Very helpful for our planned HS's.
good idea - CC "failures" are a little hard to explain to the production users, especially if there are many and the benefits are good enough that we shouldn't simply disallow them because we HS occasionally
GREAT IDEA!!!
I would like to expand on this request. Before executing a HS have a HS CC Checker. This should list the amount of CC running and the Job name with the LPAR.
If you decide to execute the HS, put a reserve so no other CC could run.
Swiss Re / PPRC
This would make life easier during our operations, too.