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
Following are descriptions of each of the messages supported by
the SuperLoader.
Abort (06h)2
Bus Device Reset
(0Ch)
2
This message is sent from the initiator to the target to clear the
current I/O process on the selected unit. The target goes directly to
the BUS FREE phase after successful receipt of this message.
Current settings of MODE SELECT parameters and reservations
are not affected. Commands, data, and status for other initiators
are not affected.
This message can be sent to a logical unit that is not currently
performing an operation for the initiator. If no unit has been
selected, the target goes to BUS FREE phase and no commands,
data, or status on the target are affected.
If a command that causes movement of the media changer has
started, the movement will complete and STATUS will not be sent
to the initiator.
The BUS DEVICE RESET message is sent from an initiator to direct
the SuperLoader to clear all I/O processes on the drive. The
message causes the SuperLoader to execute a hard reset, leaving it
as if a Bus Reset had occurred.
The SuperLoader creates a Unit Attention condition for all
initiators after accepting and processing a Bus Device Reset
message. The additional sense code is set to POWER ON, RESET,
or BUS DEVICE RESET OCCURRED.
If a command that causes movement of the media changer has
started, the movement will complete and STATUS will not be sent
to the initiator.
The COMMAND COMPLETE message is sent by the SuperLoader
to an initiator to indicate that an I/O process has completed and
that valid status has been sent to the initiator. After successfully
sending this message, the SuperLoader goes to the BUS FREE
phase by releasing the BSY signal. The SuperLoader considers the
message transmission successful when it detects the negation of
ACK for the COMMAND COMPLETE message with the ATN
signal false. If a COMMAND COMPLETE message is received by
the SuperLoader, it is handled as an illegal message: the
SuperLoader returns MESSAGE REJECT and enters its STATUS
phase, reporting CHECK CONDITION with the sense key set to
COMMAND ABORTED.
The DISCONNECT message is sent from the SuperLoader to
inform the initiator that the present connection is going to be
broken, such as the SuperLoader plans to disconnect by releasing
the BSY signal, and a later reconnect will be required to complete
the current I/O process. The message does not cause the initiator
to save the data pointer. After sending the message, the
SuperLoader goes to the BUS FREE phase by releasing the BSY
signal.
The DISCONNECT message can also be sent by the initiator to tell
the SuperLoader to suspend the current phase and disconnect
from the bus. The SuperLoader’s response to and its handling of a
DISCONNECT message are based on when, in the I/O process, the
initiator introduces the DISCONNECT message. Table 7
summarizes the SuperLoader’s response.
SELECTIONThe SuperLoader discards the DISCONNECT message and goes to BUS
FREE.
COMMANDThe SuperLoader discards the DISCONNECT message and goes to BUS
FREE. The ATTENTION request is ignored while the Command Descriptor
Block is fetched. The SuperLoader does not switch to MESSAGE OUT until
the current DMA completes.
DATAThe ATTENTION request is ignored while the current data transfer
completes; that is, the SuperLoader does not switch to MESSAGE OUT
until after the current DMA completes. The SuperLoader returns a
MESSAGE REJECT message and responds with CHECK CONDITION
status, indicating the command aborted because of an invalid message.
STATUSThe SuperLoader sends a MESSAGE REJECT message, then sends
COMMAND COMPLETE.
MESSAGE INThe SuperLoader sends a MESSAGE REJECT message and switches to the
BUS FREE phase.
The IDENTIFY message is sent by either the initiator or the
Identify (80h-FFh)2
SuperLoader to establish or re-establish the physical connection
path between an initiator and target for a particular logical unit
under the conditions listed below. Figure 2
IDENTIFY message and table 5
IdentifyThe Identify bit must be set to 1. This identifies the message as an IDENTIFY
message.
DiscPrivDisconnect Privilege. The DiscPriv can be 0, provided that no other I/O
process is currently active in the SuperLoader. If not set to 1 and other I/O
processes are currently active in the SuperLoader, the SuperLoader returns
BUSY status.
LUNTARThe Logical Unit/Target Routine (LUNTAR) field must be set to zero. The
SuperLoader does not support target routines. A LUNTAR bit of one causes
the drive to send a MESSAGE REJECT message and switch to the BUS FREE
phase.
ReservedThe Reserved bits must be zero. If a Reserved bit is non-zero, the
SuperLoader returns a MESSAGE REJECT message and switches to the BUS
FREE phase.
LUNTRNLogical Unit Number. The SuperLoader has two logical units. The tape
drive is always logical unit 0, and the media changer device is always logical
unit 1.
Ignore Wide
Residue (23h)
The IGNORE WIDE RESIDUE message is sent by the target to the
2
initiator to indicate that the number of valid bytes sent during the
last REQ/ACK handshake and REQB/ACKB handshake of a
DATA IN phase is less than the negotiated transfer width. The
Ignore field indicates the number of invalid data bytes transferred.
This message is sent immediately following that DATA IN phase
and prior to any other messages. Figure 3
format of an IGNORE WIDE RESIDUE message. Table 6
The INITIATOR DETECTED ERROR message is sent from an
2
initiator to inform the SuperLoader that an error has occurred that
does not preclude the SuperLoader from retrying the operation (a
bus parity error, for example). The source of the error may either
be related to previous activities on the SCSI bus or may be only
SuperLoader-related. When received, the SuperLoader attempts to
re-transfer the last command, data, or status bytes by using the
RESTORE POINTER message mechanism.
The SuperLoader’s response to and its handling of an INITIATOR
DETECTED ERROR message are based on when, in the I/O
process, the initiator introduces the message. Table 7
SELECTIONThe SuperLoader discards the INITIATOR DETECTED ERROR
message and then goes to the BUS FREE phase.
COMMANDThe SuperLoader discards any Command Descriptor Block bytes
fetched from the initiator, sets the Sense Key to ABORTED
COMMAND, sets the Additional Sense Code to INITIATOR
DETECTED ERROR MESSAGE RECEIVED. It sends the CHECK
CONDITION status and the COMMAND COMPLETE message and
then goes to the BUS FREE phase.
DATAThe SuperLoader discards the INITIATOR DETECTED ERROR
message and sets the Sense Key to ABORTED COMMAND, sets the
Additional Sense Code to INITIATOR DETECTED ERROR MESSAGE
RECEIVED. It sends the CHECK CONDITION status and the
COMMAND COMPLETE message and then goes to the BUS FREE
phase.
STATUSThe SuperLoader sends a RESTORE POINTERS message, returns to the
STATUS phase, resends the STATUS command, and continues the I/O
process.
MESSAGE INThe SuperLoader discards the INITIATOR DETECTED ERROR
message and sets the Sense Key to ABORTED COMMAND, sets the
Additional Sense Code to INITIATOR DETECTED ERROR MESSAGE
RECEIVED. It sends the CHECK CONDITION status and the
COMMAND COMPLETE message and then goes to the BUS FREE
phase.
Linked Command
Complete (0Ah)
This message is sent from a target to an initiator to indicate that the
2
execution of a linked command, with the FLAG bit set to zero, is
complete and that status has been sent. The initiator then sets the
pointers to the initial state for the next command.
If received by a target, this message is handled as an illegal
message; the SuperLoader enters the MESSAGE IN phase and
returns MESSAGE REJECT.
This message is sent from a target to an initiator to indicate that the
execution of a linked command, with the FLAG bit set to one, is
2
complete and that status has been sent.
This message is sent from the initiator to tell the SuperLoader that
2
the last message byte the SuperLoader passed on to the initiator
contained a parity error.
To indicate that it intends to send the message, the initiator sets the
ATN signal before it releases ACK for the REQ/ACK handshake of
the message that has the parity error. This provides an interlock so
that the target can determine which message has the parity error. If
the target receives this message under any other condition, it
proceeds directly to the BUS FREE state by releasing the BSY
signal, signifying a catastrophic error.
The target’s response to this message is to switch to the MESSAGE
IN phase and re-send from the beginning all the bytes of the
message that precipitated the MESSAGE PARITY ERROR
message.
Message Reject
(07h)
This message is sent from the initiator or target to indicate that the
2
last message received was inappropriate or has not been
implemented.
To indicate its intention to send this message, the initiator asserts
the ATN signal before it releases ACK for the REQ/ACK
handshake of the message that is to be rejected. MESSAGE REJECT
is issued in response to any message the SuperLoader considers to
be illegal or not supported. When sending to the initiator, the
SuperLoader does so before requesting any additional message
bytes.
If a target requests a message, the initiator sends a NO
OPERATION message if it does not currently have any other valid
message to send. The message is accepted when the SuperLoader
is acting as a target and may be sent when it is an initiator. If a NO
OPERATION message is received during a selection, the
SuperLoader proceeds to the COMMAND phase, provided ATN
does not continue as asserted; the NO OPERATION message is
ignored by the SuperLoader.
Restore Pointers
(03h)
Save Data Pointer
(02h)
The RESTORE POINTERS message is sent from the SuperLoader
2
to the initiator to direct the initiator to copy the most recently
saved command, data, and status pointers for the I/O process to
the corresponding current pointers. The command and status
pointers are restored to the beginning of the present command and
status areas. The data pointer is restored to the value at the
beginning of the data area in the absence of a SAVE DATA
POINTER message or to the value at the point at which the last
SAVE DATA POINTER message occurred for that logical unit.
When the RESTORE POINTERS message is received as a target,
the target switches to the MESSAGE IN phase and returns
MESSAGE REJECT.
The SAVE DATA POINTER message is sent from the SuperLoader
2
to direct the initiator to copy the current data pointer to the saved
data pointer for the current I/O process.
When functioning as a target, the SuperLoader sends this message
before a DISCONNECT message during a data transfer. It does not
send a SAVE DATA POINTER message if it intends to move
directly to STATUS phase. When received as a target, it switches to
MESSAGE IN phase and returns MESSAGE REJECT.
This extended message allows the target and initiator to agree on
the values of the parameters relevant to synchronous transfers. The
2
SuperLoader will not initiate the SYNCHRONOUS DATA
TRANSFER REQUEST message; it relies on the initiator to do so.
The SYNCHRONOUS DATA TRANSFER REQUEST message has
the format shown in figure 4
transfer negotiations with the host, but this feature is
disabled by default. To enable it, set the MODE SELECT
VU EEROM parameter EnaInitSyncNeg.
Figure 4 Synchronous
Data Transfer Request
Message
Bit
Byte76543210
0
Extended Message Identifier (01h) (see figure 1)
1
2
3
4
SYNCHRONOUS DATA TRANSFER REQUEST (01h)
Length (03h)
Transfer Period
Transfer REQ/ACK Offset
A SYNCHRONOUS DATA TRANSFER REQUEST message
exchange is initiated by a SCSI device whenever a previously
arranged transfer width agreement may have become invalid. The
agreement becomes invalid after any condition that may leave the
data transfer agreement in an indeterminate state such as:
•After a WIDE DATA TRANSFER REQUEST message
exchange.
The SYNCHRONOUS DATA TRANSFER REQUEST message
exchange establishes an agreement between two SCSI devices on
the clocking of the data used for DATA phase transfer between
them. This agreement applies to DATA IN and DATA OUT phases
only. All other information transfer phases must use asynchronous
transfers.
The SuperLoader implements both wide data transfer option and
synchronous data transfer option. Wide data transfer must be
negotiated prior to negotiating the synchronous data transfer
agreement. If a synchronous data transfer agreement is in effect,
then after accepting a WIDE DATA TRANSFER REQUEST
message, it resets the synchronous agreement to asynchronous
mode.
If the Transfer Period requested is lower than the minimum value
supported by the device, the return value will be adjusted up to
the minimum supported value. All possible transfer periods
between the minimum and maximum values are not supported. If
the Transfer Period requested is between the minimum and
maximum supported values, but not exactly achievable by the
device, the returned value will be the request value and the
SuperLoader will transmit data at the next lower speed it is
capable of. The initiator may send data at the request speed. The
maximum supported synchronous period is 5Dh (372 nsec). A
request with a Transfer Period lower than this will return a request
for asynchronous mode.
0Bh33 MHz, 30.3 nsec Transfer Period. LTO and SDLT uses 37.5 nsec period.
0Ch20 MHz, 50 nsec Transfer Period
0Dh – 5Dh(4 * Transfer Period) nsecs.
The minimum supported value for Transfer Period is 0Ah when
the bus is operating in LVD mode. When operating in HVD or
Single-Ended mode, the minimum Transfer Period value is 0Ch.
The SuperLoader SDLT 220 and SuperLoader SDLT 320 Transfer
REQ/ACK offset may be any value between 0 and 62. A value of 0
indicates asynchronous transfers. A request with a value greater
than 62 will cause the device to return a request for 62.
Wide Data Transfer
Request Extended
Message (03h)
The SuperLoader DLT1 Transfer REQ/ACK offset may be any
value between 0 and 15. A value of 0 indicates asynchronous
transfers. A request with a value greater than 15 will cause the
device to return a request for 15.
The SuperLoader LTO only supports a Transfer REQA/ACK offset
of 0. This indicates asynchronous transfers.
The following figure illustrates the message format.
A WIDE DATA TRANSFER REQUEST message exchange is
initiated by a SCSI device whenever a previously arranged transfer
width agreement may have become invalid. The agreement
becomes invalid after any condition that may leave the data
transfer agreement in an indeterminate state such as
•After a hard reset condition
•After a BUS DEVICE RESET Message
•After a power cycle.
The WIDE DATA TRANSFER REQUEST message exchange
establishes an agreement between two SCSI devices on the width
of the data path to be used for DATA phase transfer between them.
This agreement applies to DATA IN and DATA OUT phases only.
All other information transfer phases must use an 8-bit data path.
The SuperLoader implements both wide data transfer option and
synchronous data transfer option. It negotiates the wide data
transfer agreement prior to negotiating the synchronous data
transfer agreement. If a synchronous data transfer agreement is in
effect, then after accepting a WIDE DATA TRANSFER REQUEST
message, it resets the synchronous agreement to asynchronous
mode.
The transfer width is expressed as 2n where n is the transfer width
in bytes. The transfer width that is established applies to all logical
units. Valid transfer widths for the SuperLoader are 8 bits
(m = 00h) and 16 bits (m = 01h). Values of m greater than 01h are
reserved.
This chapter describes the Media Changer SCSI protocol features
implemented by the Media Changer device of the SuperLoader
system. Note that the sections included in this chapter do not fully
reiterate every ANSI SCSI option and/or command code
specification; the sections do describe the supported commands
and options.
Overview of Command and Status Processing3
The SCSI feature set has been described as “SCSI-2 plus.” This
means the SuperLoader supports:
•All of the mandatory features of SCSI-2
•Many of the optional features of SCSI-2
•Some of the mandatory and optional features of SCSI-3
Chapter 3 Media Changer Commands
Overview of Command and Status Processing
When conflicts arise between the features of SCSI-2 and SCSI-3, the
SCSI-2 methods have been chosen in all cases where execution
would differ without explicit knowledge of the host. That is, if a
command would act differently in SCSI-3 implementation without
any difference in the actual CDB, the SCSI-2 functionality is used.
If SCSI-3 defined a new functionality of a command but only with
a new field or value for a field as defined by a SCSI-3 document,
this functionality may have been implemented. Please see
individual command descriptions for the SCSI-3 features that have
been implemented.
The SuperLoader device supports the Media Changer commands
listed in table 9
The Media Changer commands are presented in alphabetical
order. Because information about a particular command may span
multiple pages, the command name is repeated, at the top of every
page that concerns that command.
Throughout this manual, multiple bytes that contain information
about specific command parameters are portrayed as shown in the
example of the Parameter List Length field (bytes 7 and 8) of the
MODE SELECT command shown as follows:
The INITIALIZE ELEMENT STATUS command allows the media
changer to check all assigned element addresses for volume and
any other status relevant to that element address. The intent of this
command is to enable the Initiator to get a quick response from a
subsequent READ ELEMENT STATUS command. It may be useful
to issue this command after a power failure, if a volume has been
changed by an operator, or if configurations have been changed.
Chapter 3 Media Changer Commands
Inquiry Command (12h)
Inquiry Command (12h)3
The INQUIRY command allows the initiator to determine the kind
of SCSI devices attached to its SCSI BUS. It causes a device that is
attached to a SCSI BUS to return information about itself. The
SuperLoader identifies itself as a media changer that implements
the SCSI-2 protocol.
The media changer can provide three categories of data in
response to an INQUIRY command: Standard Inquiry Data, Vital
Product Data, and Command Support Data. Standard Inquiry
Data contains basic data about the device. Vital Product Data
comprises several pages of additional data. Each Vital Product
Data page requires a separate INQUIRY command from the
initiator. Command Support Data indicates the fields in the CDB
that are supported by opcode. An INQUIRY command is not
affected by, nor does it clear, a Unit Attention condition.
CmdDtCommand Support Data. If CmdDt = 0 and EVPD (see below) = 0, the
media changer returns the Standard Inquiry Data. If CmdDt = 1 with
EVPD = 0, the media changer returns the Command Data specified
by Page Code/ Operation. Information about Command Support
Data is provided in figure 15
on page 43 and table 14 on page 43.
EVPDEnable Vital Product Data. If EVPD = 0 and CmdDt (see above) = 0,
the media changer returns the Standard Inquiry Data. If EVPD = 1
and CmdDt = 0, the media changer returns the Vital Product Data
Page specified by Page Code/Operation Code.
Page Code or
Operation Code
Specifies the Vital Product Data Page which is to be returned by the
media changer when EVPD is set. Specifies the SCSI Operation Code
for command support data to be returned by the media changer
when CmdDt is set. A CHECK CONDITION status is returned if this
field specifies an unsupported Page or Operation Code or if both
EVPD and CmdDt are set. Figure 11
on page 39 shows the Page
Codes for the Vital Product Pages supported by the media changer.
Allocation LengthSpecifies the number of bytes of inquiry information the media
changer is allowed to return to the initiator during the command's
DATA IN phase. Error status is not returned if the value in this field
truncates the requested information.
Standard Inquiry
Data Page
Figure 9
3
returned by the media changer.
shows the format of the Standard Inquiry Data page
TrmlOP (DLT)0Terminate I/O Process. The media changer does not support
the TERMINATE I/O PROCESS message.
NormACA (LTO)0The media changer does not support the NACA bit in the
control byte of the CDB.
HiSup (LTO)0The hierarchical addressing model is not used.
Response Data
2This Standard Inquiry Data is in SCSI-2 format.
Format
Additional Length27hThis field indicates the number of additional bytes of
INQUIRY Response Data available.
SCCS (LTO)0This device does not contain an embedded storage array
controller.
BQue (LTO)0Basic queueing is not supported.
EncServ (LTO)0This device does not contain an embedded enclosure services
component.
MultiP (LTO)0This device does not implement multi-port requirements.
MChangr (LTO)0This device is not an attached media changer.
MChnger (DLT)0Set to 1 if a Media changer (loader) is present and EEPROM
parameter EnblngMedChgr is set to 1. this SCSI-3 bit indicates
that the Read Element Status and Move Medium commands
can be issued to the drive (LON0). By default, this bit is set to
There are three different Identification Descriptors returned, in
numerical order of the Identifier Type. Each Identification
Descriptor takes the following form:
Figure 14 Identifier
Descriptor
Bit
Byte76543210
0
1
2
3
4 - n
Table 12 Identifier
Descriptor Field
Descriptions
ReservedCode Set
Reserved AssociationIdentifier Type
Reserved
Identifier Length (n-3)
Identifier
Field NameField Description
Code SetIndicates the type of data to be found in the
Identifier field. A value of 1 indicates binary data. A
value of 2 indicates ASCII data.
AssociationIndicates whether the Identifier is associated with
the logical unit or the port. Always contains a 0,
indicating the Identifier is associated with the
logical unit.
Chapter 3 Media Changer Commands
Inquiry Command (12h)
Field NameField Description
IdentifierIdentifier data, based on the Identifier Type.
The following table describes the identifiers supported by the
SuperLoader.
ValueDescription
1Concatenation of the Vendor Name,
Product ID, and unit serial number
2Canonical form of the IEEE Extended
Unique Identifier, 64 bit (EIU-64)
3FC-PH Name_Identifier
Table 13 Supported
Identifiers
Command Support
Data
Identifier
Type
1224QUANTUM UHDL, 12 ASCII space
2188 bytes of binary data indicating the
3188 bytes of binary data indicating the
Code
SetLengthIdentifier
characters (20h), followed by the unit
serial number in ASCII.
EUI-64 assigned to the drive.
64-bit, type 3, FC-PH Name_Identifer
assigned to the drive.
An application client can request command support data by
3
setting the CmdDt bit of the INQUIRY command to 1, and
specifying the SCSI operation code of the Command Descriptor
Block (CDB) for which it wants information.
The format of the command support data and definitions of the
fields follow.
Chapter 3 Media Changer Commands
Inquiry Command (12h)
Field NameDescription
100bVendor-Specific
101bThe device supports the SCSI operation code, but in a
110bVendor-Specific
111bReserved
ISO-VersionMust be 0.
ECMA-VersionMust be 0.
vendor-specific manner.
ANSI-Approved
2.
Version
CDB SizeThis field contains the number of bytes in the CDB for the Operation
Code being requested and the size of the CDB Usage Data in the data
that is returned in response to the INQUIRY.
CDB Usage DataThis field contains information about the CDB for the Operation
Code being queried. Note that the first byte of the CDB Usage Data
contains the OpCode for the operation specified. All of the other
bytes of the CDB Usage Data contain a map for bits in the CDB of the
OpCode specified.
NOTE: The bits in the map have a 1-to-1 correspondence to the CDB for the OpCode being
queried. That is, if the device senses a bit as the entire field or as part of the field of the
operation, the map in CDB Usage Data contains a 1 in the corresponding bit position. If the
device ignores a bit or declares a bit as “reserved” in the CDB for the OpCode being queried,
the map has a 0 in that corresponding bit position.
The LOAD UNLOAD command tells the target to eject all
magazines. If no magazines are present, UNLOAD returns a
CHECK CONDITION status with an ILLEGAL REQUEST sense
key.
This command will eject the magazine(s) regardless of the setting
via the PREVENT/ALLOW MEDIUM REMOVAL command.
Figure 16 Load
Unload Command
Descriptor Block
Bit
Byte76543210
0
1
2 - 4
5
Table 15 Unload
Command Descriptor
Block
Logical Unit NumberReservedImmed
UnusedReservedFlagLink
Operation Code (1Bh)
Reserved
Field NameDescription
ImmedImmediate. If this bit is set to 1, status is returned as
soon as the operation is started. If set to 0, status is
returned after the operation has completed.
PPCParameter Pointer Control. A PPC of 0 indicates that the parameter data
requested from the device starts with the parameter code specified in the
Parameter Pointer field (Bytes 5 - 6) and returns the number of bytes specified
in the Allocation Length field (Bytes 7 - 8) in ascending order of parameter
codes from the specified log page. Request for changed parameters is not
supported. This field must be 0.
SPSave Parameters. Not supported, must be set to 0. If for some reason the Save
Parameters bit is set, the command terminates with a CHECK CONDITION
status with a sense key of ILLEGAL REQUEST and an ASC of INVALID FIELD
IN CDB.
PCPage Control. This field defines the type of parameter values to be returned:
PCType of Parameter Values
00bThreshold Values
01bCumulative Values
10bDefault Threshold Values
11bDefault Cumulative Values
The Default Threshold Values are the maximum values that each parameter
can attain.
The Current Cumulative Values are the values computed since the last reset of
the device (either via power-cycle, BUS DEVICE RESET, or SCSI RESET.)
The Default Cumulative Values are the values to which each parameter is
initialized at a reset condition. Default values are zero.
By default, Current Threshold Values = Default Threshold Values.
Page CodeThe Page Code field identifies which log page is being requested by the
initiator. If the page is not supported, then the command terminates with a
CHECK CONDITION status, sense key set to ILLEGAL REQUEST, and
additional sense code of INVALID FIELD IN CDB. Supported pages are:
Chapter 3 Media Changer Commands
Log Sense Command (4Dh)
Field NameDescription
Page CodePage Definition
Parameter
Pointer
00h Supported Pages Log Page (Page 00h)
07hLast n Error Events Page (07h)
2EhTapeAlert Page (2Eh)
on page 52 (LTO only)
30hMove Statistics Page (30h)
on page 50
on page 54
31hHard/Soft Error Statistics Page (31h)
33hDevice Wellness Page (33h)
3EhDevice Status Page (3Eh)
on page 59
on page 62
on page 49
on page 56
SDLT and DLT must be 0.
For LTO only: The Parameter Pointer field allows the host to specify at which
parameter within a log page the requested data should begin. For example, if a
page supports parameters 0 through 5, and the Parameter Pointer contains 3,
then only parameters 3, 4, and 5 are returned to the initiator. Similarly, if a page
supports parameters 1, 3, and 6, and the Parameter Pointer contains 2, then
only parameters 3 and 6 are returned to the initiator.
If the Parameter Pointer is larger than the highest numbered parameter on the
page, then the target terminates the command with CHECK CONDITION
status, sense key set to ILLEGAL REQUEST, and additional sense code set to
INVALID FIELD IN CDB.
Note that parameters within a page are always returned in ascending order
according to parameter code.
If the target does not support a parameter code within this page, then it does
not return any data associated with this parameter.
Allocation
Length
This field specifies the maximum number of bytes that the initiator has
allocated for returning data. The host uses this field to limit the size of data
transfers to its own internal buffer size.
Chapter 3 Media Changer Commands
Log Sense Command (4Dh)
Last n Error Events
Page (07h)
This page returns the ASCII text for the hard error event log. This
3
page consists of a page header, a parameter header and parameter
value. The parameter value returned consists of the ASCII text for
the EEROM Hard Error Log.
Figure 19 Last n Error
Events Log Sense
Header
Bit
Byte76543210
0
1
2 - 3
ReservedPage Code (07h)
Reserved
(MSB)
Page Length (n)
(LSB)
Table 17 Last n Error
Events Log Sense
Header
Field NameDescription
Page CodeThe Page Code echoes the page code that was
specified in the LOG SENSE command descriptor
block.
Page LengthThe Page Length field specifies the total number of
bytes contained in this log page, not including the
four bytes that make up the header.
Figure 20 Format for
Last n Error Events
Log Sense
Bit
Byte76543210
(MSB)
0 -1
2
DUDSTSDETCTMCRsv’dLP
3
(MSB)
4 - n
Table 18 Parameters
Last n Error Events
Log Sense
Parameter Code
(LSB)
Parameter Length
ASCII String for Event n
(LSB)
Field NameDescription
Parameter CodeThe Parameter Code value represents the relative
time at which the error occurred. It identifies the
log parameter being transferred for that log page.
Only the most recent 10 events are reported in the
SuperLoader LTO and 5 events for the
SuperLoader DLT..
DUDisable Update. Not supported, always 0.
DSDisable Save. Not supported, always 1.
TSDTarget Save Disable. Not supported, always 1.
ETCEnable Threshold Comparison. Not supported,
always 0.
TMCThreshold Met Criteria. Not supported, always 0.
Chapter 3 Media Changer Commands
Log Sense Command (4Dh)
Field NameDescription
LPList Parameter. This bit is set to 1.
TapeAlert Page
(2Eh)
Figure 21 TapeAlert
Log Sense Header
Format
Parameter
Length
ASCII Strong for
Event n
The length in bytes of the following parameter
value.
The text includes the time of the event, the error
code indentifying the event, and additional data
specific to the event.
The TapeAlert Log page defines error and informational flags for
3
detailed device diagnostics. The TapeAlert data is event-based and
the page control bits in the LOG SENSE command are not
applicable and are ignored.
The SuperLoader LTO supports the definition of the flags for
media changer devices as defined in SMC-2.
The SuperLoader DLT only supports the reporting of the
TapeAlert Log page on logical unit 0. It supports the combined
drive and media changer flags are defined in SSC-2.
Chapter 3 Media Changer Commands
Log Sense Command (4Dh)
Bit
Byte76543210
5n + 2
5n + 3
Table 20 TapeAlert
Page Log Parameters
Value of TapeAlert Flag (Flag is set when Bit 0 = 1; Bits 1 - 7 are Reserved)
Move Statistics
Page (30h)
Parameter Length
Field NameDescription
Parameter
This field contains the Flag code.
Code
Parameter
This field is set to 1.
Length
Value of
TapeAlert Flag
If Bit 0 is set to 1, indicates that TapeAlert has
sensed a problem. If Bit 0 is 0, the Flag is not set
and no problem has been sensed.
This page consists of the Log Page Header followed by a count of
3
various movements of cartridges within the system. The entries in
the log page are cumulative throughout the life of the unit and
cannot be reset via SCSI or power cycle. Log Parameters are not
supported for this page.
Chapter 3 Media Changer Commands
Log Sense Command (4Dh)
Table 21 Move
Stati sti cs
Hard/Soft Error
Statistics Page
(31h)
Field NameDescription
Page CodeThe page code is 30h.
Page LengthThe page length is 18h bytes.
Total MovesTotal number of SuperLoader moves.
Drive LoadsNumber loads to the drive from magazines and
mail slot.
Mail Slot ImportsNumber times a cartridge was importing into the
system.
Mail Slot ExportsNumber of times a cartridge was exported from
the system.
Magazine MovesNumber of moves between storage slots.
Magazine LoadsNumber of times a cartridge was moved from a
storage slot to the drive.
This page consists of the Log Page Header followed by a count of
recovery actions performed. The entries in this log page are
3
cumulative throughout the life of the unit and cannot be reset via
SCSI or power cycle. Log Parameters are not supported for this
page. These numbers, in relation to the total number of moves
performed, can provide an indication as to the health of the servo
system.
The Device Wellness Page returns information about any check
3
conditions related to Sense Keys 4 and 9 logged by the media
changer. Up to 16 entries (parameter code 0000h to 000Fh) can be
contained in the page. Each entry records a hardware error (Sense
Key = 4) or a code update event (Sense Key = 9). Note that
parameter code 000h contains the oldest log information while
parameter 000Fh contains the most recent.
This page begins with a 4-byte header followed by the log
parameter blocks.
Figure 25 Device
Wellness Log Sense
Header
Bit
Byte76543210
0
1
ReservedPage Code (33h)
Reserved
(MSB)
2 - 3
Table 23 Device
Wellness Log Sense
Header
Page Length
(LSB)
Field NameDescription
Page CodeThe Page Code echoes the page code that was
specified in the LOG SENSE command descriptor
block.
Page LengthThe Page Length field specifies the number of bytes
available and depends on the parameters requested.
Figure 27 Log
Parameters for Device
Wellness Log Sense
Additional Sense Code Qualifier
Additional Error Information
Field NameDescription
Parameter
Code
Parameter Codes 0000h through 000Fh are supported. This provides 16 log
entries for error information capture.
DUDisable Update. Always 0.
DSDisable Save. Not supported. This bit always set to 1.
TSDTarget Save Disable. Not supported. This bit always set to 1.
ETCEnable Threshold Comparison. Threshold checking is not supported on this
page. Always set to 0.
TMCThreshold Met Criteria. Always 0.
LPList Parameter. Always set to 0.
Parameter
The number of bytes to follow (0Ch).
Length
Time StampLTO: The Time Stamp is represented as number of power cycles and total
power on hours.
SDLT/DLT: Tape motion hours when check condition occurred (note that
this is the number of power-on hours since the last time the unit was
powered on, not total number of hours during the lifetime of the drive).
The time stamp counter is updated once per hour; if the tape drive is
powered down before the hourly update occurs, the update will not occur
until a full hour after power is reapplied.
Chapter 3 Media Changer Commands
Log Sense Command (4Dh)
Field NameDescription
Media IDSDLT/DLT only: Internal media identifier being used when check condition
occurred. 0 = no media or unknown media when event occurred. Note that
this is not an applicable means of tracing media.
Source
Element/
Destination
LTO only: These fields report the element addresses that were involved in the
failure. These fields will be zero (0) if the failure did not involve a move
command.
Element
Device Status Page
(3Eh)
Figure 28 Device
Status Log Sense
Header
The Device Status Page describes the current status of the media
The MODE SELECT command (available in either 6- or 10-byte
format) enables the host to configure the media changer.
Implementing MODE SELECT and MODE SENSE requires
“handshaking” between the host and the media changer. Before
configuring the media changer, the host should issue a MODE
SENSE command to the media changer to obtain a report of the
current configuration and determine what parameters are
configurable. The host interprets this information and then may
issue MODE SELECT to set the media changer to the host’s
preferred configuration. The Mode Parameter List described in
Mode Parameter List
media changer during the command’s DATA OUT phase. The
media changer device does not allow the host to save any values
on any page.
Information for the media changer is carried on a number of pages,
each of which serves to set the media changer’s operating
parameters. The MODE SELECT pages supported, and the page
within this manual that details each, are:
PFPage Format. The Page Format bit indicates that the
data sent by the host after the MODE SELECT header
and block descriptors complies with the definition of
pages in the SCSI-2 specification. The SCSI-1 format
will not be implemented so this bit must be set to 1. It
is an ILLEGAL REQUEST to have page parameters
while the PF bit is 0.
SPSave Parameters. Must be 0. If set, this bit instructs the
SuperLoader to save all savable pages, and this is not
supported.
The following figure shows the format of the Mode Parameter List
3
that is passed by the initiator to the media changer during the
command’s DATA OUT phase.
This field specifies the length in bytes of all the block
descriptors. Since the media changer only allows one
block descriptor, the value must be either 0 or 8. A
value of 0 indicates no block description is included;
a value of 8 indicates a block descriptor is present and
precedes the mode page data. Any other value other
than 0 or 8 causes a CHECK CONDITION status with
sense key of ILLEGAL REQUEST to be returned.
Mode Parameter Block Descriptor3
The figure and table that follow provide an illustration and
description of the fields that make up the MODE SELECT
command’s Mode Parameter Block Descriptor.
This field is sent as 0. It is not applicable to media
changer devices.
Block LengthThis field is sent as 0. It is not applicable to media
changer devices.
Mode Page Descriptors3
Following the MODE SELECT command’s Mode Parameter Block
Descriptor are the MODE SELECT pages, each of which sets a
different device parameter. Each mode page has a 2-byte header
that identifies the page code and indicates the number of bytes in
that page.
Chapter 3 Media Changer Commands
Mode Sense (6) / (10) Command (1Ah/ 5Ah)
Mode Sense (6) / (10) Command (1Ah/ 5Ah)3
The MODE SENSE command allows the media changer to report
its current or changeable configuration parameters to the host. It is
a complementary command to MODE SELECT.
The command descriptor block for the 6-byte MODE SENSE (1Ah)
is shown below. An illustration of the command descriptor block
for the 10-byte MODE SENSE (5Ah) follows on the next page.
Figure 39 Mode
Sense (6) Command
Descriptor Block
Bit
Byte76543210
0
1
2
3
4
5
Logical Unit NumberRsv’dDBDReserved
PCPage Code
UnusedReservedFlagLink
Operation Code (1Ah)
Reserved
Allocation Length
The MODE SENSE (10) command returns descriptor data in a
different format than MODE SENSE (6).
Chapter 3 Media Changer Commands
Mode Sense (6) / (10) Command (1Ah/ 5Ah)
Field NameDescription
10Report Default Values
11Report Saved Values
Note that the media changer device does not support saved values.
Page CodeThis field allows the host to select any specific page or all of the pages
supported by the media changer.
Page CodeDescription
Allocation
Length
Mode Sense Data
Headers
1ChTapeAlert Page (1Ch)
1DhElement Address Assignment Page
1EhTransport Geometry Parameters Page
1FhDevice Capabilities Page
3FhReturn all pages
This field specifies the number of bytes that the host has allocated for
returned MODE SENSE data. An allocation length of zero indicates that the
media changer will return no MODE SENSE data. This is not considered an
error, and GOOD status is returned.
on page 79 (LTO only)
on page 82
on page 85
on page 86
MODE SENSE may be either MODE SENSE (6) or MODE SENSE
(10). MODE SENSE (6) data contains a 4-byte header followed by
one 8-byte block descriptor, followed by zero or more variable
length pages, depending on the Page Code and Allocation Length.
The MODE SENSE (6) and MODE SENSE (10) headers are
Chapter 3 Media Changer Commands
Mode Sense (6) / (10) Command (1Ah/ 5Ah)
Table 33 Mode
Sense Data Heade
Field NameDescription
Mode Sense
Data Length
This field specifies the length (in bytes) of the MODE
SENSE data that is available to be transferred during
the DATA IN phase. Note that the Mode Sense Data
Length does not include itself.
Mode Sense Mode
Pages
Figure 43 Mode
Sense Page
Descriptor
Block
Descriptor
Length
The following figure depicts the variable length page descriptor.
3
This field specifies the length (in bytes) of all of the
block descriptors. This value will be 0, indicating no
Block Descriptors were sent.
Bit
Byte76543210
0
1
2
PS0Page Code
Additional Page Length
Page Defined or Vendor Specific Parameter Bytes
Descriptions of the MODE SENSE page descriptor fields are
provided in the following table. Detailed descriptions of each of
the MODE SENSE Pages follow.
parameters cannot be saved (savable pages are not
supported). When set to 1, it indicates that the page
can be saved in nonvolatile memory by the media
changer.
Additional Page
Length
This field indicates the number of bytes in the page.
Note that this value does not include bytes 0 and 1.
The length is returned on MODE SENSE and must
subsequently be set to the same value when
performing MODE SELECT.
LTO only: The SuperLoader supports the TapeAlert Page that is
3
used to set/change the supported TapeAlert configuration
options. Use the MODE SENSE command to read the settings of
the TapeAlert page.
Chapter 3 Media Changer Commands
Mode Sense (6) / (10) Command (1Ah/ 5Ah)
Bit
Byte76543210
(MSB)
Interval Timer
4 - 7
(LSB)
MSB)
Report Count/Test Flag Number
8 - 11
Table 35 TapeAlert
Page Format
Descriptor
(LSB)
Field NameDescription
PSParameters Savable. Not supported, this bit must be 0.
Additional Page
Length
This field indicates the number of bytes in the page. However, this value
does not include bytes 0 and 1. The length is returned on MODE SENSE
and must subsequently be set to the same value when performing
MODE SELECT. If the page length does not match that expected by the
drive, a CHECK CONDITION status is returned, sense key set to
ILLEGAL REQUEST.
The device returns a CHECK CONDITION status with sense key set to
ILLEGAL REQUEST if it receivees an unsupported Page Code or a Page
field with values not supported or changeable. In such cases, no
parameters are changed as a result of the command.
PerfPerformance bit. Performance Impacting Exceptions are acceptable. This
bit is ignored.
DExcptDisable Information Exception Operations. If = 0, the reporting method
specified by the contents of MRIE is selected. When this bit is set to 1, all
information exception conditions are disabled regardless of the contents
for the MRIE field. To enable CHECK CONDITION mode, DExcpt
should = 0. Default setting = 1.
TestTest bit. Used to generate false TapeAlert conditions to test the response
to failure conditions. See the Report Count/Test Flag Number
description for more information. If both Test and DExcpt are set to 1, the
drive will return CHECK CONDITION status, with a send key ILLEGAL
REQUEST, and additional sense data of INVALID FIELD IN
PARAMETER LIST.
LogErrError Log. Not supported.
MRIEMethod for Reporting Information Exceptions. The tape drive uses the
contents of this field to report information about exception conditions.
ValueMet hod
00hNo reporting of Informational Exception Conditions.
The device server does not report information exception
conditions.
03hConditionally Generate Recovered Error. The device
server reports information exception conditions, if such
reports of recovered errors is allowed, by returning
CHECK CONDITION status on the next SCSI command
(except INQUIRY and REQUEST SENSE commands)
following detection of the condition. The Sense Key is
set to RECOVERED ERROR with an additional sense
code of 5D 00 (TapeAlert Event). The SCSI command
with CHECK CONDITION completes without error
prior to the report of any exception condition, and does
not need to be repeated.
04hUnconditionally Generate Recoevered Error. The drive
reports information exception conditions by returning
CHECK CONDITION status on the next SCSI command
(except INQUIRY and REQUEST SENSE commands)
following detection of the condition. The Sense Key is
set to RECOVERED ERROR with an additional sense
code of 5D 00 (TapeAlert Event). The SCSI command
with CHECK CONDITION completes without error
prior to the report of any exception condition, and does
not need to be repeated.
Chapter 3 Media Changer Commands
Mode Sense (6) / (10) Command (1Ah/ 5Ah)
Field NameDescription
06hOnly Report Informational Exception Condition on
Interval TimerNot supported.
Request. The device server preserves informational
exception data. To access the data, a poll can be taken by
issuing an unsolicited REQUEST SENSE command. The
Sense Key is set to NO SENSE with an additional sense
code of 5D 00 (TapeAlert Event).
The additional sense code of 5D 00 for values 03h, 04h,
and 06h signals that a TapeAlert event has occurred.
Information about the event is stored in the TapeAlert
Log Page. The setting of MRIE does not impact logging
of events in the TapeAlert Log Page.
Report Count/Test
Flag Number
Element Address
Assignment Page
Report Count or Test Flag Number. This field must be set to 0 unless the
Test bit is set. When the Test bit is set, this field indicates that a test
condition to be generated as follows:
ValueResult
0Change no TapeAlert Flag but report an exception
condition based on the setting of the MRIE field.
1 to 64Set the TapeAlert flag indicated in the value and
generate an exception condition based on the MRIE
field.
-1 to -64Clear the TapeAlert flag in an equivalent manner to
taking corrective action of indicated by the absolute
number of the value.
32767Set all TapeAlert flags and generate and exception
condition based on the setting of the MRIE field.
The element address assignment page is used to report element
3
address assignments to the host. This page also defines the number
of each type of element present. None of the fields in this page are
changeable.