Using outboard policy management support, you can also specify whether a Peer-to-Peer VTS makes a copy of the logical volume in each distributed library. On a volume-by-volume basis, you can indicate which distributed VTS library is to be used as the I/O VTS and whether the data written is to be copied to the other VTS. Use the library manager management class policy to specify which distributed VTS library should be the I/O VTS and to specify the "no copy" option.