Pair management server
return to main contents page
HDvM Agent
HDvM Agent 6.0 or later.
In some versions of HDvM Agent, the functions available for HRpM may be restricted, so it is recommended to apply the same version as that of HRpM.
For the system requirements of HDvM Agent, see the following file.
Application_server
Note:
If the version of HDvM Agent used with HRpM is 6.4.0 or later, we strongly recommend that the version of CCI running on the same host as the agent be 01-17-03/05 or later for Windows or 01-21-03/05 for Linux.
If an earlier version of CCI is used, an error will occur that requires a property file setting described below.
When a host running HDvM Agent and CCI is restarted, device information is updated. 
This update can render the configuration definition file used to identify command devices obsolete (because values referring to pre-update device information remain unchanged). 
This might make it impossible to gather pair, pool and journal information from HRpM.
To prevent this error, specify the following HDvM Agent property in�@the server.properties file:
server.agent.rm.optimization.userHorcmFile=true
Note: If you want to link with a Device Manager agent running on a guest OS of VMware ESXi 5.x, use a Device Manager server and agent of version 7.2 or later.
CCI
For the system requirements of CCI, see relevant CCI manual or release notes.
BCM / Mainframe Agent
OS Case Product Name Product Version
OS/390 When replication environment of the mainframe is monitoring BCM (*1) 5.0 - 7.3
Mainframe Agent 6.0 - 7.1
z/OS When replication environment of the mainframe is monitoring BCM (*1) 5.0 or later
Mainframe Agent 6.0 or later
Legend:
(*1) BCM  cannot be used if Core License is registered in Device Manager - Server.
For the system requirements of BCM and Mainframe Agent.
Mainframe Server