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.
Not a requirement for HSBC
Not a requirement for JPMC
Not a requirement for FI
Useful but low priority for LBG.
Would be useful also for us.
We have a 2-step processes to backup the Ksystem simplex disc:
1st Job - FlashCopy our Ksystem simplex disc (all of them) to separate UCBs using DFSMSdss FULL FASTREP(REQUIRED) FCNOCOPY DUMPCONDITIONING, using a job within the Ksystem itself.
2nd Job - DFSMSdss DUMP FCWITHDRAW each FC-device to tape on a production system.
The jobs are coordinated using our job scheduler. The FC devices are set online in the system that needs them, then offline when finished.
A solution to avoid this home-grown procedure would be welcome, but we are setup for recovery of the Ksystems anyway, we hope :-).
Low priority as we have developed a process. It could be better.
We would also like standard option(s) for backing up our controlling systems.
Not a requirement for us
Actually, this is something IBM should have done versions ago.
Here the original content from the RFE. Looks like the IBM conversion failed for old RFE 153950......
If a critical situation occurs and our volumes used for a Controlling LPAR are cleared we must recover the entire LPAR somehow......
Use case:The way you handle mirroring and backup of controlling LPARs is fully based on homegrown coding and procedures. The GDPS product as such haven't any support for mirroring of the controlling lpars nor support for backing up the volumes. If at least GDPS could support mirroring as well as break of mirroring base on standard scripts we could use the restAPI for handling mirror/break mirror etc and then we just needed a potential BU to tape for the volumes. I guess most installations have to do such activities themselves or maybe the don't take backups but rely on that they have two controlling........
Business justification:We ask for a standardized solution. We need to control mirroring/break of mirror via standard scripts in a manner where we can do proper backups of our controlling LPARs according to the single installations own requirements. To ensure proper backups of our "Island Lpars". We prefer it handled via standard licenses and not based on SafeGuarded Copy handlings.