Virtual Volumes can be shared between systems, just like physical tapes. Also, just like physical tapes, if the Tape Management System (TMS) Database is not shared, tape usage is not completely documented, tape security may not be flawless, and application JCL changes may be required to mount the shared tapes.
For example, if a tape is defined only in the TMS Database on system A and written to on system B, the mount will not be documented in the Database. Since the system B Database is not controlling the usage of this tape, an unauthorized user may be able to read or write to this tape. If the TMS is setup to not allow the mounting of tapes that are not documented in the Database, a TMS override may need to be coded in the application JCL to mount the tape on system B.
If the CA Vtape Subsystems running on system A and system B are configured as Externalization and Recall Servers, the Backstore Tapes must be shared. If the TMS Database is not also shared and the TMS is setup to not allow undocumented or foreign tapes to be mounted, the Backstore Tapes will only be mountable on the system where the tapes are defined to the TMS. An override cannot be coded since CA Vtape always performs a dynamic allocation of the Backstore Tapes.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|