Setting up the environment for HyperSwap
You must set up an environment in which you can run HyperSwap® processing before you can enable HyperSwap for a Copy Services Manager session.
Before you begin
To enable HyperSwap processing on IBM z/OS® systems, the following conditions must exist:
- The HSIB and IOSHSAPI address spaces are started on the z/OS system to which the storage systems are connected.
- All reserve volumes are converted to global enqueues (ENQs).
- The storage system volumes are count key data (CKD) volumes that are attached to a z/OS system. The volumes can be attached to the same z/OS system or different systems.
- If the storage system volumes are not connected to a z/OS system on which Copy Services Manager is installed, the required Resource Access Control Facility (RACF®) settings are set on the z/OS system and the SOCKPORT parameter is defined for the HyperSwap management address space IOSHMCTL. This set up enables Copy Services Manager to connect to the z/OS system by using an IP connection. For the required RACF settings, see the IBM® Copy Services Manager Installation and Configuration Guide.
To enable HyperSwap
processing on FlashSystem/IBM Spectrum Accelerate systems, the
following conditions must exist:
- When adding copy sets to a FlashSystem/IBM Spectrum Accelerate session that will support HyperSwap, the source and target volumes in the copy set MUST have the same name. FlashSystem/IBM Spectrum Accelerate requires that the source and target have the same name.
- Before a FlashSystem/IBM Spectrum Accelerate session can be enabled for HyperSwap, a Quorum Witness must be defined on the storage system. See the following Redbooks publication (http://www.redbooks.ibm.com/abstracts/redp5434.html) for more information. Also see the Quorum Witness section in the IBM online documentation at https://www.ibm.com/support/knowledgecenter/en/STJKMM_12.3.2/cli_12.3.2.x/r_command__mirroring__quorum_witness_define.html.