IBM TotalStorage 3494 Tape Library Operator's Manual page 397

Table 18. Operator Intervention Messages and Parameters (OPINT TRAP Type) (continued)
OPINT # Parameter [A]
132 Volser
134 Volser
135 Volser
136 Volser
137 —
138 Media
139 Pool #
140 Volser
141 Volser
142 Volser
143 —
144 Volser
145 Volser
146 Volser
147 Volser
148 —
151 —
152 Volser
153 Volser
154 Pool #
Parameter [B] Parameter [C]
—
—
—
—
—
—
—
Pool # Pool #
—
—
—
Errcode
—
—
—
—
—
—
—
—
Actual Library Manager OPINT Trap
— Stacked volume [A] could not be ejected
because the convenience I/O station is full,
or the door is open. (VTS z)
— Write-protected stacked volume [A] ejected.
(VTS z)
— A VTS unsuccessfully attempted to eject
write-protected stacked volume [A]. (VTS z)
— Stacked volume [A] moved to category FF08
due to unreadable internal label. (VTS z)
— A VTS has initialized with the Library. (VTS
z)
— * The Common Scratch Pool (Pool 00) is out
of [A] media stacked volumes. (VTS z)
— * Storage Pool [A] is out of scratch stacked
volumes. (VTS z)
Volser [A] could not be moved from Storage
Pool [B] to Storage Pool [C]. View help
panel for error code. (VTS z)
— VTS was unable to obtain construct
information for logical volume [A]. (VTS z)
— Stacked volume [A] exists in VTS database
but not in Library Manager database. (VTS
z)
— VTS has completed processing the stacked
volumes as part of Disaster Recovery
inventory. (VTS z)
— Eject failed on stacked volume [A] that
contains active data. View help panel for
error code = [B]. (VTS z)
— Unable to make stacked volume [A]
read-only. (VTS z)
— Unable to make stacked volume [A]
read-write. (VTS z)
— Stacked volume [A] is in an invalid state.
(VTS z)
— There are stacked volumes in the VTS
database that cannot be found in the library.
(VTS z)
— The time on the VTS could not be adjusted.
Call service. (VTS z)
— Active data on ejected stacked volume [A]
needs to be recovered. (VTS z)
— Stacked volume [A] is misplaced. (VTS z)
— Pool [A] has stacked volumes of wrong
(opposite) media class. (VTS z)
Chapter 6. Advanced Operating Procedures
Message
371