Previous Topic: CA Vtape P2P OptionNext Topic: How P2P Works


Overview and Requirements

The CA Vtape P2P Option is an optional component which requires a separately licensed LMP key. CA Vtape P2P uses TCP/IP to provide real time remote duplexing of Virtual Volumes.

Virtual Volumes can be shared by multiple SVTS subsystems in a SVTS complex environment without CA Vtape P2P. A SVTS complex is comprised of several SVTS subsystems accessing a common set of control files and Virtual Volumes through the use of shared DASD across one or more LPARs. This configuration also works well when all of the subsystems are running in a common physical location.

CA Vtape P2P allows separate SVTS complexes with single or multiple SVTS subsystems to communicate and share a common subset of Virtual Volumes using TCP/IP. These systems do not need to share DASD or a common set of control files. Additionally these SVTS subsystems may be in physically diverse locations.

CA Vtape P2P requires an active TCP/IP stack running on your zOS/390 system. If necessary, refer to IBM's zOS/390 documentation regarding how to install or setup TCP/IP on your system.

CA Vtape P2P is only supported for Virtual Volumes created by a CA Vtape Subsystem running with CacheManagement=Dynamic.