Reserve/Release Support for HyperSwap

MUFG Bank, the former name was BTMU, would like to use z/OS HyperSwap among multiple SYSPLEXes.
And MUFG Bank has a shared volumes between multiple SYSPLEXes, it is a strong requirement to maintain it.

To achieve the objective, MUFG Bank need the following requests.
1) z/OS HyperSwap with H/W reserve (non GRS)
2) Data shared among multiple SYSPLEXes can be HyperSwaped.

With GDPS Proxy support, we can use GDPS HyperSwap in multiple SYSPLEXes environment. However, GDPS Proxy doesn't support to do HyperSwap for volumes shared with multiple SYSPLEXes, where the H/W reserve/release function works to keep data sharing. In addtion, MUFG Bank doesn't accept GDPS HyperSwap because they it's costly and it needs additional z/OS called K-sys to manage the HyperSwap environment. Therefore, we need to implement above two items with z/OS HyperSwap solution, not GDPS HyperSwap.

EMC is now proposing the Auto-Swap to MUFG Bank. EMC says the Auto-Swap can work in H/W reserve/release data sharing environment and keep its reserve status in swapping time. In addition, the Auto-Swap can work in multiple SYSPLEXes environment. So, unfortunately, IBM is behind EMC in this competition.

MUFG Bank is already using TPC-R to manage DS8K MGM. They don't use HyperSwap due to the above current HyperSwap restrictions. If we relieve the above two restrictions, we must get better position in this competition.