SDLT 600 Fibre Channel Interface Guide, 81-81200-02 A01, December 2007, 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.
COPYRIGHT STATEMENT
Copyright 2007 by Quantum Corporation. All rights reserved.
Your right to copy this document 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
Quantum, DLT, DLTtape, the Quantum logo, and DLTtape logo are all registered trademarks of Quantum Corporation. SDLT and Super
DLTtape are trademarks of Quantum Corporation.
Other trademarks may be mentioned herein which belong to other companies.
This reference guide is a comprehensive source of information about SCSI commands and SCSI
messages used by the Super DLTtape™-generation (SDLT) tape drives. This document is written for
original equipment manufacturers (OEMs) that are integrating the Quantum SDLT tape drive into a
system or subsystem. Background knowledge of the SCSI-3, SAM, SPC, SPI, and SSC standards is
assumed.
This document’s primary audience is the OEM technical system integrators who are responsible for the
SCSI interface. In addition, technically astute end-users can use this manual for installation and
operation of the tape drive, although that group is a secondary audience.
•Current standards documents available from www.t10.org:
SCSI Architecture Model (SAM-2)
SCSI Parallel Interface (SPI-3)
SCSI Primary Commands (SPC-2)
SCSI Stream Commands (SSC)
1.4Structure of this Manual
•Chapter 1, Introduction, is the chapter you are currently reading.
•Chapter 2, SCSI Parallel Protocol, provides an overview of SDLT tape drive-specific SCSI
information. Background knowledge of the SCSI-3, SAM, SPC, SPI, and SSC standards is
assumed.
•Chapter 3, SCSI Messages, lists and describes the SCSI messages supported by SDLT tape
drives. The SCSI message system allows communication between SCSI initiators and SCSI targets
(the SDLT tape drive, in this case) for interface management and command elaboration and
qualification.
•Chapter 4, SCSI Commands, describes in detail each command supported by SDLT tape drives.
The SCSI command system enables a SCSI initiator to direct an SDLT tape drive to perform a
wide range of operational and diagnostic functions. This chapter also provides Sense Key and
Additional Sense Code information for the REQUEST SENSE and SEND DIAGNOSTIC SCSI
commands as well as density codes for the MODE SELECT and MODE SENSE commands.
This manual uses the following conventions to designate specific elements:
Table 1-1. Typographical Conventions
ElementConventionExample
CommandsUppercase (unless case-
sensitive)
MessagesUppercaseIDENTIFY
Hexadecimal NotationNumber followed by
lowercase h
Binary NotationNumber followed by
lowercase b
Decimal NotationNumber without suffix512
AcronymsUppercasePOST
AbbreviationsLowercase, except where
standard usage requires
uppercase
1.6For More Information
The web site http://www.dlttape.com includes information about the various DLTtape systems
available for purchase. To locate specific product-related support information or to register your tape
drive, visit http://www.quantum.com/AM/support/. Once you are registered, you can download a
variety of useful drivers, software programs, and diagnostic utilities.
TEST UNIT READY
25h
101b
Mb (megabits)
MB (megabytes)
For personalized information about Quantum’s reliable data protection products, call 1-800-624-5545
in the U.S.A. and Canada.
81-81200-02 REV A01January 20051-3
Reader CommentsSDLT 600 SCSI Interface Guide
1.7Reader Comments
Quantum is committed to providing the best products and service. We encourage your comments,
suggestions, and corrections for this manual. Please send all comments on existing documentation to:
Quantum Technical Publications
4001 Discovery Dr.
Suite 1100
Boulder, Colorado USA 80303
•“Background Information About SCSI” describes the knowledge required to use this manual
•“Information Transfer Phases” describes the specifics of information transfer in SDLT tape drives.
81-81200-02
REV A01
CHAPTER 2
SCSI Parallel Protocol
successfully.
•“SCSI Bus Conditions” describes the two asynchronous conditions of the SCSI bus.
2.1Background Information About SCSI
Small Computer System Interface (SCSI) is one of the industry’s most widely adopted I/O interfaces;
it is widely used in computing platforms from personal computers to mainframes to peripheral devices
of all types. SDLT tape drives conform to the SPI-3 standard. You should familiarize yourself with the
SCSI-3, SAM-2, SPC-2, SPI-3, and SSC standards before using the remaining portions of this manual.
Important features of SPI-3 implementation include the following:
•Efficient peer-to-peer I/O bus for up to 15 devices
•Asynchronous transfer rates that depend only on device implementation and cable length
•Logical addressing (rather than physical addressing) for all data blocks
•Multiple initiators and multiple targets
•Distributed arbitration (bus contention logic)
•Command set enhancement.
NOTE: Complete SCSI standards documents are available at www.t10.org.
81-81200-02 REV A01January 20052-1
Information Transfer PhasesSDLT 600 SCSI Interface Guide
2.2Information Transfer Phases
The COMMAND, DATA, STATUS, and MESSAGE phases are known as the information transfer
phases because they are used to transfer data or control information. Keep the following guidelines in
mind:
•SDLT tape drives support wide asynchronous and synchronous data transfers.
•Odd parity is generated during all information transfer phases during which the device writes data
to the SCSI bus and parity is checked during all transfer phases in which data is read from the bus
by the SDLT tape drive.
•SDLT tape drives support block sizes from 4 bytes to 16,777,212 bytes.
•The tape drive disconnects from the SCSI bus at regular intervals during information transfer
phases to allow other devices to access the bus. These disconnects are user-configurable using the
Disconnect-Reconnect Page of the MODE SELECT command.
•The SDLT tape drive does not act as an initiator on the SCSI bus. Therefore, the drive does not:
1) generate unsolicited interrupts to the bus, 2) initiate its own SCSI commands, or 3) assert bus
reset.
•The SDLT 600 SCSI drive supports both LVD and single-ended bus configurations.
2.3SCSI Bus Conditions
The SCSI bus has two asynchronous conditions:
•Attention Condition
•Reset Condition
2.3.1 Attention Condition
The Attention Condition informs an SDLT tape drive that an initiator has a message ready. The drive
gets the message by performing a MESSAGE OUT phase. The Attention Condition requires the
following timing:
•The initiator creates the Attention Condition by asserting ATN at any time except during the
ARBITRATION or BUS FREE phases.
•The initiator negates the ATN signal at least two deskew delays before asserting the ACK signal
while transferring the last byte of the message.
•If an initiator wishes to send a message before transitioning to a new bus phase, the initiator asserts
the ATN signal, then waits at least two deskew delays before negating the ACK signal for the last
byte transferred in the current bus phase. Asserting the ATN signal later may not be honored until
a later bus phase which may result in an unexpected action.
The SDLT tape drive responds with a MESSAGE OUT phase, as described in the following table:
Table 2-1. Drive’s MESSAGE OUT Phase Response
ATN Signal True in Phase...The Drive Enters MESSAGE OUT…
COMMANDAfter transferring part or all of the command descriptor block
bytes.
DATAAt the drive’s earliest convenience (often on a logical block
boundary). The initiator continues REQ/ACK handshakes
until it detects the phase change.
STATUSAfter the initiator has acknowledged the status byte.
MESSAGE INBefore it sends another message. This permits a MESSAGE
PARITY ERROR message from the initiator to be associated
with the appropriate message.
SELECTION
RESELECTION
1.Before the initiator releases BSY, provided the initiator asserted ATN.
2.The initiator should only assert the ATN signal during a RESELECTION phase to transmit a TARGET
RESET or DISCONNECT message.
1
2
Immediately after that SELECTION phase.
After the drive has sent its IDENTIFY message for that
RESELECTION phase.
The initiator keeps the ATN signal asserted if more than one byte is to be transferred. The initiator may
negate the ATN signal at any time, except that it should not negate ATN while the ACK signal is
asserted during a MESSAGE OUT phase.
NOTE: Normally, the initiator negates the ATN signal while the REQ signal is
true and the ACK signal is false during the last REQ/ACK handshake of
the MESSAGE OUT phase.
81-81200-02 REV A01January 20052-3
SCSI Bus ConditionsSDLT 600 SCSI Interface Guide
2.3.2 Reset Condition
The SDLT tape drive responds to bus reset conditions as follows:
•Within 250 milliseconds—and typically under 4 milliseconds—after a bus reset, the drive
responds to SCSI bus selections and returns the appropriate normal responses. Tape motion
commands are returned with Check Condition status, Sense Key of Not Ready, until the drive
makes the medium ready.
•The drive rewinds the tape medium to Beginning of Partition (BOP, which is Beginning of Tape
[BOT]).
NOTE: The SDLT tape drive does not implement the hard reset alternative for bus
RESET processing.
The SDLT tape drive recognizes multiple bus resets in succession as well as bus resets of arbitrarily
long duration (power-on conditions). It recovers within the time limits specified above following the
last bus reset.
2-4January 200581-81200-02 REV A01
SDLT 600
SCSI Interface Guide
SCSI Messages
This chapter provides a detailed description of the SCSI messages SDLT tape drives support.
Specifically, it covers the following topics:
•“Message Format” lists the specific format of SCSI messages.
•“Supported SCSI Messages” contains descriptions of each of the messages supported by the drive.
81-81200-02
REV A01
CHAPTER 3
SCSI Messages
3.1Message Format
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 across multiple 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 3-3 .
When a connection to the SDLT tape drive is established (that is, the drive is selected with ATN
asserted), the first message byte passed by the initiator must be either an IDENTIFY, ABORT TASK
SET, or TARGET RESET message. If not, the drive discards the message, saves no status information,
and enters the BUS FREE phase.
If an initiator supplies an unsupported message (for example, TASK COMPLETE or a reserved or
undefined message code), the drive returns a MESSAGE REJECT message and continues where it left
off (possibly returning to MESSAGE OUT if ATN is raised).
81-81200-02 REV A01January 20053-1
Message FormatSDLT 600 SCSI Interface Guide
The first byte of the message, as defined in Table 3-1, determines the format of the message.
Table 3-1. SCSI Message Format
Message CodeMessage
00hOne-byte message (TASK COMPLETE)
01hExtended message
02h – 1FhOne-byte message
20h – 2FhTwo-byte message
30h – 54hReserved
55hOne-byte message
56h – 7FhReserved
80h – FFhOne-byte message (IDENTIFY)
Two-byte messages consist of two consecutive bytes. The value of the first byte, as defined in
Table 3-1, determines which message will 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 multiple-byte extended message. The
minimum number of bytes sent for an extended message is three. The extended message format is
shown in Figure 3-1, and the data fields are described in Table 3-2.
Table 3-2. SDLT Tape Drive Extended Message — Field Descriptions
FieldDescription
Extended
Message
Length
Extended
Message
Code
This field specifies the length, in bytes, of the Extended Message Code plus the Extended
Message Arguments that follow. 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.
The drive supports the following Extended Messages:
CodeDescription
01hSynchronous Data Transfer Request
03hWide Data Transfer Request
04hParallel Protocol Request
3.2Supported SCSI Messages
The SDLT tape drive supports the messages listed in Table 3-3. The message code and the direction of
the message flow is also included in the table (In = target-to-initiator; Out = initiator-to-target). This
section describes each message the drive supports.
SYNCHRONOUS DATA TRANSFER REQUEST
(extended message 01h)
WIDE DATA TRANSFER REQUEST (extended
message 03h)
3.2.1 ABORT TASK SET (06h)
The initiator sends this message to the SDLT tape drive to clear the current I/O process on the selected
logical unit. Buffered (cached) write operations are completed if possible. The drive 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.
An initiator may send this message to a logical unit that is not currently performing an operation for
the initiator. If the initiator does not select a logical unit, the drive enters the BUS FREE phase and no
commands, data, or status on the drive are affected.
InOut
InOut
InOut
If a WRITE command is in progress and STATUS has not been sent to the initiator when the drive
receives this message, the drive may write some or all of the data for the WRITE command to the
medium.
An initiator sends the TARGET RESET message to direct the SDLT tape drive to clear all I/O
processes. This message causes the drive to:
1. Flush the contents of the cache to tape and go to the BUS FREE phase.
2. Execute a soft reset, leaving the drive as if a Bus Reset had occurred.
The drive creates a Unit Attention condition for all initiators after accepting and processing a TARGET
RESET message. The additional sense code is set to TARGET RESET OCCURRED.
If a WRITE command is in progress and STATUS has not been sent to the initiator when the drive
receives this message, the drive may write some or all of the data for the WRITE command to the
medium.
3.2.3 TASK COMPLETE (00h)
The SDLT tape drive sends the TASK COMPLETE message to an initiator to indicate that an I/O
process has completed and that the drive sent VALID STATUS to the initiator. After successfully
sending this message, the drive enters the BUS FREE phase by releasing the BSY signal. The drive
considers the message transmission successful when it detects the negation of ACK for the TASK
COMPLETE message with the ATN signal false. If the SDLT tape drive receives the TASK
COMPLETE message, the drive handles it as an illegal message, returning MESSAGE REJECT.
3.2.4 DISCONNECT (04h)
The SDLT tape drive sends the DISCONNECT message to inform the initiator that the drive is about
to break the present connection by releasing the BSY signal and that a later reconnect is 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 drive enters the BUS FREE phase by releasing the BSY signal.
The initiator may also send the DISCONNECT message to tell the drive to suspend the current phase
and disconnect from the bus. The drive’s response to and its handling of a DISCONNECT message are
based on when, in the I/O process, the initiator sends the DISCONNECT message. Tab l e 3-4
summarizes the drive’s response.
Table 3-4. Drive’s Response to DISCONNECT Message
BUS PhaseDrive Response
SELECTIONThe drive discards the DISCONNECT message and enters the BUS FREE
Table 3-4. Drive’s Response to DISCONNECT Message (Continued)
BUS PhaseDrive Response
COMMANDThe drive discards the DISCONNECT message and enters the BUS FREE
phase. The drive ignores the ATTENTION request while it fetches the
Command Descriptor Block. The drive does not switch to MESSAGE OUT
until the current DMA completes.
DATAThe drive ignores the ATTENTION request while the current data transfer
completes; that is, the drive does not switch to MESSAGE OUT until after
the current DMA completes. The drive returns a MESSAGE REJECT
message and responds with CHECK CONDITION status, indicating the
command aborted because of an invalid message.
STATUSThe drive sends a MESSAGE REJECT message, then sends TASK
COMPLETE.
MESSAGE INThe drive sends a MESSAGE REJECT message and enters the BUS FREE
phase.
3.2.5 IDENTIFY (80h - FFh)
Either the initiator or the SDLT tape drive sends the IDENTIFY message to establish or re-establish
the physical connection path between an initiator and drive for a particular logical unit under the
conditions listed below. Figure 3-2 shows the format of the IDENTIFY message and Tab l e 3-5
describes the data field contents.
Bit76543210
IdentifyDiscPrivLUN
Figure 3-2. IDENTIFY Message — Data Format
Table 3-5. IDENTIFY Message — Field Descriptions
FieldDescription
IdentifyMust be set to 1, indicating that the current message is an IDENTIFY message.
DiscPrivDisconnect Privilege. May be set to 0 provided that no other I/O process is
currently active in the drive. If this bit is not set to 1 and other I/O processes are
currently active in the drive, the drive returns a BUSY status.
The SDLT tape drive sends the IGNORE WIDE RESIDUE message to the 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. The drive sends this message immediately following the DATA IN
phase and before any other messages. Figure 3-3 illustrates the data format of the IGNORE WIDE
RESIDUE message. Table 3-6 describes the field definitions.
Bit
Byte
0Message Code (23h)
1Ignore (01h)
76543210
Figure 3-3. IGNORE WIDE RESIDUE Message — Data Format
Table 3-6. IGNORE WIDE RESIDUE Message — Field Definitions
IgnoreInvalid Data Bits (16-bit Transfers)
00hReserved
01hDB(15 - 8)
02h - FFhReserved
3.2.7 INITIATOR DETECTED ERROR (05h)
The initiator sends the INITIATOR DETECTED ERROR message to inform the SDLT tape drive that
an error has occurred that does not preclude the drive from retrying the operation (for example, a bus
parity error). The source of the error may either be related to previous activities on the SCSI bus or
may be strictly drive-related. When the drive receives this message, it may attempt to re-transfer the
last command, data, or status bytes using the RESTORE POINTERS message mechanism.
The drive’s response to and its handling of an INITIATOR DETECTED ERROR message are based on
when, in the I/O process, the initiator sends the message. Table 3-7 summarizes the drive’s response.
Table 3-7. Drive’s Response to INITIATOR DETECTED ERROR Message
Bus PhaseDrive Response
SELECTIONThe drive discards the INITIATOR DETECTED ERROR message and then
enters the BUS FREE phase.
COMMANDThe drive discards any Command Descriptor Block bytes fetched from the
initiator, sets the Sense Key to ABORTED COMMAND, and sets the
Additional Sense Code to INITIATOR DETECTED ERROR MESSAGE
RECEIVED. The drive then sends the CHECK CONDITION status and the
TASK COMPLETE message and then enters the BUS FREE phase.
DATAThe drive discards the INITIATOR DETECTED ERROR message, sets the
Sense Key to ABORTED COMMAND, and sets the Additional Sense Code to
INITIATOR DETECTED ERROR MESSAGE RECEIVED. The drive then
sends the CHECK CONDITION status and the TASK COMPLETE message
and then enters the BUS FREE phase.
STATUSThe drive sends a RESTORE POINTERS message, returns to the STATUS
phase, resends the STATUS command, and continues the I/O process.
MESSAGE INThe drive discards the INITIATOR DETECTED ERROR message, sets the
Sense Key to ABORTED COMMAND, and sets the Additional Sense Code to
INITIATOR DETECTED ERROR MESSAGE RECEIVED. The drive then
sends the CHECK CONDITION status and the TASK COMPLETE message
and then enters the BUS FREE phase.
3.2.8 LOGICAL UNIT RESET (17h)
This message causes the drive to execute a logical unit reset function on the logical unit identified by
the last IDENTIFY message. The logical unit reset function is the same as would be performed
following a BUS DEVICE RESET message except only the logical unit selected is affected. The drive
enters the BUS FREE phase as part of processing this message and aborts all commands to the selected
logical unit.
The initiator sends this message to tell the SDLT tape drive that the last message byte the drive passed
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 drive can determine which message has the parity error. If the drive receives this message under
any other condition, it proceeds directly to the BUS FREE phase by releasing the BSY signal,
signifying a catastrophic error.
The drive’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.
3.2.10 MESSAGE REJECT (07h)
The initiator or SDLT tape drive sends this message to indicate that the last message received was
illegal 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. The drive issues the
MESSAGE REJECT message in response to any message it considers to be illegal or not supported.
The drive sends this message to the initiator before requesting any additional message bytes.
3.2.11 NO OPERATION (08h)
If the SDLT tape drive requests a message, the initiator sends a NO OPERATION message if it does
not currently have any other valid message to send. The drive ignores the NO OPERATION message.
PARALLEL PROTOCOL REQUEST (PPR) messages (as shown in Table 3- 4 ) are used to negotiate
synchronous transfer agreements and wide data transfer agreements, and to set the protocol options
between two SCSI devices.
Bit
Byte
0
1Extended Message Length (06h)
2Parallel Protocol Request (04h)
3Transfer Period Factor
4Reserved
5REQ/ACK Offset
6Transfer Width Exponent
7
76543210
Extended Message Identifier (01h)
Figure 3-1)
(see
ReservedDT_
REQ
Rsv’d
Figure 3-4. PARALLEL PROTOCOL REQUEST Message — Data Format
The PPR message is required to configure an SDLT tape drive. This command sets the transfer period,
offset, transfer width, and clocking all in one message.
Support for the PPR message is indicated by the Clocking field in the Standard Inquiry page. The PPR
message can also be used to set the transfer period, offset, and transfer width on an SDLT tape drive
with an Ultra 2 interface card. To enable it, set the MODE SELECT Vendor Specific EEPROM
parameter EnablePPRMsg to 1.
The PPR message allows the host and target devices to negotiate operating conditions of the SCSI bus.
An SDLT tape drive responds to a PPR message with a reciprocal PPR message containing acceptable
parameters for the interface. An SDLT tape drive never initiates a PPR negotiation.
Details about how to configure the PPR message are shown in Table 3-8 .
Table 3-8. Features of the PARALLEL PROTOCOL REQUEST Message
FieldDescription
DT_REQDouble Transition Clocking Request. This bit indicates a request for Double
Transition Clocking, which means that two units of data are transferred for
each clock cycle. Support for the PPR message is indicated by the Clocking
field in the Standard Inquiry page.
Transfer Width
Exponent
Transfer Period
Factor
Valid transfer widths for the SDLT tape drive are 8 bits (transfer width =
00h) and 16 bits (transfer width = 01h). Other transfer widths are reserved.
09h = 12.5 nsec Transfer Period, 80 MHz
0Ah = 25 nsec Transfer Period, 40 MHz
0Ch = 50 nsec Transfer Period, 20 MHz
19h = 100 nsec Transfer Period, 10 MHz
32h = 200 nsec Transfer Period, 5 MHz
3.2.13 RESTORE POINTERS (03h)
The SDLT tape drive sends the RESTORE POINTERS message 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 drive receives the RESTORE POINTERS message, it switches to the message in phase and
returns MESSAGE REJECT.
3.2.14 SAVE DATA POINTER (02h)
The SDLT tape drive sends the SAVE DATA POINTER message to direct the initiator to copy the
current data pointer to the saved data pointer for the current I/O process.
The drive sends this message before a disconnect during a data transfer. It may not send a SAVE DATA
POINTER message if it intends to move directly to the STATUS phase. If the drive receives this
message, it enters the message-in phase and returns MESSAGE REJECT.
3.2.15 SYNCHRONOUS DATA TRANSFER REQUEST (extended
message 01h)
This extended message allows the SDLT tape drive and initiator to agree on the values of the
parameters relevant to synchronous transfers. The SYNCHRONOUS DATA TRANSFER REQUEST
message has the format shown in Figure 3-5.
NOTE: The ANSI SPI-4 standard prohibits target devices from initiating
negotiations using the PARALLEL PROTOCOL REQUEST message.
Instead, targets are required to negotiate using the WIDE DATA
TRANSFER REQUEST and SYNCHRONOUS DATA TRANSFER
REQUEST messages. The SDLT tape drive initiates negotiations starting
with a WIDE DATA TRANSFER REQUEST message before transferring
any data if transfer parameters have not been established or have been
lost. See SPI-4.
Bit
Byte
0
1Length (03h)
2SYNCHRONOUS DATA TRANSFER REQUEST (01h)
3Transfer Period
4Transfer REQ/ACK Offset
76543210
Extended Message Identifier (01h)
Figure 3-1)
(see
Figure 3-5. SYNCHRONOUS DATA TRANSFER REQUEST Message — Data Format
A SCSI device initiates a SYNCHRONOUS DATA TRANSFER REQUEST message exchange
whenever a previously arranged transfer 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 any SCSI reset condition
•After a TARGET RESET message
•After a power cycle
•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 the DATA IN and DATA OUT phases only. All other information transfer
phases must use asynchronous transfers.
The SDLT tape drive implements both the wide data transfer and synchronous data transfer options. If
both wide and synchronous data transfers are used, the wide data transfer agreement must be
negotiated first. If a synchronous data transfer agreement is in effect, the drive resets the synchronous
agreement to asynchronous mode after accepting a WIDE DATA TRANSFER REQUEST message.
If the Transfer Period requested is less than the minimum value the drive supports, the drive adjusts the
return value up to the minimum supported value.
Not all possible transfer periods between the minimum and maximum values are supported. If the
Transfer Period requested is between the minimum and maximum supported values, but not exactly
achievable by the drive, the drive returns the request value and the drive transmits 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 less than this returns a request
for asynchronous mode.
Table 3-9. Transfer Periods and Transfer Rates
Transfer PeriodTransf e r R ate
0Ah40 MHz, 25 nsec Transfer Period
0Bh33 MHz, 30.3 nsec Transfer Period; Super DLTtape uses 37.5 nsec period
0Ch20 MHz, 50 nsec Transfer Period
0Dh – 5Dh(4 * Transfer Period) nsec
The drive’s minimum supported value for Transfer Period is 0Ah when the bus is operating in LVD
mode. When operating in SE (Single-Ended) mode, the minimum Transfer Period value is 0Ch.
When the Transfer REQ/ACK value is non-zero, the drive will transfer data using synchronous
transfers; a Transfer REQ/ACK offset value of zero indicates asynchronous transfers. If the host
requests a Transfer REQ/ACK offset value greater than the maximum value that the drive supports, the
drive responds with the maximum value that it supports.
3.2.16 WIDE DATA TRANSFER REQUEST (extended message
03h)
Figure 3-6 illustrates the message formats.
Bit
Byte
0
1Extended Message Length (02h)
2WIDE DATA TRANSFER REQUEST (03h)
3Transfer Width Exponent
76543210
Extended Message Identifier (01h)
Figure 3-1)
(see
Figure 3-6. WIDE DATA TRANSFER REQUEST Message — Data Format
The SDLT tape drive initiates a WIDE DATA TRANSFER REQUEST message exchange 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 TARGET 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 eight-bit data path.
The drive implements both the wide data transfer option and synchronous data transfer option. If both
wide and synchronous data transfers are used, the wide data transfer agreement must be negotiated
first. If a synchronous data transfer agreement is in effect, the drive resets the synchronous agreement
to asynchronous mode after accepting a WIDE DATA TRANSFER REQUEST message.
The transfer width established applies to all logical units. Valid transfer widths for the SDLT tape drive
are 8 bits (transfer width = 00h) and 16 bits (transfer width = 01h). Other transfer widths are reserved.
3-14January 200581-81200-02 REV A01
SDLT 600
SCSI Interface Guide
SCSI Commands
This chapter describes the supported SCSI commands, options, and error recovery procedures
implemented in the Quantum SDLT tape drive. This chapter does not fully reiterate the entire ANSI
SCSI specification; for information of this nature, refer to the SCSI specification itself.
The web sites http://www.scsita.org and http://www.t10.org are also helpful sources of information.
81-81200-02
REV A01
CHAPTER 4
SCSI Commands
4.1Overview of SCSI Command and Status
Processing
The Quantum SDLT tape drive supports the SCSI-3 command set. The SDLT tape drive supports the
SCSI commands listed in Tabl e 4-1.
Table 4-1. SCSI Commands Supported by SDLT Tape Drives
CommandOperation CodeSubsection
ERASE19hPage 4-10
INQUIRY12hPage 4-11
LOAD UNLOAD1BhPage 4-28
LOCATE2BhPage 4-30
LOG SELECT4ChPage 4-31
LOG SENSE4DhPage 4-39
MODE SELECT (6) / (10)15h / 55hPage 4-67
MODE SENSE (6) / (10)1Ah / 5AhPage 4-107
PERSISTENT RESERVE IN5EhPage 4-135
81-81200-02 REV A01January 20054-1
Overview of SCSI Command and Status ProcessingSDLT 600 SCSI Interface Guide
Table 4-1. SCSI Commands Supported by SDLT Tape Drives (Continued)
Table 4-1. SCSI Commands Supported by SDLT Tape Drives (Continued)
CommandOperation CodeSubsection
WRITE BUFFER3BhPage 4-249
WRITE FILEMARKS10hPage 4-252
1.SA = Service Action
NOTES:1The SDLT tape drive does not act as an initiator on the SCSI
bus. Therefore, the drive does not 1) generate unsolicited
interrupts to the host, 2) initiate its own SCSI commands, or
3) assert bus RESET.
2 The RECEIVE DIAGNOSTIC RESULTS and SEND
DIAGNOSTIC commands implement vendor-specific pages
to test the drive during the manufacturing process. Quantum
recommends that initiators specify only the non-page format
variants of these commands (PF=0) for all pages except page
40h.
4.1.1 Status and Error Reporting
SCSI message-level errors are communicated by messages that are defined specifically for that
purpose (for example, MESSAGE PARITY ERROR, MESSAGE REJECT). Message-level errors are
also handled by drive-managed retries. Refer to Chapter 3, “SCSI Messages” for more detailed
message-handling information.
SCSI command-level errors are communicated by a status code that the drive returns during the
STATUS phase. This phase occurs at the end of each command unless one of the following events
terminates the command:
•ABORT TASK SET message
•TARGET RESET message
•Reset condition
•Unexpected disconnect.
The status code is contained in bits 1 through 5 of the status byte. Bits 0, 6, and 7 are reserved.
Table 4-2 describes the status codes the drive returns.
81-81200-02 REV A01January 20054-3
Overview of SCSI Command and Status ProcessingSDLT 600 SCSI Interface Guide
Table 4-2. Status Codes
Status
Code
00hGOODThe drive successfully completed the command.
DefinitionMeaning
02hCHECK
CONDITION
08hBUSYThe drive cannot currently service the command and has
18hRESERVATION
CONFLICT
An exception condition occurred and the drive has established
a Contingent Allegiance condition.
discarded the CDB. The initiator may retry the command later.
The drive returns this status when an initiator attempts to
reserve the drive when another initiator has already reserved it
with a RESERVE UNIT, RESERVE (10), or PERSISTENT
RESERVE OUT command. The drive never returns this status
for INQUIRY or REQUEST SENSE commands.
4.1.2 DATA Phase Command Components
Many of the SCSI commands cause data to be transferred between the initiator and the SDLT tape
drive. The content and characteristics of this data are command-dependent. Table 4 - 4 lists the
information transmitted with each of the commands.
The drive uses the “Length in CDB” column of Table 4-4 to determine how much command-related
data are to be transferred. Table 4-3 lists how the units (bytes or logical blocks) for the different Length
fields are implied by the Length field name as follows:
Table 4-3. Units for Length Fields
Field NameUnits Implied
Allocation LengthBytes of data the drive is allowed to send to the initiator.
Parameter List LengthBytes of data the initiator has available for the drive.
Transfer LengthLogical number of data blocks or data bytes the initiator wants
transferred or verified.
Byte Transfer LengthBytes of data the initiator wants transferred.
The Data Out column in Table 4- 4 lists the information the initiator passes to the drive as part of the
command. The Data In column lists the information the drive sends to the initiator. Numbers in
Queued Unit Attentions are implemented on the SDLT tape drive and are maintained separately for
each valid LUN for each initiator. Unit Attentions are created in each of the following circumstances:
•At power-on.
•At Bus Reset
•On a BUS DEVICE RESET message
•When the medium may have changed asynchronously.
•When another initiator changes the Mode parameters.
•When a firmware (microcode) update has completed.
•Change of SCSI bus transceivers (SE or LVD).
Up to three Unit Attentions may be queued for each initiator. If an initiator does not clear its queued
Unit Attentions, any additional Unit Attention conditions are not reported.
4.1.4 Behavior at Power-On
The SDLT tape drive’s behavior at power-on consists of the following:
•The drive’s SCSI lines are set to high impedance.
•The design of the drive prevents it from generating any spurious signals on the SCSI bus during
power-on.
•Within five seconds of power-on, the tape drive responds to SCSI bus selections and returns
appropriate, normal responses. The drive returns tape motion commands with CHECK
CONDITION status, Sense Key set to NOT READY, until the tape medium is ready.
•The drive rewinds the tape to Beginning of Tape (BOT).
•The drive goes through a calibration process at power-on and loading of media.
•The drive recognizes multiple, successive SCSI bus resets and SCSI bus resets of arbitrarily long
duration. The drive recovers within the time limits specified above following the last SCSI bus
reset.
The Quantum SDLT tape drive contains a data cache that buffers blocks and filemarks until it writes
them to tape. This section describes what happens when the drive writes, or “flushes,” those blocks to
tape. A MODE SELECT parameter allows the data cache to be disabled (unbuffered mode). In this
mode, every WRITE command causes data to be written to the tape medium before the drive returns
the STATUS byte and the TASK COMPLETE message to the host.
NOTE: Unbuffered mode is NOT recommended due to the poor performance that
may result.
The drive writes the contents of the write data cache to the tape medium under the following
circumstances:
•When the initiator issues a WRITE FILEMARKS command with the Immediate bit set to 0.
•When data has been in the cache longer than the maximum time specified by the value of the
MODE SELECT command Write Delay Time parameter (the default is 10 seconds).
•When the drive receives a non-write-type media access command.
•When a RESET condition occurs.
4.2SCSI Command Descriptions
The SCSI command descriptions that make up the rest of this chapter contain detailed information
about each command the SDLT tape drive supports. The SCSI commands are presented in alphabetical
order. Fields common to many of the SCSI commands are not repeated for every command; instead
they are supported as shown in Table 4 - 5:
Table 4-5. Fields Common to Many SCSI Commands
Name of FieldHow Field is Supported in SCSI Commands
Logical Unit Number (LUN)LUN for the SDLT tape drive is 0.
ControlAll SCSI commands must have a Control byte, which is implemented as
described in SCSI Architecture Model – 3 (SAM–3).
ReservedReserved bits, fields, bytes, and code values are set aside for future
standardization and must be set to 0. If the drive receives a command that
contains non-zero bits in a reserved field or a reserved code value, the
drive terminates the command with a CHECK CONDITION status and
the Sense Key is set to ILLEGAL REQUEST.
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 to 8) of the LOG
SELECT command, shown as follows:
Bit
Byte
7 – 8
76543210
(Bytes 0 – 6)
(MSB)
Parameter List Length
(LSB)
This sample indicates that the most significant bit (MSB) of the field is bit 7 of byte 7; the least
significant bit is bit 0 of byte 8. The shorthand version of presentation is used in this manual to save
space.
This is an alternate, “shorthand” presentation for:
Bit
Byte
7(MSB)
8
76543210
(Bytes 0 – 6)
Parameter List Length
(LSB)
81-81200-02 REV A01January 20054-9
SDLT 600
SCSI Interface Guide
SCSI Commands
ERASE Command (19h)SDLT 600 SCSI Interface Guide
81-81200-02
REV A01
4.3ERASE Command (19h)
The ERASE command erases the data on the tape medium. The SDLT tape drive erases the data only if
the Long bit is set to 1 and the drive receives the ERASE command while it is at Beginning of Tape
(BOT). If the Long bit is set to 0, this command has no effect on the tape medium.
NOTE: The time required to completely erase a Super DLTtape II cartridge is
more than 3 hours.
Bit
Byte
0Operation Code (19h)
1ReservedImmedLong
2 – 4Reserved
5Control
76543210
Figure 4-1. ERASE Command Descriptor Block — Data Format
Table 4-6. ERASE Command Descriptor Block — Field Descriptions
FieldDescription
ImmedImmediate. If set to 0, the drive does not return status until the selected operation
has completed. If set to 1, the drive returns status as soon as it initiates the
operation.
LongMust be set to 1 to perform an erase operation. Issuing an ERASE command when
the tape is not at BOT is an ILLEGAL REQUEST. If set to 0, the drive performs no
operation—the ERASE command does not affect the tape.
The INQUIRY command allows the initiator to direct all attached devices to return information about
themselves. SDLT devices respond by providing a variety of information, including their World Wide
Name and other important characteristics. The SDLT tape drive identifies itself as a Sequential Access
Storage Device that implements the SCSI-3 protocol.
NOTE: The tape drive does not need to access its tape medium to respond to the
INQUIRY command.
The drive can provide different categories of data in response to an INQUIRY command:
•Standard Inquiry Data — contains basic data about the drive, including vendor-specific inquiry
data that precisely identifies the revision of SDLT tape drive subsystem components.
•Vital Product Data — comprises several pages of additional data. Each Vital Product Data page
requires a separate INQUIRY command from the initiator. To see a list of specific Vital Product
Data pages returned by this SDLT tape drive, refer to “Supported Vital Product Data Page (00h)”
on page 4-17.
An INQUIRY command is neither affected by—nor does it clear—a Unit Attention condition.
Bit
Byte
0Operation Code (12h)
1ReservedObsolete EVPD
2Page Code
3 – 4
5Control
76543210
(MSB)
Allocation Length
(LSB)
Figure 4-2. INQUIRY Command Descriptor Block — Data Format
Table 4-7. INQUIRY Command Descriptor Block — Field Descriptions
FieldDescription
EVPDEnable Vital Product Data. If set to 0, the drive returns the Standard Inquiry Data.
If EVPD is set to 1, the drive returns the Vital Product Data Page specified by
Page Code.
Page CodeSpecifies the Vital Product Data Page that the drive is to return when EVPD is set
to 1. Figure 4-5 on page 4-17 shows the Page Codes for the Vital Product Data
pages the drive supports.
Allocation
Length
Specifies the number of bytes of inquiry information the drive is allowed to return
to the initiator during the command’s DATA IN phase. The drive does not return
Error status if the value in this field truncates the requested information.
The following table contains field descriptions for the data the drive returns.
Table 4-8. Standard Inquiry Data Page — Field Descriptions
Field NameVal ueDescription
Peripheral Qualifier0This field contains 000b if the command is directed to a
valid device. The field contains 011b if there is no device
at the selected LUN.
Peripheral Device Type1This field contains 01h if the LUN is 0h, 8h if the LUN
selects an attached loader, or 1Fh if no device is attached
to the selected LUN.
RMB1Removable Medium Bit. Always set to 1.
Version04hThe drive supports ANSI SCSI-3 per SPC-2.
NormACA0Normal ACA Supported. When set to 0, indicates that the
drive does not support setting the NACA bit to 1 in the
Control byte of the CDB. When set to 1, indicates that the
drive supports setting the NACA bit to 1.
HiSup1Hierarchical Support. When set to 0, indicates that the
drive does not support the hierarchical addressing model
to assign LUNs to logical units. When set to 1, indicates
that the drive does support the hierarchical addressing
model to assign LUNs to logical units.
Response Data Format2This Standard Inquiry Data is in the format described in
the Version field.
Additional Length---The drive uses this field to indicate the number of
additional bytes of INQUIRY Response Data available.
The value depends on the number of version descriptors
returned in the INQUIRY Response Data.
SCCS0SCC Supported. The drive does not contain an embedded
storage array controller component. Always set to 0.
ACC0Access Controls Coordinator. The drive does not contain
an access controls coordinator. Always set to 0.
ALUA00bAsymmetric Logical Unit Access. Not supported. Always
set to 0.
3PC0Third-party Copy. Not supported. Always set to 0.
BQue0Tagged (Basic) Command Queuing. Not supported.
Always set to 0.
EncServ0Enclosure Services. The drive does not contain an
embedded enclosure services component. Always set
to 0.
Table 4-8. Standard Inquiry Data Page — Field Descriptions (Continued)
Field NameVal ueDescription
VS0Vendor Specific. Both VS bits are always set to 0.
MultiP0Multi Port. The drive is a single-port device that does not
implement multi-port requirements. Always set to 0.
MChnger0Medium Changer. The drive does not support attached
medium changer commands sent to the drive’s LUN.
Always set to 0.
Addr16116-bit Addressing. Always set to 1 to indicate that the
drive supports 16-bit-wide SCSI addresses.
RelAdr0Relative Addressing. Not supported. Always set to 0.
WBus161Wide Bus 16. Always set to 1 to indicate that the drive
supports 16-bit wide data transfers.
Sync1Synchronous Data Transfer. Always set to 1 to indicate
that the drive supports synchronous data transfers.
Linked0Linked Command Support. Not supported. Always set to
0.
CmdQue0Tagged Command Queuing. Not supported. Always set to
0.
Vendor IdentificationQUANTUMThe value in this field is left-aligned and set to
“QUANTUM”. The remainder of the field is filled with
space characters.
Product IdentificationSDLT600For the SDLT 600 tape drive, this field is set to
“SDLT600”, left-aligned, filled with space characters to
the end of the field.
Product Revision Level---Contains 4 bytes of ASCII data that provide the drive’s
firmware revision levels. The first 2 bytes are the version
number for servo code. The second 2 bytes are the
version number of the SCSI/read/write code. When a
firmware update is performed on the SDLT tape drive, the
second two bytes of the revision level change to reflect
that update.
Vendor Specific---See “Vendor Specific Inquiry Data Page” on page 4-17
for details about what types of vendor-specific
information are returned.
Clocking---Indicates level of data clocking supported. Set to 00b if
only single-edge transfers are supported; set to 11b to
indicate that both single- and dual-edge transfers are
supported (Ultra 160).
The following information precisely identifies the revision of SDLT tape drive subsystem components.
Note: Page content is subject to change at any time.
Bit
Byte
36Product FamilyReleased Firmware
37Firmware Major Version Number
38Firmware Minor Version Number
39EEPROM Format Major Version Number
40EEPROM Format Minor Version Number
41Firmware Personality
42Firmware Subpersonality
43Vendor Specific Subtype
44Controller Hardware Version Number
45Tape Drive EEPROM Version Number
46Tape Drive Hardware Version Number
47Media Loader Firmware Version Number
48Media Loader Hardware Version Number
76543210
49Media Loader Mechanical Version Number
50Media Loader Present Flag
51Library Present Flag
52 – 55Module Revision
Figure 4-4. Vendor Specific Inquiry Data Page — Data Format
NOTE: Refer also to “Subsystem Components Revision Page (C1h)” on
page 4-26 for information about an alternate method for accessing these
Table 4-9. Vendor Specific Inquiry Data Page — Field Descriptions
Field NameDescription
Product FamilyIndicates the data density of each of the SDLT tape drives as
follows:
ValueDrive Density
Ah110.0 / 220.0 GB
Bh160.0 / 320.0 GB
Ch300.0 / 600.0 GB
Released FirmwareDifferentiates between released and test versions of firmware.
When set to 1, indicates released code (Vxxx); when set to 0,
indicates field test code (Txxx). Released code has no minor
firmware version number (byte 38 is set to 0). For tracking
purposes, field test and engineering versions of code have nonzero minor firmware version numbers.
Version Number FieldsThese fields display the various version numbers in binary
format, instead of ASCII.
Firmware PersonalityNumeric indicator of firmware personality. Note that when set
to 4, indicates OEM family.
Firmware SubpersonalityIndicates the variant of the firmware personality. Always set to
1, indicating the primary firmware personality variant.
Vendor Specific SubtypeProduct identification.
Media Loader Present Flag When set to 0, indicates no loader present. Non-zero indicates
loader is present.
Library Present FlagWhen set to 0, indicates no library present. Non-zero indicates
library is present.
Module RevisionA 4-byte ASCII string representing the revision level of the tape
drive’s module (the controller PCBA attached to the drive).
Figure 4-6 shows the format of the Unit Serial Number page the drive returns.
Bit
Byte
0Peripheral QualifierPeripheral Device Type
1Page Code (80h)
2Reserved
3Page Length (10h)
4 – 19Serial Number
76543210
Figure 4-6. Unit Serial Number Page — Data Format
Table 4-10. Unit Serial Number Page — Field Descriptions
Field NameDescription
Serial NumberThe serial number given is the serial number of the module or the drive,
typically beginning with “MX”, indicating the site of manufacture. If the
drive serial number is valid, it is reported; otherwise, the module serial
number is reported. The serial number appears on the bar code label. The
drive returns the serial number in ASCII format.
Figure 4-7 shows the format of the Device Identification page the drive returns.
Bit
Byte
0Peripheral QualifierPeripheral Device Type
1Page Code (83h)
2Reserved
3Page Length
4 – nIdentification Descriptors
76543210
Figure 4-7. Device Identification Page — Data Format
Table 4-11. Device Identification Page — Field Descriptions
Field NameDescription
Peripheral
Qualifier
Peripheral
Device Type
Contains 000b if the command is directed to a valid device. Contains 011b if
there is no device at the selected LUN.
Contains 01h if the LUN is 0h, 8h if the LUN selects an attached library, or
1Fh if there is no device at the selected LUN.
Page CodeA value of 83h identifies this as the Device Identification page.
Page LengthIndicates the size of the returned Device Identification page.
Identification
Descriptors
The drive always returns the Vendor-unique Logical Unit Identifier and the
Logical Unit NAA Identifier. It may also return other identifiers. The
following identifiers are described in this section:
Table 4-12. Vendor-unique Logical Unit Identifier — Field Descriptions (Continued)
Field NameDescription
Identifier
Length
Specifies the length in bytes of the Identifier field. If the Allocation Length
field of the CDB is too small to transfer the entire identifier, the Identifier
Length value is not adjusted to reflect the truncation.
Vendor
Identification
Product
Identification
The value in this field is left-aligned and set to “QUANTUM”. The remainder
of the field is filled with space characters.
For the SDLT 600 drive, this field is set to “SDLT600”, left-aligned, and filled
with space characters to the end of the field.
Serial NumberThe serial number given is the serial number of the module or the drive,
typically beginning with “MX”, indicating the site of manufacture. If the drive
serial number is valid, it is reported; otherwise, the module serial number is
reported. The serial number appears on the bar code label. The drive returns the
serial number in ASCII format.
Figure 4-9 shows the format of the Logical Unit NAA Identifier.
Bit
Byte
0Protocol IdentifierCode Set (1)
1PIV (0)Rsv’dAssociation (0)Identifier Type (3h)
2Reserved
3Identifier Length (08h)
4 – 11
76543210
(MSB)
NAA Identifier (binary)
Figure 4-9. Logical Unit NAA Identifier — Data Format
Table 4-13. Logical Unit NAA Identifier — Field Descriptions
Field NameDescription
Protocol
Identifier
Set to 0.
(LSB)
Code SetIndicates the type of data found in the Identifier field. Set to 1h, indicating
binary data.
PIVProtocol Identifier Valid. Set to 0, indicating that the value returned in the
Protocol Identifier field should be ignored.
AssociationSet to 0, indicating that the Identifier is associated with the logical unit.
Identifier TypeType of identifier.
ValueDescription
3hNAA identifier
Identifier
Length
NAA IdentifierContains the Name Address Authority (NAA) identifier for the logical unit.
4-24January 200581-81200-02 REV A01
Specifies the length in bytes of the Identifier field. If the Allocation Length
field of the CDB is too small to transfer the entire identifier, the Identifier
Length value is not adjusted to reflect the truncation.
The following information precisely identifies the revision of SDLT tape drive subsystem components.
Note: Page content is subject to change at any time.
Bit
Byte
0Peripheral QualifierPeripheral Device Type
1Page Code (C1h)
2Reserved
3Page Length (39h)
4Product FamilyReleased Firmware
5Firmware Major Version Number
6Firmware Minor Version Number
7EEPROM Format Major Version Number
8EEPROM Format Minor Version Number
9Firmware Personality
10Firmware Subpersonality
11Vendor Specific Subtype
12Controller Hardware Version Number
13Tape Drive EEPROM Version Number
76543210
14Tape Drive Hardware Version Number
15Media Loader Firmware Version Number
16Media Loader Hardware Version Number
17Media Loader Mechanical Version Number
18Media Loader Present Flag
19Library Present Flag
20 – 23Module Revision
24 – 43Unit Serial Number
Figure 4-11. Subsystem Components Revision Page — Data Format
Table 4-15. Subsystem Components Revision Page — Field Descriptions
Field NameDescription
Product FamilyIndicates the data density of each of the SDLT tape drives as
follows:
ValueDrive Density
Ah110.0 / 220.0 GB
Bh160.0 / 320.0 GB
Ch300.0 / 600.0 GB
Released FirmwareDifferentiates between released and test versions of firmware.
When set to 1, indicates released code (Vxxx); when set to 0,
indicates field test code (Txxx). Released code has no minor
firmware version number (byte 38 is set to 0). For tracking
purposes, field test and engineering versions of code have nonzero minor firmware version numbers.
Version Number FieldsThese fields display the various version numbers in binary
format, instead of ASCII.
Firmware PersonalityNumeric indicator of firmware personality. Note that when set
to 4, indicates OEM family.
Firmware SubpersonalityIndicates the variant of the firmware personality. Always set to
1, indicating the primary firmware personality variant.
Vendor Specific SubtypeProduct identification.
Media Loader Present FlagWhen set to 0, indicates no loader present. Non-zero indicates
loader is present.
Library Present FlagWhen set to 0, indicates no library present. Non-zero indicates
library is present.
Module RevisionA 4-byte ASCII string representing the revision level of the tape
drive’s module (the controller PCBA attached to the drive).
Unit Serial NumberThe drive’s serial number; matches what is shown on the
The LOAD UNLOAD command instructs the SDLT tape drive to load or unload the tape inside the
data cartridge. If no data cartridge is in the drive, the LOAD UNLOAD command returns a CHECK
CONDITION status with the Sense Key set to NOT READY. Likewise, if the drive receives a LOAD
UNLOAD command with the Immediate bit set and then it receives another command that requires
tape motion or if it receives a TEST UNIT READY command, the drive returns a CHECK
CONDITION status with the Sense Key set to NOT READY.
Before executing the LOAD UNLOAD command, the drive writes any cached write data to the tape.
Bit
Byte
0Operation Code (1Bh)
1ReservedImmed
2 – 3Reserved
4ReservedHoldEOTReTenLoad
5Control
76543210
Figure 4-12. LOAD UNLOAD Command Descriptor Block — Data Format
Table 4-16. LOAD UNLOAD Command Descriptor Block — Field Descriptions
Field NameDescription
ImmedImmediate. When set to 1, the drive returns status as soon as the operation starts.
When set to 0, the drive returns status after the operation has completed.
HoldWhen set to 1, indicates that Enhanced Medium Auxiliary Memory (EMAM) is
accessible upon completion of the command but the medium is not repositioned
for access. When the Hold bit is set to 0 and the Load bit is set to 1, the medium
is positioned for access. When both the Hold and Load bits are set to 0, EMAM
is not accessible upon completion of the command.
EOTEnd of Tape. The drive ignores this bit unless both the EOT and Load bits are set
to 1, then the drive returns CHECK CONDITION status with Sense Key set to
ILLEGAL REQUEST.
ReTenRetension. Ignored. Retension operations are not needed.
LoadIf the Load bit is set to 1 and the medium is already loaded, the drive writes any
cached data to the tape, rewinds the tape, and returns a GOOD status. If the drive
unloaded the medium but the cartridge was not removed, a LOAD UNLOAD
command causes the drive to load the tape to Beginning of Partition (BOP) again
and make it ready for use.
If the Load bit is set to 0 and the medium is loaded, the drive writes any buffered
data and filemarks to the tape, rewinds the tape to BOM, and unloads the
medium back into the cartridge. At that point, the drive ejects the medium if not
in a library. If the drive is in a library, the drive does not eject the medium, but
waits for another command. If the medium is already unloaded, the drive takes
no action. The drive returns a GOOD status.
81-81200-02 REV A01January 20054-29
SDLT 600
SCSI Interface Guide
SCSI Commands
LOCATE Command (2Bh)SDLT 600 SCSI Interface Guide
81-81200-02
REV A01
4.6LOCATE Command (2Bh)
The LOCATE command performs high-speed positioning to a specified block address. Use the READ
POSITION command to obtain the block address associated with the current position on tape. Then
use the LOCATE command to position the tape at the same logical position for high-performance
restore operations of particular blocks of data.
Bit
Byte
0Operation Code (2Bh)
1ReservedBTCPImmed
2Reserved
3 – 6
7Reserved
8Partition
9Control
76543210
(MSB)
Logical Object Identifier
Figure 4-13. LOCATE Command Descriptor Block — Data Format
Table 4-17. LOCATE Command Descriptor Block — Field Descriptions
Field NameDescription
(LSB)
BTBlock Type. The drive ignores this bit.
CPChange Partition. The drive does not support multiple partitions.
Always set to 0.
ImmedImmediate. When set to 1, the drive returns status as soon as the
operation starts. When set to 0, the drive returns status after the
operation has completed.
Logical Object
Identifier
PartitionNot applicable; the drive ignores this bit. See CP field above.
4-30January 200581-81200-02 REV A01
Specifies the Logical Object Identifier to which the drive positions the
medium.
The LOG SELECT command allows the host to manage statistical information the SDLT tape drive
maintains about its own hardware parameters and about the installed tape medium. Read the
description of the “LOG SENSE Command (4Dh)” on page 4-39; it provides information about log
page format, parameters, and supported pages.
Bit
Byte
0Operation Code (4Ch)
1ReservedPCRSP
2PCReserved
3 – 6Reserved
7 – 8
9Control
76543210
(MSB)
Parameter List Length
Figure 4-14. LOG SELECT Command Descriptor Block — Data Format
Table 4-18. LOG SELECT Command Descriptor Block — Field Descriptions
Field NameDescription
PCRParameter Code Reset. If this bit is set to 1 and the Parameter List Length field
is set to 0, all accumulated values of page codes 2, 3, and 32 are set to 0 and all
threshold values are set to default. If PCR is set to 1 and the Parameter List
Length field is set to a non-zero value, the drive terminates the command with
CHECK CONDITION status, Sense Key set to ILLEGAL REQUEST, and
Additional Sense Code (ASC) set to INVALID FIELD IN CDB. (See the Note
under SP [Save Parameters] below.)
SPSave Parameters. When set to 1, indicates that after performing the specified
LOG SELECT operation the drive saves to nonvolatile memory all parameters
identified as saveable by the DS bit in the log page. When set to 0, specifies
that the drive does not save the parameters.
Note: If PCR and SP are both set to 1, the drive terminates the command with
a CHECK CONDITION status, Sense Key set to ILLEGAL REQUEST,
and Additional Sense Code set to INVALID FIELD IN CDB.
PCPage Control. Defines the type of parameter values to be selected:
CodeType of Parameter Value
00bCurrent Threshold Values
01bCurrent Cumulative Values
10bDefault Threshold Values
11bDefault Cumulative Values
When the PC field is set to 10b and the Parameter List Length field is set to 0,
all Current Threshold Values are reset to the Default Threshold Values.
When the PC field is set to 11b and the Parameter List Length field is set to 0,
all Current Cumulative Values are reset to the Default Cumulative Values. This
is equivalent to clearing all log pages that can be cleared.
Note: The drive ignores the PC field value if the PCR bit is set to 1.
Parameter
List Length
Specifies the length, in bytes, of the LOG SELECT parameter list to be
transferred from the initiator to the drive during the DATA OUT phase. A
Parameter List Length of 0 indicates that no data is to be transferred. This
condition is not considered an error.
The following conditions constitute errors that the drive detects in relation to the CDB. The Request
Sense Data is set to Sense Key of ILLEGAL REQUEST, and Additional Sense Code set to INVALID
FIELD IN CDB.
The conditions that constitute errors are:
•PCR bit is set to 1 and Parameter List Length field is not set to 0.
•Both the PCR and SP bits are set to 1.
•A Parameter List Length that would cause a parameter within a valid page to be truncated or
otherwise incompletely initialized.
4.7.2 Operation of LOG SELECT
The LOG SELECT command allows the initiator to modify and initialize parameters within the logs
the drive supports.
The two ways to initialize the log parameters are:
1. Set the PCR bit to 1 in the LOG SELECT CDB; this clears all parameters.
2. Specify the log page and parameter values as the log parameters to clear individual pages. The
following pages can be cleared using this method:
Table 4-19. LOG SELECT Page-clearing Codes
Page CodePage Description
02hWrite Error Count Page
03hRead Error Count Page
32hCompression Ratio Page
If an initiator sends multiple pages during the DATA OUT phase, it must send them in ascending order
according to page code. Otherwise, the drive terminates the command with a CHECK CONDITION
status, Sense Key set to ILLEGAL REQUEST, and Additional Sense Code set to INVALID FIELD IN
PARAMETER LIST. The drive returns the same status if an unsupported page code appears in any
header or if the specified page cannot be cleared.
Each log page begins with a 4-byte header followed by n number of log parameter blocks—one block
for each parameter code. Each block, except for parameter code 05h, comprises 8 bytes. The parameter
block for page code 05h is 12 bytes.
Bit
Byte
0Page Code
1Reserved
2 – 3
4Log Parameter (First)
x + 3Length (x)
n – y + 1Log Parameter (Last)
nLength (y)
76543210
(MSB)
Page Length (n – 3)
Log Parameters
.
.
Figure 4-15. LOG SELECT Log Page — Data Format
(LSB)
Table 4-20. LOG SELECT Log Page Header — Field Descriptions
Field NameDescription
Page CodeSpecifies the log page to which this LOG SELECT command is directed.
Page LengthSpecifies the total number of bytes contained in this log page, not including the
Table 4-21. LOG SELECT Log Parameters — Field Descriptions (Continued)
Field NameDescription
8003hTotal servo tracking errors
9000h-
Without substantial delay errors by channel
9007h
9080h9087h
Write only: Possible delay errors assignable to specific
channels
Read only: Raw sub-block read errors by channel
Note: Many of these errors are write, not read, errors and are
not to be included in read error-rate calculations. If
these errors are used to try to identify bad channels, the
bad channel may be on either the writing or reading
drive.
Note: Parameter codes 00h, 01h, and 04h always have a value of 0.
Parameter value for 05h is eight bytes; the Parameter Length field is
set to 8.
DUDisable Update. This bit is not defined for LOG SELECT; the drive ignores
any value in DU.
DSDisable Save. Not supported. DS and Target Save Disable (TSD) must be set
to 1. If DS or TSD or both are set to 0, the drive terminates the command
with CHECK CONDITION status, Sense Key set to ILLEGAL REQUEST,
and Additional Sense Code set to INVALID FIELD IN PARAMETER
LIST.
TSDTarget Save Disable. Not supported. TSD and DS must be set to 1. If TSD or
DS or both are set to 0, the drive terminates the command with CHECK
CONDITION status, Sense Key set to ILLEGAL REQUEST, and
Additional Sense Code set to INVALID FIELD IN PARAMETER LIST.
ETCEnable Threshold Comparison. When set to 1, the drive performs a
comparison with threshold values once the cumulative value is updated.
Comparison criteria are defined in Threshold Met Criteria (TMC). If the
comparison is met and the RLEC bit of MODE SELECT / SENSE Control
Page 0Ah is set to 1, the drive generates a UNIT ATTENTION for all
initiators. The drive sets the Additional Sense Code to THRESHOLD
CONDITION MET. If the RLEC bit is 0 and the comparison is met, the
drive does not generate a UNIT ATTENTION.
TMCThreshold Met Criteria. Once the criteria specified in this field are met, the
ETC bit is 1, and the RLEC bit in the MODE SENSE / SELECT Control
Page is set to 1, the drive generates a UNIT ATTENTION for all initiators.
The host issues a LOG SENSE command to initialize host-resident software that allows determination
of:
•The log pages the drive uses
•The parameter codes and length of each parameter.
The following conditions constitute errors in the parameter block that cause the drive to return
CHECK CONDITION status with Sense Data set to ILLEGAL REQUEST and Additional Sense Code
set to INVALID FIELD IN PARAMETER LIST:
•The drive receives a page header with unsupported page codes.
•An incorrect log page length is specified in the page header.
•An illegal parameter code is contained in a valid page code.
•Parameter codes for a supported page are not sent in ascending order.
•The LP bit is set to 1 in the parameter control byte.
•The DS bit is set to 0 in the parameter control byte.
•The TSD bit is set to 0 in the parameter control byte.
The LOG SENSE command allows the host to retrieve statistical information the SDLT tape drive
maintains about its own hardware parameters or about the installed tape medium. This command
complements the LOG SELECT command.
Bit
Byte
0 Operation Code (4Dh)
1ReservedPPCSP (0)
2PCPage Code
3 – 4Reserved
5 – 6
7 – 8
9Control
76543210
(MSB)
Parameter Pointer
(MSB)
Allocation Length
Figure 4-17. LOG SENSE Command Descriptor Block — Data Format
(LSB)
(LSB)
81-81200-02 REV A01January 20054-39
LOG SENSE Command (4Dh)SDLT 600 SCSI Interface Guide
Table 4-22. LOG SENSE Command Descriptor Block — Field Descriptions
Field NameDescription
PPCParameter Pointer Control. When set to 0, indicates that the parameter data
requested from the drive 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. When set to 1, the drive returns only the
parameters that have changed since the last time the page was read.
SPSave Parameters. Not supported. Must be set to 0. If the Save Parameters bit is
set to 1, the drive terminates the command with CHECK CONDITION status,
Sense Key set to ILLEGAL REQUEST, and Additional Sense Code set to
INVALID FIELD IN CDB.
PCPage Control. This field defines the type of parameter values to be returned:
CodeType 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 drive by power-cycle, TARGET RESET, or SCSI RESET.
• The Default Cumulative values are the values to which each parameter is
initialized at a reset condition. Default values are 0.
• By default, Current Threshold Values are set to Default Threshold Values.
Page CodeThe Page Code field identifies the log page the initiator requested. If the drive
does not support the specified page, the drive terminates the command with
CHECK CONDITION status, Sense Key set to ILLEGAL REQUEST, and
Additional Sense Code set to INVALID FIELD IN CDB. The drive supports the
following pages:
Table 4-22. LOG SENSE Command Descriptor Block — Field Descriptions (Continued)
Field NameDescription
0ChSequential Access Device Log PagePage 4-49
0DhTemperature Log PagePage 4-51
2EhTapeAlert Log PagePage 4-53
32hRead / Write Compression Ratio Log PagePage 4-57
33hDevice Wellness Log PagePage 4-61
3EhDevice Status Log PagePage 4-64
Parameter
Pointer
Allocation
Length
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, the drive returns
only parameters 3, 4, and 5 to the host. Similarly, if a page supports parameters
1, 3, and 6, and the Parameter Pointer contains 2, the drive returns only
parameters 3 and 6 to the host.
If the Parameter Pointer is larger than the highest numbered parameter on the
page, the drive 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 the drive always returns parameters within a page in ascending order
according to the parameter code.
If the drive does not support a parameter code within a page, it does not return
any data associated with that parameter.
Specifies the maximum number of bytes that the host allocated for returning
data. The host uses this field to limit the size of data transfers to its own internal
buffer size.
4.8.1 Error Summary in LOG SENSE Command Descriptor
Block
The following conditions constitute errors the drive detects relating to the LOG SENSE CDB. The
drive terminates the command with CHECK CONDITION status, Sense Key set to ILLEGAL
REQUEST, and Additional Sense Code set to INVALID FIELD IN CDB.
Error conditions occur when:
•The drive does not support the requested page.
•The parameter pointer is larger than the highest numbered parameter on the page.
•The SP bit is set to 1.
81-81200-02 REV A01January 20054-41
LOG SENSE Command (4Dh)SDLT 600 SCSI Interface Guide
4.8.2 Supported Pages Log Page (Page 00h)
When the host requests Page 00h, the drive returns the 4-byte page header followed by the pages
supported in ascending order, one byte for each.
Bit
Byte
0Page Code (00h)
1Reserved
2 – 3
4Supported Pages Log Page (00h)
5Write Error Log Page (02h)
6Read Error Log Page (03h)
7Last n Error Events Log Page (07h)
8Sequential Access Device Log Page (0Ch)
9Temperature Log Page (0Dh)
10TapeAlert Log Page (2Eh)
11Read / Write Compression Ratio Log Page (32h)
12Device Wellness Log Page (33h)
76543210
(MSB)
Page Length (0Ah)
(LSB)
13Device Status Log Page (3Eh)
Figure 4-18. Supported Pages LOG SENSE Page — Data Format
Table 4-24. Log Parameters for Read / Write Error LOG SENSE Page —
Field Descriptions (Continued)
Field NameDescription
8002hTotal dropout error count
8003hTotal servo tracking errors
9000h-
Without substantial delay errors by channel
9007h
9080h9087h
Write only: Possible delay errors assignable to specific
channels
Read only: Raw sub-block read errors by channel
Note: Many of these errors are write, not read, errors and
are not to be included in read error-rate calculations.
If these errors are used to try to identify bad
channels, the bad channel may be on either the
writing or reading drive.
Note: Parameter codes 00h, 01h, and 04h always return a value of 0.
DUDisable Update. When set to 0, indicates that the drive updates all log
parameter values. When set to 1, indicates that the drive does not update
the log parameter values except in response to a LOG SELECT command.
The drive sets this bit to 1 when accumulated values reach maximum. The
drive also returns this bit set to 1 if the host set the bit in the last LOG
SELECT command. Default is 0.
Note that for parameter types other than threshold and cumulative values,
this bit is always set to 0.
DSDisable Save. Not supported. Always set to 1.
TSDTarget Save Disable. Not supported. Always set to 1.
ETCEnable Threshold Comparison. When set to 1, indicates that the drive
performs comparison to threshold. When set to 0, indicates that the drive
does not perform the comparison. The Control Mode Page of the MODE
SELECT command sets this bit set to 1. Default is 0.
81-81200-02 REV A01January 20054-45
LOG SENSE Command (4Dh)SDLT 600 SCSI Interface Guide
Table 4-24. Log Parameters for Read / Write Error LOG SENSE Page —
Field Descriptions (Continued)
Field NameDescription
TMCThreshold Met Criteria. This field is valid only if the host sets the ETC bit
to 1. This field determines the basis for comparison. The host specifies this
field using the LOG SELECT command. If the result of comparison is true
(cumulative = threshold) and the MODE SELECT / SENSE Control Mode
Page RLEC bit is set to 1, the drive generates a UNIT ATTENTION for all
initiators. In that case, the drive sets the Sense Key to UNIT
ATTENTION, the Additional Sense Code to LOG EXCEPTION, and the
Additional Sense Code Qualifier to THRESHOLD CONDITION MET. If
the RLEC bit in Control Mode Page is 0, the drive does not generate a
UNIT ATTENTION.
Note that comparison is performed in real time. A LOG SENSE command
need not be issued to get the CHECK CONDITION status. Once ETC is
selected and the RLEC bit in Control Mode Page is set to 1, the drive
issues a CHECK CONDITION status based on the criteria defined in the
TMC bits if the criteria is met in real time. The CHECK CONDITION
status does not identify for which parameter code the criterion is met. The
host must issue a LOG SENSE command to read the counters to determine
for which parameter code the criterion has been met.
The criteria for comparison are:
CodeBasis of Comparison
00bEvery update of the cumulative value
01bCumulative value equal to threshold value
10bCumulative value not equal to threshold value
11bCumulative value greater than threshold value
LBINList Binary. Not used.
LPList Parameter. The drive treats the parameter codes as data counters.
Always set to 0.
Parameter LengthSpecifies the number of bytes in the parameter value. All parameters are 4
bytes in length except parameter 0005h, which is 8 bytes in length.
Parameter ValueIndicates the actual value of this log parameter.
This page returns one parameter at a time that contains the ASCII text for the specified event log. The
Parameter Number field in the CDB specifies the log event to return. The log events in EEPROM are
numbered from 0 to 255, after which the number wraps back to 0. A maximum of 32 events are stored
at a given time. The log event returned is the first one whose parameter code is equal to or greater than
the parameter number specified in the CDB.
Bit
Byte
0Page Code (07h)
1Reserved
2 – 3
76543210
(MSB)
Page Length
Figure 4-21. Last n Error Events LOG SENSE Page — Header Format
(LSB)
81-81200-02 REV A01January 20054-47
LOG SENSE Command (4Dh)SDLT 600 SCSI Interface Guide
Table 4-25. Last n Error Events LOG SENSE Header — Field Descriptions
Field NameDescription
Page CodeEchoes the page code specified in the LOG SENSE CDB.
Page LengthSpecifies the total number of bytes contained in this log page, excluding
the 4 bytes that make up the header.
Bit
Byte
76543210
(MSB)
0 – 1
Parameter Code
(LSB)
1
2
DUDSTSDETCTMCLBINLP
3Parameter Length
(MSB)
4 – n
ASCII String for Event n
(LSB)
1.The byte 2 fields are collectively referred to as the Parameter Control Byte. For definitions of the bits that
compose the Control Byte (the byte 2 in the above figure), refer to “Read (Page 03h) / Write (Page 02h) Error
Log Page” on page 4-43.
Figure 4-22. Log Parameters Format for Last n Error Events LOG SENSE Page
Table 4-26. Log Parameters for Last n Error Events LOG SENSE Page — Field Descriptions
Field NameDescription
Parameter CodeParameter Code values are assigned from 0 to 63 (decimal), where 0 is
the oldest event stored and the highest Parameter Code returned is the
most recent event.
ASCII String for
Event n
The text of the parameter includes a “Packet #” that is a value from 0 to
255. The drive assigns this internal number when the packet is written to
EEPROM. A value of 0 is normally the oldest packet, but packet
numbers wrap back to 0 after reaching 255.
This page provides a standardized way to report the device temperature.
Bit
Byte
0Page Code (0Dh)
1Reserved
2 – 3
76543210
(MSB)
Page Length
Figure 4-25. Temperature LOG SENSE Page — Header Format
Table 4-29. Temperature LOG SENSE Header — Field Descriptions
Field NameDescription
Page CodeEchoes the page code specified in the LOG SENSE CDB.
Page LengthSpecifies the number of bytes available and depends on the parameters
requested.
(LSB)
Bit
Byte
0 – 1
2DUDSTSDETCTMCLBINLP
3Parameter Length (02h)
4 – 5
76543210
(MSB)
Parameter Code (Temperature)
(LSB)
(MSB)
Parameter Value
(LSB)
Figure 4-26. Log Parameters Format for Temperature Page
81-81200-02 REV A01January 20054-51
LOG SENSE Command (4Dh)SDLT 600 SCSI Interface Guide
Table 4-30. Temperature LOG SENSE Parameters — Field Descriptions
Field NameDescription
Parameter CodeParameter codes supported for the Temperature page are as follows:
CodeDescription
0000hCurrent operating temperature (degrees Celsius).
0001hReference temperature (degrees Celsius). This is the maximum
reported sensor temperature at which the tape drive is capable of
operating continuously without experiencing degradation beyond
the limits, specified in the Product Manual for this product.
DUDisable Update. Always set to 0.
DSDisable Save. Not supported. Always set to 1.
TSDTarget Save Disable. Not supported. Always set to 0.
ETCEnable Threshold Comparison. Threshold checking is not supported on this page.
Always set to 0.
TMCThreshold Met Criteria. Ignored. Always set to 0.
LBINList Binary. Always set to 1.
LPList Parameter. The drive treats the parameter codes as data counters. Always set
to 1.
Parameter
Length
Specifies the number of bytes in the parameter value. All parameters are 2 bytes in
length.
Parameter ValueIndicates the actual value of this log parameter.
This page returns results of the SDLT tape drive’s ongoing self-diagnosis, so that the drive’s behavior
can be monitored and high reliability assured. The host typically reads the TapeAlert page from the
drive at the beginning of each READ or WRITE activity, after any fatal errors occur during a READ or
WRITE, at the end of any data cartridge when the READ or WRITE activity continues onto another
data cartridge, and at the end of each READ or WRITE activity. The drive sets or clears the flags when
the failure or corrective action occurs.
Bit
Byte
0Page Code (2Eh)
1Reserved
2 – 3
76543210
(MSB)
Page Length
Figure 4-27. TapeAlert LOG SENSE Page — Header Format
Table 4-31. TapeAlert Page LOG SENSE Header — Field Descriptions
Field NameDescription
Page CodeEchoes the page code specified in the LOG SENSE CDB.
Page LengthSpecifies the total number of bytes contained in this log page, excluding the
4 bytes that make up the header.
(LSB)
81-81200-02 REV A01January 20054-53
LOG SENSE Command (4Dh)SDLT 600 SCSI Interface Guide
Bit
Byte
76543210
(MSB)
0 – 1
1
2
DUDSTSDETCTMCLBINLP
Parameter Code
3Parameter Length (1)
4Value of TapeAlert Flag (Flag is set when bit 0 is set to 1; bits 1–7 are reserved)
1.The byte 2 fields are collectively referred to as the Parameter Control Byte.
Figure 4-28. TapeAlert LOG SENSE Page — Parameters Format
Table 4-32. TapeAlert Page LOG SENSE Parameters — Field Descriptions
Field NameDescription
Parameter CodeContains the Flag code. See Table 4-33 on page 4-55 for the
supported flags, level of severity, and the flag definitions.
(LSB)
Parameter LengthAlways set to 1.
Value of TapeAlert FlagIf bit 0 is set to 1, indicates that TapeAlert has sensed a problem. See
Table 4-33 on page 4-55 for the supported flags and their definitions.
If bit 0 is set to 0, indicates that TapeAlert did not sense a problem
and therefore did not set the flag.
WarningThe temperature inside the drive exceeds the allowable
specifications.
Note: The drive issues this warning 3 degrees C
below the maximum temperature threshold so
that you can provide additional cooling before
potential damage occurs.
38 Predictive
Failure
CriticalA hardware failure of the drive is predicted. Call the
tape drive supplier help line to arrange for a
replacement.
51 Tape Directory
Invalid at Unload
1.Severity levels are Informational, Warning, and Critical. Informational flags provide a status-type
message, Warning flags indicate that there is the possibility of loss of data, and Critical flags indicate
the possibility of loss of data and that user intervention, a service call, or both may be required.
WarningA WRITE error prevented the directory from being
This page begins with a 4-byte header followed by the log parameter blocks of 6 or 8 bytes, depending
on the parameter code selected.
Bit
Byte
0Page Code (32h)
1Reserved
2 – 3
76543210
(MSB)
Additional Length
Figure 4-29. Read / Write Compression Ratio LOG SENSE Page — Header Format
Table 4-34. Read / Write Compression Ratio LOG SENSE Header — Field Descriptions
Field NameDescription
Page CodeEchoes the page code specified in the LOG SENSE CDB.
Additional LengthSpecifies the number of bytes available and depends on the parameters
requested.
(LSB)
Bit
Byte
0 –1
2DUDSTSDETCTMCLBINLP
3Parameter Length (02h)
4 – 5
76543210
(MSB)
Parameter Code
(LSB)
(MSB)
Compression Ratio x 100
(LSB)
Figure 4-30. Log Parameters Format for Read / Write Compression Ratio LOG SENSE Page
(Parameter Codes 00h and 01h)
81-81200-02 REV A01January 20054-57
LOG SENSE Command (4Dh)SDLT 600 SCSI Interface Guide
Table 4-35. Log Parameters for Read / Write Compression Ratio LOG SENSE Page — Field
Descriptions (Parameter Codes 00h and 01h)
Field NameDescription
Parameter
Code
DUDisable Update. Always set to 0.
DSDisable Save. Not supported. Always set to 1.
TSDTarget Save Disable. Not supported. Always set to 1.
ETCEnable Threshold Comparison. Not supported. Always set to 0.
TMCThreshold Met Criteria. Always set to 0.
LBINList Binary. Not used.
LPList Parameter. The drive treats the parameter codes as data counters. Always
Parameter codes supported for the Read / Write Compression Ratio Page are
as follows (for codes 00h and 01h only; codes 02h through 09h are detailed
separately):
CodeDescription
00hREAD Compression Ratio x 100
01hWRITE Compression Ratio x 100
set to 0.
Bit
Byte
0 – 1
2DUDSTSDETCTMCLBINLP
3Parameter Length (04h)
4 – 7
76543210
(MSB)
Parameter Code
(LSB)
(MSB)
Counter Value
(LSB)
Figure 4-31. Log Parameters Format for Read / Write Compression Ratio LOG SENSE Page
(Parameter Codes 02h through 09h)
4-58January 200581-81200-02 REV A01
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.