Filter
Top Products
Table 42. Status Codes and Status Text (continued)
Operation Status Resolution Actions
Status Code
17
Status Text
Logical volume Copy failure
Probable Cause
During an export operation, the logical volume
could not be exported because a permanent
error was encountered when copying the volume
from the source stacked volume to the Exported
Stacked Volume. During an import operation, the
logical volume could not be imported because a
permanent error was encountered when copying
the volume from the source Exported Stacked
Volume to a stacked volume.
Suspected media failure, call an IBM Service
Representative.
Status Code
18
Status Text
No Data Associated With Logical Volume
Probable Cause
The logical volume could not be exported
because there is no data associated with the
volume on a stacked volume in the VTS
subsystem. The most likely reason is that the
logical volume has never been used in the VTS
prior to it being specified for export.
Check the logical volume’s record in the tape
management system to determine if the volume contains
active data or not. If it does not, use the logical volume
deletion function to remove the volume from the library. If
it does show that the volume contains active data, call for
service.
Status Code
19
Status Text
Logical Volume Copy/Fragment Failure
Probable Cause
The logical volume could not be exported
because it is currently resident in the Tape
Volume Cache and attempts to copy it to a
stacked volume and create its Fragment failed.
Call an IBM Service Representative.
Status Code
1A
Status Text
Logical Volume TVC State Unknown
Probable Cause
The logical volume could not be exported
because its state in the Tape Volume Cache
could not be determined.
Call an IBM Service Representative.
Appendix B. Virtual Tape Server Import/Export Advanced Function 321
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|