A copy export operation is initiated using the existing LIBRARY EXPORT command. However, unlike the export support that is available in the 3494 VTS, when the logical volumes are exported from the , a copy of the logical volume remains in the library. So from a host database perspective the logical volumes are still library resident. There is no automatic notification to the host (or to the tape management system) that a copy of the logical volume also exists outside the library. When logical volumes are exported from the 3494 VTS, the volumes are placed in an exported category and the host is notified. As part of this notification, the host processes each volume in the exported category. This results in the host and the tape management system updating their database to indicate that the volume now resides outside the library. The capability also exists for this support to track on which physical volume an exported logical volume now resides. Because there is no host notification with a copy export, it is up to the user to manage and track the exported physical volumes. One mechanism may be to use the existing SHELF LOCATION field in the tape configuration database (TCDB). This is a 32-byte free form field available for the users. As with the 3494 VTS support, you can use the SHELF LOCATION field to track on which physical volume the logical volume resides (using IDCAMS ALTER VOLUMEENTRY). For example, COPY EXPORT STACKED=xxxxxx could be placed in this field to differentiate from STACKED=xxxxxx which is used with the 3494 VTS support. If you use DFSMSrmm and stacked volume support is enabled, DFSMSrmm automatically handles and tracks the stacked volumes created by copy export. However, there is no way to track which logical volume copies are on the stacked volume. You should retain the updated export list file created by you and updated by the library, so that you have such a record. Refer to z/OS DFSMSrmm Implementation and Customization Guide for more information about DFSMSrmm support of copy export.