VTV Transfer Fails Due To Selection Of An Inappropriate ACS
(Doc ID 1588777.1)
Last updated on FEBRUARY 07, 2019
Applies to:
Sun StorageTek Virtual Tape Control Software (VTCS) - Version 7.0 to 7.2 [Release 7.0]Sun StorageTek Enterprise Library Software (ELS) - Version 7.0 to 7.2 [Release 7.0]
IBM z/OS on System z
Multiple ACS configuration.
Affected VTSSs have RTDs of the same device type in both / all ACSs
Multiple storage classes specified; for example:
MGMT NAME(M) MIGPOL(S0,S1)
STOR NAME(S0) ACS(00)
STOR NAME(S1) ACS(01)
Symptoms
SLS6696I Transfer VTV vvvvvv from VTSS nnnnnnn1 to nnnnnnn2 via ACS aa (where ACS aa is disconnected or unavailable)
VTV transfer does not select an available, connected ACS.
Scenario:
A mount was issued for VTV v1 in VTSS s2. As VTV v1 was resident in VTSS s1 and no migrated copies existed, a VTV transfer was initiated.
Each of VTSS s1 and VTSS s2 were connected to RTDs in ACS 00 and ACS 01. The two VTSSs had RTD device types in common in both ACSs, but all RTDs in ACS 00 were offline.
VTCS incorrectly attempted to transfer VTV v1 using ACS 00 because it did not check the online/offline status of RTDs, only their connectivity. The transfer failed.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |