HyperSwap session is in an unexpected state after running a Recover command

Edit online

This condition occurs when you run a Recover command on a HyperSwap® session in which the standby management server is an open system or on a different sysplex.

Problem

After you run the Recover command on a HyperSwap session, the session might change to the Prepared state instead of the expected target available state. However, this condition might not occur at all, when a valid Host IP connection exists to an active remote z/OS System.

Action

To use the Start H1>H2>H3 command on a HyperSwap session, complete the following steps:
  1. Issue a Start H1>H2>H3 command. Verify that the HyperSwap session reaches a Prepared state.
  2. Add the standby management server. The standby management server can be an open system or a system that is on a different z/OS® sysplex.
  3. Issue a takeover from the standby management server.

    Verify that the HyperSwap session has errors that indicate that it cannot communicate with the standby management server because it cannot communicate to IOS. Because the HyperSwap configuration was not be purged, it is possible for a HyperSwap to still occur on the new active open server.

  4. Shut down the previously active z/OS server.
  5. Cause a HyperSwap event to occur.

    Verify that the copy sets are in the Suspended state.

  6. On the new active open server, disable HyperSwap by clearing the Manage H1-H2 with HyperSwap property in the View/Modify Properties notebook.

    Verify that the HyperSwap session now has the Recover command available.

  7. Verify that the hardware and Copy Services Manager are matched and in a Prepared state.