Table42. Status Codes and Status Text (continued)
Operation Status Resolution Actions
Status Code
1B
Status Text
Logical VolumeProcessing Error XXXX
Probable Cause
The logical volume could not be exported or
imported because an internal VTS error XXXX
was encountered. Internal or host time-out
occurrences also result in Export/Import Status
file records with this Status Code for all logical
volumes which were not successfully processed.
Call an IBM Service Representative. Error XXXX
indicates the functional area within the VTS which
detected the internal error.
Status Code
1C
Status Text
Fragment File Not Readable
Probable Cause
For Export, the logical volume could not be
exported because its fragment file in the Tape
VolumeCache could not be read.
For Import, the logical volume could not be
imported because its fragment information could
not be read from the Exported Stacked Volume.
Call an IBM Service Representative.
Status Code
1D
Status Text
Unable to Write Fragment File
Probable Cause
The logical volume could not be exported
because its fragment file could not be written to
the Exported Stacked Volume.
Call an IBM Service Representative.
Status Code
X'1E'
Status Text
Invalid Logical Volume,record NNNNN
Probable Cause
The Volserof the logical volume is not six
characters or contains characters which are not
valid.
1. Examine the first thirteen bytes of the status record.
They contain the input from the list file decimal record
number NNNNN as read.
2. Correct the input record and retry the operation.
322 Magstar 3494 TapeLibrary Operator Guide
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|