Ability to manually disable protective mechanisms like QHA

This is to request manual ability to disable various protective mechanisms in GDPS, for example automatic QHA on GDPS/PPRC resynch/failback.

We recently had an issue PMH 13736 BR 122 where pathgroups were left online to an LPAR that was already down, and we could not resynch PPRC because GDPS/PPRC automatically does QHA before it allows a START SECONDARY.

QHA works great otherwise so it took us only a few minutes to determine this was not a real risk to us and that DEVSERV agreed with GDPS and the pathgroups should not be there - but we couldn't do anything about it because there was no documented way to disable that automatic QHA.

We had to escalate on the software side and were very lucky to get a GDPS teammember as quickly as we did (only a few hours) to help resolve the situation via undocumented commands to disable QHA, but still had PPRC down several hours longer than necessary without Hyperswap protection following a rare site swap in Production.

Another example of a protective mechanism that IBM introduced is Flashcopy locking with GDPS/XRC. We dont' use it, nor will we after testing it. Luckily for us, it can be disabled in GEOXPARM. We believe any new function put in to "protect a customer from themselves" should be implemented with this same philosophy, or at least have a documented way to disable it so we don't need a Sev 1 PMR and longer outage to account for situations where there is a software or DASD microcode bug.