MGM resiliency in recovery region

With MzGM 4-SITE we had resiliency in our recovery region for disk.  For example, if C disk (XRC secondaries) died, GDPS/Metro in that region could Hyperswap to D disk and XRC would remain up, capable both of building DR and of doing our daily required Flashcopies into our HA environment.

We have converted to MGM now and it is lacking in resiliency for the recovery region.   If the C disk dies, not only is there no automatic Hyperswap to D disk, but in order to re-establish DR capability we either have to wait on IBM to repair the C subsystem (which can take days), or we have to create an entirely new GM config that points to D disk and manually figure out a way to clean things up and establish GM to the D disk.     Once C were repaired, we would have to manually load the original config and figure out a way to get things back (easier said than done when MGM procedures are relatively opaque when compared to MzGM scripts).

We'd like to see IBM pursue two things - first, GDPS MGM 4-SITE should really be 4-SITE, i.e. GDPS should be able to manage a cleanup and establish (fullcopy) of GM from A or B disk to D disk if C disk dies (high priority).    The second thing involves enhancements to disk microcode - make the Global Copy relationship in the recovery region a Metro Mirror relationship capable of Hyperswap if necessary and eliminate the need for a potential fullcopy of GM (medium/high priority).