T048: Drive Tapealert Flag 23 - Invalid Cleaning Tape; T049: Drive Tapealert Flag 30 - Hardware A; Cartridge; Cartridge - IBM System Storage TS3310 Setup And Operator Manual

Detection Scenarios
Root Causes
Possible CRU Replacements
Resolution

T048: Drive TapeAlert Flag 23 - Invalid Cleaning Tape

Description
Detection Scenario
Root Causes
Possible CRU Replacements
Resolution

T049: Drive TapeAlert Flag 30 - Hardware A

Description
Detection Scenario
Root Causes
10-20
TS3310 Tape Library Setup and Operator Guide
v Tape drive issues a TapeAlert 22
v Code that manages library based cleaning determines
that a cartridges is consumed based on actively
managing the use count.
Cleaning tape is used up.
v Tape Cartridge
If the cartridge is manage by a host application, export the
cartridge via the host application.
If the cartridge is managed by the library, perform the
following:
v Remove the suspect cartridge (see "Exporting a Cleaning
Cartridge" on page 7-16).
v Import a new cartridge (see "Importing a Cleaning
Cartridge" on page 7-16).
System determines that the drive has issued a TapeAlert 23
indicating that the drive was expecting a cleaning tape but
the loaded cartridge is not a cleaning tape.
Tape drive issues a TapeAlert 23 which is recognized by
the library during the continuous four second polling cycle
of drive status.
v User or library attempts to mount a cleaning tape but
the tape is not actually a cleaning tape.
v User mistakenly loads a data tape as a cleaning tape
v Inventory or application issue results in data tape being
loaded when drive expects cleaning tape
v Tape Cartridge
If the cartridge is manage by a host application, export the
cartridge via the host application.
If the cartridge is managed by the library, perform the
following:
v Remove the suspect cartridge (see "Exporting a Cleaning
Cartridge" on page 7-16).
v Import a new cartridge (see "Importing a Cleaning
Cartridge" on page 7-16).
System determines that the drive has issued a TapeAlert 30
indicating a hardware error that requires a drive power
cycle before the drive might recover to a usable state.
Tape drive issues a TapeAlert 30 which is recognized by
the library during the continuous four second polling cycle
of drive status.
Drive has determined that there is a problem per its
internal algorithms.