Quantum ATL SuperLoader DLT and ATL SuperLoader LTO Software Interface Guide, 81-60220-01 A02,
March 2003. Made in USA.
Quantum Corporation provides this publication “as is” without warranty of any kind, either express or
implied, including but not limited to the implied warranties of merchantability or fitness for a particular
purpose. Quantum Corporation may revise this publication from time to time without notice.
Your right to copy this manual is limited by copyright law. Making copies or adaptations without prior
written authorization of Quantum Corporation is prohibited by law and constitutes a punishable violation of
the law.
TRADEMARK STATEMENT
DLTtape, Super DLTtape, the Super DLTtape logo, and SuperLoader are trademarks, and Quantum and the
Quantum logo are registered trademarks, of Quantum Corporation.
Other trademarks are the property of their respective owners.
This section outlines the scope and contents of the Quantum ATL
SuperLoader™ Software Interface Guide. It contains information
about the intended audience, purpose, organization, and
document conventions.
Intended Audience0
This interface guide is a written for the following audiences:
•Original Equipment Manufacturers (OEMs) that integrate the
Quantum ATL SuperLoader into a system or subsystem
•System integrators that are responsible for the SCSI interface
•End users that operate and troubleshoot the SuperLoader
This interface guide describes the procedures and issues involved
in the development of software applications and utilities to
communicate with the Quantum ATL SuperLoader.
•SCSI interfaces
•SCSI Messages
•Media Changer Commands
Organization0
This reference manual is organized as follows:
•Chapter 1, Theory of Operation
the SuperLoader models, media changer elements, events, and
automatic drive cleaning.
•Chapter 2, Messages
the SuperLoader.
•Chapter 3, Media Changer Commands
protocol features implemented in the media changer.
The SuperLoader products are an integration of two separate
devices, a tape drive and a media changer. The media changer
consists of all the mechanics and electronics required to store and
move tape cartridges while the tape drive provides the read/write
functionality.
Each device has a separate interface for communication to the host.
The SCSI command set supported by the tape drive is documented
separately. The SCSI command set supported by the media
changer device is detailed in xxx.
The SuperLoader is fully compliant with the ANSI SCSI-2 standard
for tape drive and media changer devices and implements many
optional features.
The SuperLoader does not act as an initiator on the SCSI bus.
Therefore, it does not generate unsolicited interrupts to the bus,
initiate its own SCSI commands, or assert bus reset.
Quantum ATL SuperLoader Software Interface Guide1
Chapter 1 Theory of Operation
SuperLoader DLT
SuperLoader DLT1
The SuperLoader DLT family of products utilize a single SCSI ID
and two logical units. The tape drive always resides at logical unit
0 and the media changer resides at logical unit 1. The SuperLoader
supports narrow and wide, synchronous and asynchronous data
transfers. Both LVD and single-ended versions are available.
SuperLoader LTO1
The SuperLoader LTO family of products utilize two separate SCSI
IDs. The tape drive and media changer each reside on a unique ID.
The media changer device supports narrow and wide,
asynchronous data transfers only. The tape drive device supports
narrow and wide, synchronous and asynchronous data transfers.
Medium Changer Elements1
The medium changer command set accesses the address space for
the set of physical locations and mechanisms with the
SuperLoader. This guide uses the SCSI-2 term element to refer to
one member of the SuperLoader address space. Each element is a
discrete physical entity that can hold a single tape cartridge. Each
element within a SuperLoader is represented by a unique 16-bit
element address. The SuperLoader consists of the following
medium changer elements.
•Medium transport element
•Storage elements
•Data transfer elements
2Quantum ATL SuperLoader Software Interface Guide
Chapter 1 Theory of Operation
Events
You can issue the Mode Sense command to determine the
SuperLoader configuration. You can also use this command to
determine the first address and the number of elements of each
type.
Although the SuperLoader does have a mailslot, it is not reported
as an Import/Export element for use by the host system. It is
strictly to allow users to access tape cartridges using the front
panel or On-board Remote Management tool.
Medium Transport
Element
Data Transfer
Element
Storage Elements1
This mechanism can hold a single cartridge and is considered a
1
single medium transport element. It is used to move media
between elements within the SuperLoader.
The SuperLoader is configured with a single tape drive.
1
All of the storage elements within the SuperLoader are contained
within removable magazines. There are two magazines which hold
eight tape cartridges each, for a total of 16 storage elements. Since
the magazines are removable, a user may insert or remove a
magazine at any time. Because of this, the SuperLoader always
reports 16 storage elements, regardless of how many magazines
are currently installed. When a magazine is removed, the
corresponding storage elements are reported as inaccessible. This
is done via the Read Element Status–Storage Element Descriptor
on page 134–byte 2, bit 3.
Events1
Events are system conditions created y operator actions or system
failures. These events are recorded in sense data for the SCSI host
to retrieve via the Request Sense command.
Quantum ATL SuperLoader Software Interface Guide3
Chapter 1 Theory of Operation
Events
Power Cycle1
SuperLoader
Offline
When the SuperLoader is powered-on, it goes through an
initialization sequence, during which it:
•Resets and initializes all hardware
•Responds to SCSI commands which do not require movement
•Responds to Test Unit Read and all movement type comands
with a not ready, initialization in progress check condition
(SK=02 ASC=29 ASCQ=02).
When the power on initialization is complete, it:
•Generates a Power On/Reset Occurred event (SK=6 ASC=29
ASCQ=02)
•If initialization is sucessful, it generates a note ready to ready
transition (SK=6 ASC=28 ASCQ=00), otherwise, failure sense
data is set accordingly.
When a user accesses the SuperLoader via the front panel or On-
1
board Remote Management in such a way that would cause
conflict with a SCSI command, the SuperLoader is put into an
offline state. If a SCSI command is received while in this offline
state, a not ready check condition is reported (SK=01 ASC=04
ASCQ=07).
Magazine
Insertion/
Removal
The SuperLoader must be powered-on with at least one magazine,
otherwise a check condition is reported (SK=-2 ASC=04
1
ASCQ=03).
While the system is online, the user may remove a magazine blank
and replace it with a magazine. The SuperLoader will calibrate the
newly installed magazine and check the presence of tape
cartridges in each of the storage elements. While this inventory is
in progress, the SuperLoader LTO will report a not ready check
condition (SK=02 ASC=04 ASCQ=01). The SuperLoader DLT does
not provide any indication that the operation is in progress. Once
the inventory is complete, all SuperLoaders report a unit attention
(SK=06 ASC=3B ASCQ=13).
4Quantum ATL SuperLoader Software Interface Guide
Chapter 1 Theory of Operation
Automatic Drive Cleaning
Similarly, while a magazine is in the process of being removed, a
not ready check condition is reported (SK=02 ASC=04 ASCQ=07).
Once the operation is complete, by replacing the magazine with a
blank, a unit attention is reported (SK=06 ASC=3B ASCQ=12).
While one or both of the magazine bays are open, a not ready
check condition is reported (SK=02 ASC=04 ASCQ=03).
Maximum
Temperature
Exceeded
The SuperLoader monitors the ambient temperature within the
system. If the temperature exceeds the maximum safe temperature
1
for the media, the SuperLoader will disable all movement until the
temperature decreases below a safe threshold. While the
temperature remains excessive, SCSI commands that require
movement will fail (SK=04 ASC=0B ASCQ=01).
Automatic Drive Cleaning1
There are two modes of automatic drive cleaning support
available:
•Host-initiated cleaning
•SuperLoader managed cleaning
Both modes provide automatic cleaning of the drive, but the first is
managed by the host and the second is managed by the
SuperLoader. These two modes are configured separately, and
only one should be enabled at any given time.
When automatic drive cleaning of the drive is enabled, either the
host of the SuperLoader is responsible for all cleaning functions
such as:
•Detecting when a drive requires cleaning
•Tracking and selecting cleaning cartridges
•Moving a cleaning cartridge to the drive
Quantum ATL SuperLoader Software Interface Guide5
Chapter 1 Theory of Operation
Automatic Drive Cleaning
•Determining when a cleaning cartridge has used all of its
By default, the SuperLoader is configured to allow for hostinitiated cleaning. If automatic cleaning is disabled from the host,
the SuperLoader can be configured to manage the automatic
cleaning of the drive. This is done by enabling the “Auto Clean”
function. Please refer to the Quantum ATL SuperLoader Automated Tape Library User Manual for information on how this is done.
Note:There is no way for the host and SuperLoader to know
In host-initiated cleaning mode, the host tracks all cleaning
cartridges and their use. When the SuperLoader Auto Clean
feature is enabled, a “cleaning slot” is allocated and the cleaning
cartridge is stored in this storage element. The SuperLoader
assumes that any cartridge stored in this location is a cleaning
cartridge and will attempt to use it as such.
available cleaning cycles
how the other is configured with respect to automatic
drive cleaning. It is up to the user to make sure only one
is enabled.
The SuperLoader does not keep track of the number of times a
cleaning tape is used. Instead, it relies on the tape drive to report
when the tape has expired. When this happens, the superLoader
will notify the user via the front panel. The Auto Clean function is
automatically disabled until the user inserts a new cleaning tape
and re-enables the feature.
Element Status
Information
When the SuperLoader Auto Clean feature is enabled, the
1
allocated storage element is reported as inaccessible to the host.
This is done by setting the access bit to 0 in the Read Element
Status Storage Element Descriptor page.
Automatic
Cleaning
Operation
when the SuperLoader Auto Clean feature is enabled, the
SuperLoader checks if the drive needs cleaning after each
1
successful move from the drive. Therefore, each time the drive is
unloaded, it is checked.
6Quantum ATL SuperLoader Software Interface Guide
Chapter 1 Theory of Operation
Automatic Drive Cleaning
The movement of the cleaning tape is handled differently
depending on the SuperLoader model.
SuperLoader DLT1
If the move command, that unloaded the drive, was initiated from
SCSI, the cleaning tape is moved from its storage slot, to the drive,
the cleaning is performed and the cleaning tpae is returned to its
storage slot, before command complete status is returned to the
SCSI host. If an unrecoverable error occrus when moving a
cleaning cartridge that prevents a subsequent host initiated
command from completing, a check condition will be set in the
returned status byte and sense data is set appropriately.
SuperLoader LTO1
If the move command that unloaded the drive was initiated from
SCSI, command complete is returned to the host when the move
completes. The cleaning tape is then moved from its storage slot to
the drive. The cleaning is performed and once complete, the
cleaning tape is returned to its stoage location. If a SCSI command
is received during this cleaning process, a not ready check
condition is reported (SK=-2 ASC=30 ASCQ=03).
Quantum ATL SuperLoader Software Interface Guide7
Chapter 1 Theory of Operation
Automatic Drive Cleaning
8Quantum ATL SuperLoader Software Interface Guide
Chapter 2
2Messages
The SCSI message system allows communication between an
initiator and the SuperLoader for interface management and
command qualification. Messages can be originated by either the
initiator or the SuperLoader. This section contains a detailed
description of the messages supported by the SuperLoader.
Message Format2
A message can be one or more bytes in length. One or more
messages can be sent during a single MESSAGE phase, but a
message cannot be split over MESSAGE phases. The initiator is
required to end the MESSAGE OUT phase (by negating ATN)
when it sends certain messages that are identified in table 1
When a connection to the SuperLoader is established, for example
the SuperLoader is selected with ATN asserted, the first message
byte passed by the initiator must be either an IDENTIFY, ABORT,
or BUS DEVICE RESET message. If not, the SuperLoader discards
the message, saves no status information, and goes to the BUS
FREE phase.
Quantum ATL SuperLoader Software Interface Guide9
.
Chapter 2 Messages
Message Format
If an initiator supplies an unsupported message, for example,
COMMAND COMPLETE or a reserved or undefined message
code, the SuperLoader returns a MESSAGE REJECT message and
continues where it left off, possibly returning to MESSAGE OUT if
ATN is raised.
Table 1 Message
Format
The first byte of the message, as defined in table 1
, determines the
format of the message.
Message CodeMessage
00hOne-byte message (COMMAND COMPLETE)
01hExtended message
02h – 1FhOne-byte message
20h – 2FhTwo-byte message
40h – 7FhReserved
80h – FFhOne-byte message (IDENTIFY)
The SuperLoader supports the messages listed in table 2. The
message code and the direction of the message flow is also
included in the table (In = target to initiator, Out = initiator to
target).
EXTENDED MESSAGE
(Synchronous Data and Wide
Data Transfer Requests)
IDENTIFY80h – FFhInOut
IGNORE WIDE RESIDUE 23hIn
INITIATOR DETECTED
ERROR
LINKED COMMAND
COMPLETE
LINKED COMMAND
COMPLETE (with flag)
MESSAGE PARITY ERROR09hOut
MESSAGE REJECT07hInOut
NO OPERATION08hOut
RESTORE POINTERS03hIn
SAVE DATA POINTER02hIn
*
01hInOut
05hOut
0AhIn
0BhIn
*
Extended message (figure 1).
Two-byte messages consist of two consecutive bytes. The value of
the first byte, as defined in table 1
, determines which message is to
be transmitted. The second byte is a parameter byte that is used as
defined in the message description.
A value of 1 in the first byte indicates the beginning of a multiplebyte extended message. The minimum number of bytes sent for an
extended message is three. The extended message format is shown
in figure 1
This field specifies the length, in bytes, of the Extended Message
Code plus the Extended Message Arguments that follow.
Therefore, the total length of the message is equal to the Extended
Message Length plus 2.
A value of 0 for the Extended Message Length indicates that 256
bytes follow.
Extended Message (01h)
Extended Message Length
Extended Message Code
Extended Message Arguments
Extended Message CodeThe SuperLoader supports the following Extended Messages:
01h SYNCHRONOUS DATA TRANSFER REQUEST
03h WIDE DATA TRANSFER REQUEST