DLT-S4 Interface Reference Guide, 81-81281-04 A01, January 2008, 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, the Quantum logo, DLT, DLTtape, and DLTtape logo are registered trademarks of Quantum
Corporation in the U.S. and other countries. The DLT logo, DLTSage, and StorageCare trademarks of
Quantum Corporation. LTO and Ultrium are trademarks of HP, IBM, and Quantum in the U.S. and other
countries.
All other trademarks are the property of their respective companies.
Contents
Prefacexxviii
Chapter 1Introduction1
Background Information About SCSI............................................................. 1
To comment on existing documentation send e-mail to:
doc-comments@quantum.com
Quantum Home Page0
Visit the Quantum home page at:
www.quantum.com
DLT-S4 Interface Reference Guidexxxii
0
Preface
Getting More Information
or Help
More information about this product is available on the Service and
Support website at www.quantum.com/support
. The Service and
Support Website contains a collection of information, including answers
to frequently asked questions (FAQs). You can also access software,
firmware, and drivers through this site.
For further assistance, or if training is desired, contact Quantum:
QuantumTechnical Assistance Center in the USA: 800-284-5101
For additional contact information: www.quantum.com/support
To open a Service Request: www.quantum.com/esupport
For the most updated information on Quantum Global Services, please
visit: www.quantum.com/support
.
For the most up to date information on Quantum Global Services, please
visit: www.quantum.com/support
.
DLT-S4 Interface Reference Guidexxxiii
Preface
0
DLT-S4 Interface Reference Guidexxxiv
Chapter 1
1Introduction
This chapter covers basic SCSI background information as it relates to
DLT-S4 drive characteristics and interfaces.
Background Information About SCSI1
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. DLT-S4 tape drives
conform to the SCSI-3 standard. You should familiarize yourself with the
standards as previously mentioned in
before using the remaining portions of this document.
Related Documents on page xxxi
Note:Final drafts of the SCSI standards documents are available at
www.t10.org.
The DLT-S4 is capable of supporting these separate transport layers:
•Parallel SCSI
•Fibre Channel
•Serial Attached SCSI (SAS)
DLT-S4 Interface Reference Guide1
Chapter 1 Introduction
Background Information About SCSI
Format of data written to tape:
•Logical addressing (rather than physical addressing) is used for all
data blocks.
•Tape drives support block sizes from 4 bytes to 16,777,212 bytes.
•Fixed block sizes must be in multiple of 4 bytes.
•The DLT-S4 can read DLT-S4, SDLT 600, and SDLT 320 formatted
tapes and can write to DLT-S4 formatted tapes.
Parallel SCSI
Characteristics
The features of the DLT-S4 Parallel SCSI implementation include:
1
•The DLT-S4 tape drive is capable of negotiating and running at any of
the following protocols:
•Single Transition
•Dual Transition
•Information Units (Ultra 320 speeds)
•DLT-S4 tape drives support wide asynchronous and synchronous
data transfers.
•SPI-4 compliant
•Odd parity is generated and checked during all single edge
information transfer phases.
•CRC is generated and checked during all dual edge information
transfer phases.
•The DLT-S4 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 DLT-S4 tape drive does not act as an initiator on the SCSI bus.
Therefore, the drive does not:
1 Generate unsolicited traffic on the network
2 Initiate its own SCSI commands
3 Assert bus reset.
DLT-S4 Interface Reference Guide2
Chapter 1 Introduction
Background Information About SCSI
Fibre Channel
Characteristics
The features of the DLT-S4 Fibre Channel implementation include:
1
•Automatic speed negotiation, with transfer rates of:
•100 megabytes per second (1 Gb/second)
•200 megabytes per second (2 Gb/second)
•400 megabytes per second (4 Gb/second)
•Automatic topology negotiation (the tape drive operates as an
NL_Port or N_Port):
•Arbitrated Loop: private loop, NL_Port to NL_Port(s)
•Arbitrated Loop: public loop, NL_Port to NL_Port(s) and one
FL_Port
•Fabric attachment: N_Port to F_Port
•Point-to-Point attachment: N_Port to N_Port
•FCP-2 compliant
•Class 3 level of service
•Basic and extended link services
•Task retry identification
•Hard assigned port addresses, when attached to a library. The library
can assign a hard address to the tape drive. If the library does not
assign a hard address, the tape drive takes a soft address initially.
•The DLT-S4 tape drive does not act as an initiator on the SCSI bus.
Therefore, the drive does not:
1 Generate unsolicited traffic on the bus
2 Initiate its own SCSI commands
3 Assert bus reset.
World-wide Names1Although, the DLT-S4 tape drive contains one 64-bit world-wide name
for the port and one for the SSC logical unit (LUN-0), the FCP-2 standard
allows for the use of the same world-wide name for the node as is used in
LUN-0. The drive reports the world-wide names to the host through the
INQUIRY Command (12h) on page 34.
DLT-S4 Interface Reference Guide3
Chapter 1 Introduction
Background Information About SCSI
Serial Attached SCSI
Characteristics
The important features of the DLT-S4 SAS implementation include the
following:
1
•Automatic speed negotiations, with transfer rates of:
•150 megabytes per second (1.5 Gb/second)
•300 megabytes per second (3.0 Gb/second).
•SAS-1.1 compliant
•Transport Layer Retries are supported
•The DLT-S4 tape drive is an SSP Target Port
•The DLT-S4 tape drive does not act as an SSP Initiator Port.
DLT-S4 Interface Reference Guide4
Chapter 2
2Task Management
This chapter provides a detailed description of task management by
transport layer. Specifically, it covers the following topics:
•Task Management by Transport Layer Overview
task management functions by interface.
•Task Management Function
each function.
, describes the tape drive response for
, provides a list of
DLT-S4 Interface Reference Guide5
Chapter 2 Task Management
Task Management by Transport Layer Overview
Task Management by Transport Layer Overview2
Table 1 shows the task management function and its specific
characteristics by transport layer.
Table 1 Task Management by
Transport Layer
Task
Management
FunctionFibre Channel
ABORT TASK
ABORT TASK SET
CLEAR TASK SET
LOGICAL UNIT
RESET
TARGET RESET
QUERY TASKN/A
Basic Link Service
BLS ABTS (81h)
Task Mgmt
Flag=02h
Task Mgmt
Flag=04h
Task Mgmt
Flag=10h
Task Mgmt
Flag=20h
Parallel SCSI
Serial Attached
SCSI
Task Mgmt
Flag=01h
Task Mgmt
Flag=02h
Task Mgmt
Flag=04h
Task Mgmt
Flag=08h
N/A
Task Mgmt
Flag=80h
Parallel SCSI
Information Units
Task Mgmt
Flag=01h
or
Message Out=0Dh
Task Mgmt
Flag=02h
Task Mgmt Out=04hMessage Out=0Eh
Task Mgmt Out=08hMessage Out=17h
Task Mgmt
Flag=20h
or
Message Out=0Ch
N/AN/A
Non-Information
Units
Message Out=0Dh
Message Out=06h
Message Out=0Ch
DLT-S4 Interface Reference Guide6
Chapter 2 Task Management
Task Management Function
Task Management Function2
There are three types of Task Management:
•Reset
•TARGET RESET
•LOGICAL UNIT RESET
•Abort
•ABORT TASK SET
•ABORT TASK
•CLEAR TASK SET
•Query
•QUERY TASK
TARGET RESET 2 An initiator sends the TARGET RESET request to direct the tape drive to
clear all I/O processes. This task management function causes the drive
to:
1 Abort all the commands in the task set without sending status and
flush all of the complete blocks in the cache to tape.
2 Execute a soft reset.
The drive creates a Unit Attention condition for all initiators after
accepting and processing a
code is set to
If a
WRITE command is in progress and STATUS has not been sent to the
TARGET RESET OCCURRED.
TARGET RESET request. The additional sense
initiator when the drive receives this message, the drive may write some
or all of the data for the
WRITE command to the medium.
LOGICAL UNIT RESET2 This task management function causes the drive to reset the selected unit.
When the LUN is set to 0 and the drive receives the
LOGICAL UNIT RESET
task management function, the drive is reset as described in TARGET
RESET
above.
DLT-S4 Interface Reference Guide7
Chapter 2 Task Management
Task Management Function
CLEAR TASK SET2 CLEAR TASK SET clears all commands for requesting initiator. CLEAR
TASK SET
can clear multiple commands, when command queuing is in
effect.
ABORT TASK 2 This task management function causes the drive to clear the current I/O
process on the selected unit. Buffered (cached) write operations are
completed if possible. The current settings of
MODE SELECT parameters
and reservations are not affected. Commands, data, and status for other
initiators are not affected.
This task management function can be sent to a logical unit that is not
currently performing an operation for the initiator.
If a
WRITE command is in progress and STATUS has not been sent to the
initiator when the drive receives this task management function, some or
all of the data for this command may be written to the medium.
ABORT TASK SET2 ABORT TASK SET aborts all commands for the requesting initiator.
ABORT TASK SET can clear multiple commands, when command queuing
is in effect.
QUERY TASK 2 Supported in the SAS protocol only. It is used as part of the protocol error
recovery process to determine if a command was received by the drive or
was discarded due to an error detected at the protocol layer.
DLT-S4 Interface Reference Guide8
Chapter 3
3Transport Layer
Implementation Details
This chapter explains information specific to the Parallel SCSI, Fibre
Channel, and SAS interfaces for the DLT-S4 tape drive on the transport
layer.
DLT-S4 Interface Reference Guide9
Chapter 3 Transport Layer Implementation Details
Parallel SCSI
Parallel SCSI3
This section contains descriptions of each of the messages the drive
supports.
Parallel SCSI message-level errors are communicated by messages that
are defined specifically for that purpose (for example,
ERROR
drive-managed retries (see Supported Messages
detailed message-handling information).
SCSI Bus Reset Condition 3 The DLT-S4 tape drive responds to bus reset conditions as follows:
•Within 250 milliseconds—and typically under 4 milliseconds—after a
or MESSAGE REJECT). Message-level errors are also handled by
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.
MESSAGE PARITY
on page 11 for more
•The drive rewinds the tape to Beginning of Partition 0.
Note:The DLT-S4 tape drive does not implement the hard reset
alternative for bus
The DLT-S4 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.
RESET processing.
DLT-S4 Interface Reference Guide10
Chapter 3 Transport Layer Implementation Details
Parallel SCSI
Supported Messages 3 The tape drive supports the messages and the direction of the message
flow as listed in table 2
and table 3.
Table 2 Supported Message In
List
Message In
Disconnect (04h)
Identify (80h+)
Ignore Wide Residue (23h)
Message Reject (07h)
Modify Data Pointers (1,5,0)
Parallel Protocol Request (1,6,4)
QAS Request (55h)
Restore Pointers (03h)
Save Pointers (02h)
Simple Queue (20h,Tag)
NonInformation
Units
Information
Units
D
D
D
DD
D
D
D
D
D
D
Synchronous Transfer Req (1,3,1)
Task Complete (00h)
Wide Transfer Request (1,2,3)
DLT-S4 Interface Reference Guide11
DD
D
DD
Chapter 3 Transport Layer Implementation Details
Parallel SCSI
Table 3 Supported Message
Out List
Message Out
Abort Task (0Dh)
see ABORT TASK
Abort Task Set (06h)
see ABORT TASK SET on page 8
Clear Task Set (0Eh)
see CLEAR TASK SET on page 8
Logical Unit Reset (17h)
see LOGICAL UNIT RESET on page 7
Target Reset (0Ch)
see TARGET RESET on page 7
Identify (80h+)
Initiator Detected Error (05h)
Message Parity Error (09h)
Message Reject (07h)
on page 8
NonInformation
Units
Information
Units
DD
D
D
D
DD
D
DD
DD
DD
No Operation (08h)
Parallel Protocol Request (1,6,4)
Synchronous Transfer Req (1,3,1)
Simple Queue (20h,Tag)
Wide Transfer Request (1,2,3)
DLT-S4 Interface Reference Guide12
DD
DD
DD
D
DD
Chapter 3 Transport Layer Implementation Details
Parallel SCSI
Supported Task
Management for
Information Units
Synchronous Data Transfer
Request
Figure 1 Synchronous Data
Transfer Request Message —
Data Format
For more in information about supported task management for
information units (see chapter 2,
Task Management).
3
This extended message allows the tape drive and initiator to agree on the
values of the parameters relevant to synchronous transfers. The
3
SYNCHRONOUS DATA TRANSFER REQUEST message has the format
shown in figure 1
Note:The ANSI SPI-4 standard prohibits target devices from
initiating negotiations using the
REQUEST
using the
SYNCHRONOUS DATA TRANSFER REQUEST messages. The
DLT-S4 tape drive initiates negotiations starting with a
DATA TRANSFER REQUEST
data if transfer parameters have not been established or have
been lost (see SPI-4.
.
PARALLEL PROTOCOL
message. Instead, targets are required to negotiate
WIDE DATA TRANSFER REQUEST and
message before transferring any
WIDE
Bit
Byte
0Extended Message Identifier (01h)
1Length (03h)
2SYNCHRONOUS DATA TRANSFER REQUEST (01h)
3Transfer Period
4Transfer REQ/ACK Offset
76543210
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:
DLT-S4 Interface Reference Guide13
Chapter 3 Transport Layer Implementation Details
Parallel SCSI
•After any SCSI reset condition
•After a
TARGET RESET message
•After a power cycle
•After a
The
SYNCHRONOUS DATA TRANSFER REQUEST message exchange
WIDE DATA TRANSFER REQUEST message exchange.
establishes an agreement between two SCSI devices on the clocking of the
data used for
to the
DATA IN and DATA OUT phases only. All other information transfer
DATA phase transfer between them. This agreement applies
phases must use asynchronous transfers.
The 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
DATA TRANSFER REQUEST
message.
WIDE
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 (see table 4
).
Table 4 Transfer Periods and
Transfer Rates
DLT-S4 Interface Reference Guide14
Transfer PeriodTransfer Rate
0Ah40 MHz, 25 nsec Transfer Period
0Bh33 MHz, 30.3 nsec Transfer Period; Ultra 2 Super
DLTtape uses 37.5 nsec period
0Ch20 MHz, 50 nsec Transfer Period
0Dh – 5Dh(4 * Transfer Period) nsec
Chapter 3 Transport Layer Implementation Details
Parallel SCSI
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.
Parallel Protocol Request 3 Parallel Protocol Request (PPR) messages (as shown in figure 2) are used to
negotiate synchronous transfer agreements and wide data transfer
agreements, and to set the protocol options between two SCSI devices.
Figure 2 Parallel Protocol
Request Message — Data
Format
Bit
Byte
0Extended Message Identifier (01h)
1Extended Message Length (06h)
2Parallel Protocol Request (04h)
3Transfer Period Factor
4Reserved
5REQ/ACK Offset
6Transfer Width Exponent
7ReservedDT_REQReserved
76543210
The PPR message is required to configure an DLT-S4 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 DLT-S4 tape drive with
DLT-S4 Interface Reference Guide15
Chapter 3 Transport Layer Implementation Details
Parallel SCSI
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 DLT-S4 tape drive responds to a
PPR message with a reciprocal PPR message containing acceptable
parameters for the interface. An DLT-S4 tape drive never initiates a PPR
negotiation.
Figure 3 Features of the
Parallel Protocol Request
Message
Details about how to configure the PPR message are shown in figure 3
Field Description
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 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, 40 MHz DT (Ultra160)
08h = 6.25 nsec transfer period, 80 MHz DT (Ultra320)
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
.
DLT-S4 Interface Reference Guide16
Chapter 3 Transport Layer Implementation Details
Wide Data Transfer Request3Figure 4 illustrates the message formats.
Figure 4 Wide Data Transfer
Request Message — Data
Format
Parallel SCSI
Bit
Byte
0Extended Message Identifier (01h)
1Length (02h)
2WIDE DATA TRANSFER REQUEST (03h)
3Transfer Width Exponent
76543210
The DLT-S4 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 IN and DATA OUT phases only. All other information transfer phases
DATA phase transfer between them. This agreement applies to
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
DATA TRANSFER REQUEST
message.
The transfer width established applies to all logical units. Valid transfer
widths for the tape drive are 8 bits (transfer width = 00h) and 16 bits
(transfer width = 01h). Other transfer widths are reserved.
WIDE
DLT-S4 Interface Reference Guide17
Chapter 3 Transport Layer Implementation Details
Fibre Channel
Fibre Channel3
For more in information about fibre channel task management, (see
chapter 2,
Task Management).
Link Service and
Unsolicited Control
Support
Basic Link Service3 Table 5 lists the Basic Link Service requests the drive supports (see the FC-
Table 5 Supported Basic Link
Service Commands
DLT-S4 tape drives provide Link Service and Unsolicited Control support
as described in this section.
3
FS-2 specification for details).
R_CTLAbbreviationDescription
80h
81h
84h
85h
NOPNo Operation
ABTSAbort Sequence
BA_ACCBasic Accept
BA_RJTBasic Reject
DLT-S4 Interface Reference Guide18
Chapter 3 Transport Layer Implementation Details
Fibre Channel
Extended Link Service
Commands
Table 6 Supported Extended
Link Service Commands
Table 6 lists the Extended Link Service (ELS) commands the drive supports
(see the FC-FS-2 specification for details).
3
ELS CommandAbbreviationDescription
01h
02h
03h
04h
05h
0Eh
11h
12h
13h
20h
21h
LS_RJTLink Service Reject
LS_ACCLink Service Accept
PLOGIN_Port Login
FLOGIF_Port Login
LOGOLogout
RTVRead Timeout Value
TESTTest (Loop Initialization)
RRQReinstate Recovery Qualifier
RECRead Exchange Concise
PRLIProcess Login
PRLOProcess Logout
PDISCDiscover N_Port Service Parameters
ADISCDiscover Address
RPSRead Port Status Block
RPLRead Port List
FANFabric Address Notification
RNIDRequest Node Identification Data
Extended Link Service
Loop Initialization
50h
52h
56h
57h
60h
78h
Table 7 lists the ELS Loop Initialization commands the drive supports. The
drive is capable of being a loop initialization master (see the FC-AL-2
3
specification).
DLT-S4 Interface Reference Guide19
Chapter 3 Transport Layer Implementation Details
Fibre Channel
Table 7 Supported Extended
Link Service Loop Initialization
Commands
Table 8 lists the FC-4 Link Service commands the drive supports (see the
FC-FS and FCP-2 specifications).
3
FC-4 CommandAbbreviationDescription
13h
14h
Unsolicited Control /
Name Server Requests
Table 9 Supported Name
Server Requests
Table 9 lists the Name Server Requests the drive supports (see the FC-GS).
3
Name Server RequestAbbreviationDescription
0217h
021Fh
DLT-S4 Interface Reference Guide20
RECRead Exchange Concise
SRRSequence Retransmission Request
RFT_IDRegister FC-4 Types
RFF_IDRegister FC-4 Features – Port
Identifier
Chapter 3 Transport Layer Implementation Details
Serial Attached SCSI (SAS)
Serial Attached SCSI (SAS)3
For more in information about SAS task management, (see chapter 2,
Task Management).
Transport Layer Retries3 DLT-S4 tape drives support Transport Layer Retries as indicated in the
MODE SENSE Logical Unit Control Page. It is not possible to turn off
support of Transport Layer Retries.
This section describes implementation specific details of the Transport
Layer retires for DLT-S4 tape drive.
Data In Information Unit
Retries
Transfer Ready
Information Unit Retries
Response Information
Unit Retries
When the SDLT-S4 detects that the host did not successfully receive the
Data In IU, it will resend the Data In IU. The retransmitted Data In IU will
3
have the following new information in the SSP Frame Header:
•The Changing Data Pointer bit is set to 1
•The Target Port Transfer Tag is set to a new value
The SDLT-S4 will attempt to retransmit the Data In IU up to two times.
When the SDLT-S4 detects that the host did not successfully receive the
Transfer Ready IU, it will resend the Transfer Ready IU. The
3
retransmitted Transfer Ready IU will have the following new information
in the SSP Frame Header:
•The Retransmit Bit is set to 1
•The Target Port Transfer Tag is set to a new value
The SDLT-S4 will attempt to retransmit the Transfer Ready IU up to two
times.
When the SDLT-S4 detects that the host did not successfully receive the
Response IU, it will resend the Response IU. The retransmitted Response
3
IU will have the following new information in the SSP Frame Header:
•The Retransmit Bit is set to 1
The SDLT-S4 will attempt to retransmit the Response IU up to two times.
DLT-S4 Interface Reference Guide21
Chapter 4
4SCSI Commands
This chapter describes the supported SCSI commands, options, and error
recovery procedures implemented in the DLT-S4 tape drive. This chapter
does not fully reiterate the entire ANSI SCSI standards; for information of
this nature, refer to the SCSI standards itself.
The Web sites
information.
www.scsita.org and www.t10.org are also helpful sources of
DLT-S4 Interface Reference Guide22
Chapter 4 SCSI Commands
Overview of SCSI Command and Status Processing
Overview of SCSI Command and Status Processing4
The DLT-S4 tape drive supports the SCSI-3 command set and the SCSI
commands listed in table 10
.
Table 10 SCSI Commands
Supported by DLT-S4 Tape
Drives
Operation
Command
ERASE19hpage 33
INQUIRY12hpage 34
LOAD UNLOAD1Bhpage 54
LOCATE2Bhpage 56
LOG SELECT4Chpage 57
LOG SENSE4Dhpage 66
MODE SELECT (6) / (10)15h / 55hpage 98
MODE SENSE (6) / (10)1Ah / 5Ahpage 157
PERSISTENT RESERVE IN5Ehpage 209
PERSISTENT RESERVE OUT5Fhpage 219
PREVENT / ALLOW MEDIUM REMOVAL1Ehpage 231
READ08hpage 232
READ ATTRIBUTE8Chpage 235
READ BLOCK LIMITS05hpage 261
READ BUFFER3Chpage 263
READ POSITION34hpage 269
RECEIVE DIAGNOSTIC RESULTS1Chpage 275
RELEASE (10)57hpage 277
RELEASE UNIT17hpage 279
REPORT DENSITY SUPPORT44hpage 281
REPORT DEVICE IDENTIFIER
REPORT LUNSA0hpage 291
REPORT SUPPORTED OPERATION
CODES
CodeSee
1
1
page 288
page 294
A3h, SA= 05h
A3h, SA= 0Ch
DLT-S4 Interface Reference Guide23
Chapter 4 SCSI Commands
Overview of SCSI Command and Status Processing
Operation
Command
REPORT SUPPORTED TASK
MANAGEMENT OPERATIONS
REPORT TIMESTAMP
REQUEST SENSE03hpage 304
RESERVE (10)56hpage 317
RESERVE UNIT16hpage 319
REWIND01hpage 321
SEND DIAGNOSTIC1Dhpage 322
SET DEVICE IDENTIFIER
SET TIMESTAMP
SPACE11hpage 330
TEST UNIT READY00hpage 332
VERIFY13hpage 333
WRITE0Ahpage 334
WRITE ATTRIBUTE8Dhpage 336
WRITE BUFFER3Bhpage 340
WRITE FILEMARKS10hpage 343
1. SA = Service Action
CodeSee
1
1
1
1
page 300
page 302
page 326
page 328
A3h, SA= 0Dh
A3h, SA= 0Fh
A4h, SA= 06h
A4h, SA= 0Fh
Status and Error
Reporting
SCSI command-level errors are communicated by a status code that the
drive returns during
4
STATUS. This occurs at the end of each command
unless one of the following events terminates the command:
•
ABORT TASK, ABORT TASK SET, or CLEAR TASK SET task
management function is processed so that it affects the command.
•
TARGET RESET or LOGICAL UNIT RESET task management function
is processed.
•Reset condition
•Unexpected disconnect (Parallel SCSI only).
Table 11
DLT-S4 Interface Reference Guide24
describes the status codes the drive returns.
Chapter 4 SCSI Commands
Overview of SCSI Command and Status Processing
Table 11 Status Codes
Autosense4
Status CodeDefinitionMeaning
00hGOODThe drive successfully completed the
command.
02hCHECK
CONDITION
08hBUSYThe drive cannot currently service the
18hRESERVATION
CONFLICT
28hTASK SET FULLThe drive does not have the resources
An exception condition occurred.
command and has discarded the CDB.
The initiator may retry the command
later.
The drive cannot process the command
because another initiator has
established a reservation and the
command is subject to reservations.
to presently accept the command. The
initiator should retry the command at
another time, preferably after status is
received for a currently outstanding
command to the drive.
Autosense is the automatic return of sense data to the application client
coincident with the completion of a SCSI command ending in
CONDITION
.
CHECK
Note:
While Fibre Channel and Serial Attached SCSI always support
Autosense, Parallel SCSI only supports Autosense when
running in Information Unit Mode.
When a command ends with a
describes the reason for the
CHECK CONDITION, sense data (that
CHECK CONDITION) is generated. If the
interface supports autosense, then the drive automatically returns the
sense data with the status for the command that ended with a
CONDITION
issues a
. If the interface does not support autosense, then the host
REQUEST SENSE command to find out what the sense data is.
CHECK
The sense data that is returned automatically, would still have the same
format as the sense data that is returned by the
REQUEST SENSE
command.
DLT-S4 Interface Reference Guide25
Chapter 4 SCSI Commands
Overview of SCSI Command and Status Processing
Unit Attention Condition4 Queued Unit Attentions are implemented on the DLT-S4 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.
•When the medium may have changed asynchronously.
•When another initiator changes the
Mode parameters.
•When a firmware (microcode) update has completed.
•Following a
TARGET RESET or LOGICAL UNIT RESET task
management function.
•For Parallel SCSI Only — Change of SCSI bus transceivers (SE or
LVD).
•For Parallel SCSI Only — SCSI Bus Reset
•For Fibre Channel Only — Port logout or implicit logout.
•For Serial Attached SCSI only — Link reset sequence with hard reset.
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.
Data In/Out Command
Components
Many of the SCSI commands cause data to be transferred between the
initiator and the tape drive. The content and characteristics of this data
4
are command-dependent. Table 13
lists the information transmitted with
each of the commands.
The drive uses the “Length in CDB” column of table 13
much command-related data are to be transferred. Table 12
to determine how
lists how the
units (bytes or logical blocks) for the different Length fields are implied
by the Length field name as follows:
Table 12 Units for Lengths
Fields
DLT-S4 Interface Reference Guide26
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.
Chapter 4 SCSI Commands
Overview of SCSI Command and Status Processing
The Data Out column in table 13 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 parentheses after
an item indicate the item’s length in bytes. In some cases, additional
length information is communicated during DATA.
Table 13 Command Contents
CommandLength in CDBData Out (to drive)Data In (from drive)
ERASE0------
INQUIRYAllocation---Standard Inquiry or a Vital
Product Data page
LOAD UNLOAD0------
LOCATE0------
LOG SELECTParameter ListWrite Error Count
Page, Read Error
Count Page, and
Compression Ratio
Page
LOG SENSEAllocation---Log Page
MODE
SELECT (6) / (10)
MODE
SENSE (6) / (10)
PERSISTENT RESERVE INAllocation---Parameter Data
PERSISTENT RESERVE
OUT
PREVENT ALLOW MEDIUM
REMOVAL
READTransfer---Data
READ BLOCK LIMITS0---Block Length Limits
READ BUFFERAllocation---Buffer Offset and Allocation
READ POSITIONDetermined by
Parameter ListMode Parameter
Header (4) Block
Descriptor (8) Page(s)
Allocation---Mode Parameter Header (4)
Parameter LengthParameter List ---
0------
---Position Identifier or
Long Bit
---
---
Block Descriptor (8) Page(s)
Length and/ or Test Data
SCSI Logical Address
DLT-S4 Interface Reference Guide27
Chapter 4 SCSI Commands
Overview of SCSI Command and Status Processing
CommandLength in CDBData Out (to drive)Data In (from drive)
RECEIVE DIAGNOSTIC
RESULTS
REPORT DENSITY
SUPPORT
REPORT DEVICE
IDENTIFIER
REPORT LUNSAllocation ---Supported LUNs List
REPORT SUPPORTED
OPERATION CODES
REPORT SUPPORTED TASK
MANAGEMENT FUNCTIONS
REPORT TIMESTAMPAllocation ------
REQUEST SENSEAllocation---Sense Data
REWIND0------
SEND DIAGNOSTICParameter ListDiagnostic Page---
SET DEVICE IDENTIFIERParameter ListDevice ID---
SET TIMESTAMPParameter ListTimestamp ---
SPACE0------
TEST UNIT READY0------
VERIFY0------
WRITETransferData---
WRITE BUFFERParameter ListMicrocode Image Data
WRITE FILEMARKS---------
Allocation---Diagnostic Page
Allocation---Density Support Header (4),
Density Support Descriptors
Allocation---Device Identification Information
Allocation ---Depends on Parameter Value
Allocation ---List of the Various Task
Management Functions
(Supported, Unsupported)
---
or Test Data
DLT-S4 Interface Reference Guide28
Chapter 4 SCSI Commands
Overview of SCSI Command and Status Processing
Behavior at Power-On4 Depending on the interface, the DLT-S4 tape drive’s behavior at power-
on consists of the following:
•Parallel SCSI
•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.
•Following power-on self test (POST) and self initialization, the
tape drive responds to SCSI bus selections and returns
appropriate, normal responses. The drive responds to tape
motion commands with
to
NOT READY, until the tape medium is ready.
CHECK CONDITION status, Sense Key set
•The drive rewinds the tape to Beginning of Tape (BOT).
•The drive goes through a calibration process at power-on and
loading of media.
•Fibre Channel
•Transceivers are turned on and auto speed negotiation occurs
unless a speed jumper on the rear panel of the drive is set, in
which case the drive operates at the selected speed.
•Topology is initialized (loop, point-to-point, or fabric).
•In point-to-point mode, the drive is ready to send a FLOGI to
determine if there is a fabric present.
•In public loop mode, the drive is ready to log into the fabric.
•In private loop mode, the drive is ready to accept a login request
from a host.
•The drive rewinds the tape to Beginning of Tape (BOT).
•The drive goes through a calibration process at power-on and
loading of media.
•Following power-on self test (POST) and self initialization, the
tape drive is ready to respond to interface traffic. The drive
responds to tape motion commands with
CHECK CONDITION
status, Sense Key set to NOT READY, until the tape medium is
ready.
DLT-S4 Interface Reference Guide29
Chapter 4 SCSI Commands
Overview of SCSI Command and Status Processing
•Serial Attached SCSI
•Transceivers are turned on, auto speed negotiation occurs, and
the link reset sequence is initiated.
•The drive rewinds the tape to Beginning of Tape (BOT).
•The drives goes through a calibration process at power-on and
loading of media.
•Following power-on self test (POST) and self initialization, the
tape drive is ready to respond to interface traffic. The drive
responds to tape motion commands with
status, Sense Key set to
NOT READY, until the tape medium is
CHECK CONDITION
ready.
Data Cache and Tape
Write Interaction
The DLT-S4 tape drive contains a data cache that buffers blocks and
filemarks until it writes them to tape. This section describes what
4
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 message to the
host.
Note:Unbuffered mode is NOT recommended due to the poor
performance that may result.
The DLT-S4 tape 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.
DLT-S4 Interface Reference Guide30
Chapter 4 SCSI Commands
SCSI Command Descriptions
SCSI Command Descriptions4
The SCSI command descriptions that make up the rest of this chapter
contain detailed information about each command the DLT-S4 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 14
.
Table 14 Fields Common to
Many SCSI Commands
Bit
Byte
76543210
(MSB)
7—8
Field NameHow the Field is Supported in SCSI Commands
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:
(Bytes 0 — 6)
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.
DLT-S4 Interface Reference Guide31
Chapter 4 SCSI Commands
SCSI Command Descriptions
This is an alternate, “shorthand” presentation for:
Byte
7
8
Bit
76543210
(Bytes 0 — 6)
(MSB)
Parameter List Length
(LSB)
DLT-S4 Interface Reference Guide32
Chapter 4 SCSI Commands
ERASE Command (19h)
ERASE Command (19h)4
The ERASE command erases the data on the tape medium. The 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 tape cartridge is more
than 3 hours.
Figure 5 ERASE Command
Descriptor Block — Data
Format
Bit
Byte
0Operation Code (19h)
1ReservedImmedLong
2 — 4Reserved
5Control
Table 15 ERASE Command
Descriptor Block — Field
Descriptions
76543210
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.
DLT-S4 Interface Reference Guide33
Chapter 4 SCSI Commands
INQUIRY Command (12h)
INQUIRY Command (12h)4
The INQUIRY command allows the initiator to direct all attached devices
to return information about themselves. DLT-S4 devices respond by
providing a variety of information, including their World Wide Name
and other important characteristics. The DLT-S4 tape drive identifies
itself as a Sequential Access Storage Device.
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
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 supported Vital Product Data pages (see
Supported Vital Product Data Page (00h)
An
INQUIRY command is neither affected by—nor does it clear—any Unit
Attention
Figure 6 INQUIRY Command
Descriptor Block — Data
Format
Bit
Byte
0Operation Code (12h)
1ReservedObsoleteEVPD
76543210
condition.
on page 41).
2Page Code
(MSB)
3 — 4
5Control
DLT-S4 Interface Reference Guide34
Allocation Length
(LSB)
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Table 16 INQUIRY Command
Descriptor Block — Field
Descriptions
Standard Inquiry Data
Page
Figure 7 Standard Inquiry Data
Page —Data Format
Bit
76543210
Byte
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 9
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. The drive does
not return Error status if the value in this field truncates
the requested information.
Figure 7 shows the Standard Inquiry Data page format.
4
shows the Page
0Peripheral QualifierPeripheral Device Type
1RMBReserved
2Version
3ObsoleteNormACAHiSupResponse Data Format
4Additional Length
5SCCSACCALUA3PCReserved
6BQueEncServVSMultiPMChngrObsoleteAddr16
7RelAdrObsoleteWbus16SyncLinkedObsoleteCmdQueVS
(MSB)
8 — 15
DLT-S4 Interface Reference Guide35
Vendor Identification (QUANTUM)
(LSB)
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Bit
Byte
16 — 31
32 — 35
36 — 55
56ReservedClockingQASIUS
57Reserved
58 — 59
(n — 1) — nVersion Descriptor (last version descriptor, if more than one)
76543210
(MSB)
Product Identification
(MSB)
Product Revision Level (hhss)
(MSB)
Vendor-Specific Bytes
(MSB)
Version Descriptor (first version descriptor)
Table 17 contains field descriptions for the data the DLT-S4 tape drive
returns.
(LSB)
(LSB)
(LSB)
(LSB)
Table 17 Standard INQUIRY
Data Page — Field
Descriptions
FieldValueDescription
Peripheral
Qualifier
000b or 011bThis 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 Type
01 or 1FhThis field contains 01h if the LUN is 0h or 1Fh if no device is
attached to the selected LUN.
RMB1Removable Medium Bit.
Version04hThe drive supports ANSI SCSI-3 per SPC-2.
NormACA0Normal ACA.
HiSup1Hierarchical Support.
DLT-S4 Interface Reference Guide36
FieldValueDescription
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Response
Data Format
Additional
Length
2This Standard Inquiry Data is in the format described in the
Version field.
---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
Response Data.
SCCS0SCC Supported.
ACC0Access Controls Coordinator.
ALUA00bAsymmetric Logical Unit Access.
3PC0Third-party Copy.
BQue0Basic Tagged Command Queuing.
EncServ0Enclosure Services.
VS0Vendor-Specific.
MultiP0Multi Port.
Addr16See table 18
.16-Bit Addressing.
MChnger0Medium Changer.
RelAdr0Relative Addressing.
WBus16See table 18
.Wide Bus 16.
INQUIRY
SyncSee table 18
.Synchronous Data Transfer.
Linked0Linked Command Support.
CmdQueSee table 18
Vendor
QUANTUMThe value in this field is left-aligned and set to “QUANTUM”.
Identification
Product
DLT-S4For the DLT-S4 tape drive, this field is set to “DLT-S4”, left-
Identification
Product
---Contains 4 bytes of ASCII data that provide the drive’s firmware
Revision
.Tagged Command Queuing.
The remainder of the field is filled with space characters.
aligned, filled with spaces to the end of the field.
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
tape drive, the second two bytes of the revision level change to
reflect that update.
DLT-S4 Interface Reference Guide37
FieldValueDescription
ClockingSee table 18.Clocking.
Chapter 4 SCSI Commands
INQUIRY Command (12h)
QASSee table 18
IUSSee table 18
Version
Descriptors
Version descriptors
my vary by protocol
(Parallel SCSI, Fibre
Channel, and SAS)
Table 18 INQUIRY Command
Variance by Protocol
.Quick Arbitrate Supported.
.Information Units Supported.
Identifies the industry standards to which the drive conforms.
Note:As many version descriptors as apply for the drive are
returned.
FieldParallel SCSIFibre ChannelSAS
Addr16100
Wbus16100
Sync100
CmdQue 101
Clocking11b00b00b
QAS100
IUS100
DLT-S4 Interface Reference Guide38
Figure 8 Vendor-Specific
Inquiry Data Field — Data
Format
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Vendor-Specific Inquiry Data Field4
Figure 8 identifies the revision of tape drive subsystem components.
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
49Media Loader Mechanical Version Number
76543210
50Media Loader Present Flag
51Library Present Flag
52 — 55Module Revision
Note:
See Subsystem Components Revision Page (C1h) on page 52for
information about an alternate method for accessing these same
drive subsystem components.
DLT-S4 Interface Reference Guide39
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Table 19 Vendor-Specific
Inquiry Data Page — Field
Descriptions
FieldDescription
Product FamilyIndicates the data density of the tape drive. This field is set to a value of Dh
for the DLT-S4.
Released FirmwareDifferentiates between released and test versions of firmware. The Released
Firmware field combined with the Minor Version field, can be used to
determine the Code Version. Released customer code has no minor
firmware version number (byte 38 is set to 0). The following shows how to
determine the Code Version based on the Minor Version and the Released
Firmware Fields:
Code
Version
Released
Firmware
Minor
Version
V code10
T code1Non-zero
X code0any
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 Set to zero to indicate there is no attached medium changer present.
Library Present FlagSet to 0 to indicate the drive has not detected the presence of a library
controller. Set to a non-zero value when communications has been
established with a tape automation system.
Module RevisionA 4-byte ASCII string representing the revision level of the tape drive’s
module (the controller PCBA attached to the drive).
DLT-S4 Interface Reference Guide40
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Vital Product Data Pages4 The following subsections describe the Vital Product Data Pages for the
DLT-S4 tape drive.
Supported Vital Product Data Page (00h)4
The Supported Vital Product Data Page provides a directory of the Vital
Product Data pages that the drive supports. The supported pages are:
•Supported Vital Product Data Page (00h)
•Unit Serial Number Page (80h)
•Device Identification Page (83h)
•Sequential-Access Device Capabilities Page (B0h)
•Manufacturer-assigned Serial Number Page (B1h)
•Firmware Build Information Page (C0h)
•Subsystem Components Revision Page (C1h).
Figure 9 Supported Vital
Product Data Pages — Data
Format
Bit
Byte
0Peripheral QualifierPeripheral Device Type
1Page Code (00h)
2Reserved
3Page Length (07h)
4Supported Vital Product Data Page (00h)
5Unit Serial Number Page (80h)
6Device Identification Page (83h)
7Sequential-Access Device Capabilities Page (B0h)
8Manufacturer-assigned Serial Number Page (B1h)
9Firmware Build Information Page (C0h – Vendor Specific)
Figure 10 shows the format of the Unit Serial Number Page the drive
returns.
Figure 10 Unit Serial Number
Page — Data Format
Bit
76543210
Byte
0Peripheral Qualifier (0)Peripheral Device Type (01h)
1Page Code (80h)
2Reserved
3Page Length (10h)
Chapter 4 SCSI Commands
INQUIRY Command (12h)
4 — 19Serial Number
Table 20 Unit Serial Number
Page — Field Descriptions
FieldDescription
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.
DLT-S4 Interface Reference Guide42
Figure 11 Device Identification
Page — Data Format
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Device Identification Page (83h)4
Figure 11 shows the format of the Device Identification Page the drive
returns.
Bit
Byte
0Peripheral Qualifier (0)Peripheral Device Type (01h)
1Page Code (83h)
2Reserved
3Page Length
4 — nIdentification Descriptors
Table 21 Device Identification
Page — Field Descriptions
76543210
FieldDescription
Peripheral QualifierContains 000b.
Peripheral Device TypeContains 01h.
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:
• Vendor-Unique Logical Unit Identifier
• Logical Unit NAA Identifier
• Port NAA Identifier
• Relative Target Port Identifier
DLT-S4 Interface Reference Guide43
Figure 12 Vendor-Unique
Logical Unit Identifier — Data
Format
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Vendor-Unique Logical Unit Identifier4
Figure 12 shows the format of the Vendor-Unique Logical Unit Identifier.
Bit
Byte
0Protocol Identifier (0)Code Set (2h)
1PIV (0)ReservedAssociation (0)Identifier Type (1)
2Reserved
3Identifier Length (40)
4 — 11
12 — 27
28 — 43
76543210
(MSB)
Vendor Identification
(MSB)
Product Identification
(MSB)
Serial Number
WORM
(LSB)
(LSB)
(LSB)
DLT-S4 Interface Reference Guide44
Table 22 Vendor-Unique
Logical Unit Identifier — Field
Descriptions
FieldDescription
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Protocol
Set to 0.
Identifier
Code SetSet to 2h indicating the descriptor consists of ASCII printable characters.
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 TypeSet to 1h indicating this identifier is of the T10 Vendor-Specific type.
WORMThis would indicate that the drive can read and write WORM tapes.
Identifier LengthSet to 40, indicating the remainder of the descriptor is 40 byte long.
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.
This field is set to “DLT-S4”, 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.
DLT-S4 Interface Reference Guide45
Figure 13 Logical Unit NAA
Identifier — Data Format
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Logical Unit NAA Identifier4
Figure 13 shows the format of the Logical Unit NAA Identifier.
Bit
Byte
0Protocol Identifier (0)Code Set (1)
1PIV (0)ReservedAssociation (0)Identifier Type (3h)
2Reserved
3Identifier Length (08h)
4 — 11
Table 23 Logical Unit NAA
Identifier — Field Descriptions
76543210
(MSB)
NAA Identifier (binary)
FieldDescription
Protocol IdentifierSet to 0.
Code SetSet to 1h, indicating binary data.
PIVSet to 0, indicating that the value returned in the Protocol Identifier field
should be ignored.
(LSB)
AssociationSet to 0, indicating that the Identifier is associated with the logical unit.
Identifier TypeSet to 3h indicating this identifier is of the NAA type.
Identifier LengthSpecifies 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.
NAA IdentifierContains the Name Address Authority (NAA) identifier for the logical unit.
DLT-S4 Interface Reference Guide46
Figure 14 Port NAA Identifier
— Data Format
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Port NAA Identifier4
Figure 14 shows the format of the Port NAA Identifier.
Bit
Byte
0Protocol IdentifierCode Set (1)
1PIV (1)ReservedAssociation (1)Identifier Type (3)
2Reserved
3Identifier Length (08h)
4 — 11
Table 24 Port NAA Identifier —
Field Descriptions
76543210
(MSB)
NAA Identifier (binary)
FieldDescription
Protocol IdentifierThe drive returns 0 if the protocol is Fibre Channel, and 6h if the protocol is SAS.
This identifier type is not returned by devices using a parallel SCSI interface.
Code SetSet to 1h, indicating binary data.
PIVSet to 1, indicating that the value returned in the Protocol Identifier field is valid.
(LSB)
AssociationSet to 1h, indicating that the Identifier is associated with the port.
Identifier TypeSet to 3h indicating this identifier is of the NAA type.
Identifier LengthSpecifies 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.
NAA IdentifierContains the Name Address Authority (NAA) identifier for the port.
DLT-S4 Interface Reference Guide47
Figure 15 Relative Target Port
Identifier — Data Format
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Relative Target Port Identifier4
Figure 15 shows the format of the Relative Target Port Identifier.
Bit
Byte
0Protocol IdentifierCode Set (1)
1PIV (1)ReservedAssociation (1)Identifier Type (4)
2Reserved
3Identifier Length (04h)
4 — 5Obsolete
6 — 7Relative Target Port Identifier
Table 25 Relative Target Port
Identifier — Field Descriptions
76543210
FieldDescription
Protocol IdentifierThe drive returns 0h if the protocol is Fibre Channel, 1h if the protocol is Parallel
SCSI, and 6h if the protocol is SAS.
Code SetSet to 1h, indicating binary data.
PIVSet to 1h, indicating that the value returned in the Protocol Identifier field is valid.
AssociationSet to 1h, indicating that the Identifier is associated with the port.
Identifier TypeSet to 4h indicating this identifier is of type Relative Target Port.
Identifier LengthSpecifies 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.
Relative Target Port
Value = 1 device has single port.
Identifier
DLT-S4 Interface Reference Guide48
Figure 16 Sequential-Access
Device Capabilities VPD Page
— Data Format
Figure 16 and table 26specify and describe the sequential-access device
capabilities VPD page. This page provides the application client with the
means to determine if the features specified in this page are supported by
the device server.
Bit
Byte
0Peripheral QualifierPeripheral Device Type
1Page Code (B0h)
2 — 3
4ReservedWORM (1)
5 — 7Reserved
Table 26 Sequential-Access
Device Capabilities VPD Page
— Field Descriptions
76543210
(MSB)
Page Length (4)
FieldDescription
Peripheral QualifierContains 000b.
Peripheral Device
Contains 01h.
Type
Page LengthThe
PAG E L E N GTH field specifies the length of the following VPD page data. If the
allocation length value in the
INQUIRY command descriptor block is too small to
transfer all of the VPD page data, the page length is not adjusted to reflect the
truncation.
WORMThe Write Once, Read Many (WORM) bit indicates if the device is capable of
supporting this mode. This bit is always set to 1.
(LSB)
DLT-S4 Interface Reference Guide49
Figure 17 ManufacturerAssigned Serial Number Page
— Data Format
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Manufacturer-Assigned Serial Number Page (B1h)4
Figure 17 and table 27specify and describe the Manufacturer-Assigned
Serial Number Page.
Bit
Byte
0Peripheral QualifierPeripheral Device Type
1Page Code (B1h)
2Reserved
3Page Length (10h)
4 — 19
Table 27 ManufacturerAssigned Serial Number Page
— Field Descriptions
76543210
Manufacturer Serial Number
FieldDescription
Peripheral QualifierContains 000b.
Peripheral Device
Contains 01h.
Type
Page CodeA value of B1h identifies this as the Manufacturer-Assigned Serial Number page.
Page LengthContains 10h that indicates the size of the returned Manufacturer-Assigned Serial
Number page.
Manufacturer Serial
Number
DLT-S4 Interface Reference Guide50
The Manufacturer Serial Number field contains right-aligned ASCII data that is
the manufacturer assigned serial number.
Figure 18 Firmware Build
Information Page — Data
Format
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Firmware Build Information Page (C0h)4
Figure 18 shows the format of the Firmware Build Information page the
drive returns.
Bit
Byte
0
1
2
3
4 — 7
8 — 11
12 — 15
16 — 19
20 — 43
Table 28 Firmware Build
Information Page — Field
Descriptions
76543210
Peripheral QualifierPeripheral Device Type
FieldDescription
Page Code (C0h)
ReservedWORM
Page Length (28h)
Servo Firmware Revision
Servo Firmware Checksum
Servo EEPROM Checksum
Controller Firmware Checksum
Controller Firmware Build Date
WORMThe Write Once, Read Many (WORM) bit indicates if the device is
capable of supporting this mode. This bit is always set to 1.
Servo Firmware RevisionContains the revision number of the servo firmware.
ChecksumThe Servo Firmware, Servo EEPROM, and
READ / WRITE Firmware
checksums are binary numbers used for positive firmware and
EEPROM identification.
Controller Firmware Build
Date
DLT-S4 Interface Reference Guide51
Firmware Build Date. An ASCII string in DD-MM-YYYY HH:MM:SS
format.
Figure 19 Subsystem
Components Revision Page —
Data Format
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Subsystem Components Revision Page (C1h)4
Figure 19 identifies the revision of tape drive subsystem components.
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
14Tape Drive Hardware Version Number
76543210
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
DLT-S4 Interface Reference Guide52
Chapter 4 SCSI Commands
INQUIRY Command (12h)
Table 29 Subsystem
Components Revision Page —
Field Descriptions
FieldDescription
Product FamilyIndicates the data density of the tape drive. This field is set to a value of Dh.
Released
Firmware
Differentiates 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 non-zero minor
firmware version numbers.
Version Number
Fields
Firmware
Personality
Firmware
Subpersonality
Vendor-Specific
These fields display the various version numbers in binary format, instead of
ASCII.
Numeric indicator of firmware personality. Note that when set to 4, indicates OEM
family.
Indicates the variant of the firmware personality. Always set to 1, indicating the
primary firmware personality variant.
Product identification.
Subtype
Media Loader
When set to 0, indicates no loader present. Non-zero indicates loader is present.
Present Flag
Library Present
When set to 0, indicates no library present. Non-zero indicates library is present.
Flag
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
Drive’s serial number; matches what is shown on the exterior of the drive chassis.
Number
DLT-S4 Interface Reference Guide53
Chapter 4 SCSI Commands
LOAD UNLOAD Command (1Bh)
LOAD UNLOAD Command (1Bh)4
The LOAD UNLOAD command instructs the DLT-S4 tape drive to load or
unload the tape inside the data cartridge. If no data cartridge is in the
Figure 20 LOAD UNLOAD
Command Descriptor Block
Data Format
drive, the
with the Sense Key set to
LOAD UNLOAD command with the Immediate bit set and then it receives
another command that requires tape motion or if it receives a
READY
Sense Key set to
Before executing the
cached write data to the tape.
—
LOAD UNLOAD command returns a CHECK CONDITION status
NOT READY. Likewise, if the drive receives a
TEST UNIT
command, the drive returns a CHECK CONDITION status with the
NOT READY.
LOAD UNLOAD command, the drive writes any
Bit
Byte
0Operation Code (1Bh)
1ReservedImmed
2 — 3Reserved
4ReservedHoldEOTReTenLoad
5Control
DLT-S4 Interface Reference Guide54
76543210
Chapter 4 SCSI Commands
LOAD UNLOAD Command (1Bh)
Table 30 LOAD UNLOAD
Command Descriptor Block
Field Descriptions
—
FieldDescription
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.
HoldSee table 31
.
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.
LoadSee table 31
Table 31 HOLD and LOAD —
Field Descriptions
.
HOLDLOADDescription
00The tape is unloaded and the cartridge is ejected. When the
the
LOAD bit is set to 0, the tape is unloaded and the cartridge is ejected.
01The tape is and positioned for access. When set to 0 and the
HOLD bit is set to 0 and
LOAD bit is set to one,
the tape is loaded for medium access.
10The tape is unloaded, but not ejected. When the HOLD bit is set to 1 and the
LOAD
bit is set to 0, the tape is unloaded from the device but not ejected to allow the
operator access to the cartridge.
11The tape is seated, but not loaded. When the
HOLD bit set to 1 and the LOAD bit is
also set to 1, the tape is loaded to the point where the MAM is accessible but the
medium is not positioned for access.
DLT-S4 Interface Reference Guide55
Chapter 4 SCSI Commands
LOCATE Command (2Bh)
LOCATE Command (2Bh)4
The LOCATE command performs high-speed positioning to a specified
block address. Use the
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.
Figure 21 LOCATE Command
Descriptor Block — Data
Format
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 Specifies the Logical Object Identifier to which the drive positions the medium.
PartitionNot applicable; the drive ignores this bit (see CP field).
DLT-S4 Interface Reference Guide56
Chapter 4 SCSI Commands
LOG SELECT Command (4Ch)
LOG SELECT Command (4Ch)4
The LOG SELECT command allows the host to manage statistical
information the DLT-S4 tape drive maintains about its own hardware
parameters and about the installed tape medium. Read the description of
the LOG SENSE Command (4Dh)
about log page format, parameters, and supported pages.
Figure 22 LOG SELECT
Descriptor Block — Data
Format
Bit
76543210
Byte
0Operation Code (4Ch)
on page 66; it provides information
1ReservedPCRSP
2PCReserved
3 — 6Reserved
(MSB)
7 — 8
9Control
DLT-S4 Interface Reference Guide57
Parameter List Length
(LSB)
Chapter 4 SCSI Commands
LOG SELECT Command (4Ch)
Table 33 LOG SELECT
Command Descriptor Block —
Field Descriptions
FieldDescription
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 0C 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
CONDITION
(ASC) set to
status, Sense Key set to ILLEGAL REQUEST, and Additional Sense Code
INVALID FIELD IN CDB.
CHECK
SPSave Parameters. Must be set to 0.
PCPage Control. Defines the type of parameter values to be selected:
CodeTypes of Parameter Value
00bCurrent Threshold Values
01bCurrent Threshold Values
10bDefault Threshold Values
11bDefault Threshold 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
DATA OUT.
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. If the drive detects one of the conditions listed, it will
return
4
CHECK CONDITION with the Sense Key set to ILLEGAL REQUEST
and the Additional Sense Code set to INVALID FIELD IN CDB.
The conditions that constitute errors are:
•PCR bit is set to 1; 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.
The LOG SELECT command allows the initiator to modify and initialize
parameters within the logs the drive supports.
4
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 34 LOG SELECT Pageclearing Codes
Page CodePage Description
02hWrite Error Count Page
03hRead Error Count Page
0ChSequential Access Device Page
38hGeneral Purpose Non-Volatile Log Page
Note:If an initiator sends multiple pages, it must send them in
ascending order according to page code. Otherwise, the drive
terminates the command with a
Sense Key set to
Code set to
ILLEGAL REQUEST, and Additional Sense
INVALID FIELD IN PARAMETER LIST. The drive
CHECK CONDITION status,
returns the same status if an unsupported page code appears
in any header or if the specified page cannot be cleared.
DLT-S4 Interface Reference Guide59
Chapter 4 SCSI Commands
LOG SELECT Command (4Ch)
LOG SELECT Log Page
Format
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
4
for parameter code 05h, comprises 8 bytes. The parameter block for page
code 05h is 12 bytes.
Figure 23 LOG SELECT Log
Page — Data Format
Bit
Byte
0Page Code
1Reserved
76543210
(MSB)
2 – 3
4Log Parameter (First)
x + 3Length (x)
Page Length (n – 3)
Log Parameters
(LSB)
.
.
n — y + 1Log Parameter (Last)
nLength (y)
Table 35 LOG SELECT Log
Page Header — Field
Descriptions
FieldDescription
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 4 bytes that make up the
header.
Log ParametersUse one block for each parameter code.
DLT-S4 Interface Reference Guide60
Figure 24 LOG SELECT Log
Page — Parameters Format
Chapter 4 SCSI Commands
LOG SELECT Command (4Ch)
Bit
Byte
76543210
(MSB)
0 — 1
2 DUDSTSDETCTMCLBINLP
3Parameter Length (n – 3)
Parameter Code
(MSB)
4 — n
Table 36 LOG SELECT Log
Parameters — Field
Descriptions
Parameter Value
FieldDescription
Parameter CodeParameter codes supported for the
READ / WRITE error counter pages:
(LSB)
(LSB)
CodeDescription
0000hErrors corrected without substantial delays
0001hErrors corrected with possible delays
0002hTotal read / write errors
0003hTotal read / write errors
0004hTotal times correction algorithm processed. Always 0 for write errors only.
0005hTotal bytes processed
0006hTotal uncorrected errors
8000h
DLT-S4 Interface Reference Guide61
WRITE errors since last READ (page 02) or
READ errors since last WRITE (page 03)
FieldDescription
Chapter 4 SCSI Commands
LOG SELECT Command (4Ch)
Parameter Code
(continued)
8001hTotal raw write error flags
8002hTotal dropout error count
8003hTotal servo tracking errors
9000h-
Without substantial delay errors by channel
900Fh
9080h908Fh
Note:Parameter codes 00h, 01h, and 04h always have a value of 0. Parameter value for 05h
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.
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. DS and Target Save Disable (TSD) must be set to 1.
TSDTarget Save Disable. TSD and DS must be set to 1.
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/ SENSEControl Page 0Ah is set to 1, the drive generates a UNIT
ATTENTION
THRESHOLD CONDITION MET. If the RLEC bit is 0 and the comparison is met, the
drive does not generate a
for all initiators. The drive sets the Additional Sense Code to
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
generates a
UNIT ATTENTION for all initiators.
MODE SENSE / SELECT Control Page is set to 1, the drive
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
DLT-S4 Interface Reference Guide62
FieldDescription
Chapter 4 SCSI Commands
LOG SELECT Command (4Ch)
TMC (continued)
• 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
tape drive by power-cycle,
TARGET RESET, SCSI RESET, or FCP TARGET RESET.
• The Default Cumulative Values are the values to which each parameter is
initialized at a reset condition. Default value is 0.
• By default, Current Threshold Values are set to Default Threshold Values.
• Note that all types of parameter values are changeable using
LOG SELECT.
LBINList Binary. Must be set to 0.
LPList Parameter. Always set this bit to 0 to indicate that parameter codes are treated as
data counters.
Parameter Length Specifies the number of bytes in the parameter value.
Parameter ValueIndicates the actual value of this log parameter.
General Purpose
Non-Volatile Log Page
(38h)
Log page 38h provides access to a 64 byte non-volatile buffer in the tape
drive for general purpose use. The log page contains one 64 byte
parameter with a Parameter Code setting of 0. The 64 bytes in the
4
Parameter Value field are stored in device non-volatile memory and are
returned when a
LOG SENSE command requests log page 38h.
Figure 25 General Purpose
Non-Volatile LOG SELECT
Page — Header Format
Bit
Byte
0Page Code (38h)
1Reserved
76543210
(MSB)
2 – 3
DLT-S4 Interface Reference Guide63
Page Length
(LSB)
Chapter 4 SCSI Commands
LOG SELECT Command (4Ch)
Table 37 General Purpose
Non-Volatile LOG SELECT
Header — Field Descriptions
FieldDescription
Page CodeEchoes the page code specified in the
LOG SELECT CDB.
Page LengthSpecifies the total number of bytes contained in this log
page, not including the 4 bytes that make up the header.
Figure 26 General Purpose
Non-Volatile LOG SELECT
Page — Parameter Format
Bit
Byte
76543210
(MSB)
0 — 1
2 DUDSTSDETCTMCLBINLP
3Parameter Length (40h)
Parameter Code
(MSB)
4 — 67
Parameter Value
(LSB)
(LSB)
DLT-S4 Interface Reference Guide64
Chapter 4 SCSI Commands
LOG SELECT Command (4Ch)
Table 38 General Purpose
Non-Volatile LOG SELECT
Page — Field Descriptions
FieldDescription
Parameter CodeParameter code supported for this page. Must be 0.
Parameter
Control Byte
BitValueDescription
DU1Disable Update.
DS0Disable Save.
TSD0Target Save Disable.
ETC0Enable Threshold Comparison.
TMC0Threshold Met Criteria.
LBIN0List Binary.
LP1List Parameter.
Parameter Length Specifies the number of bytes in the parameter value. Must be 40h.
Parameter ValueIndicates the actual value of this log parameter.
Error Detection Summary
in LOG SELECT Pages
The host issues a LOG SENSE command to initialize host-resident
software that allows determination of:
4
•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
ILLEGAL REQUEST and Additional Sense Code set to INVALID FIELD IN
PARAMETER LIST
:
CHECK CONDITION status with Sense Data set to
•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 parameter control byte is set to an invalid value for the parameter
code.
DLT-S4 Interface Reference Guide65
Chapter 4 SCSI Commands
LOG SENSE Command (4Dh)
LOG SENSE Command (4Dh)4
The LOG SENSE command allows the host to retrieve statistical
information the tape drive maintains about its own hardware parameters
or about the installed tape medium. This command complements the
SELECT
Figure 27 LOG SENSE
Command Descriptor Block —
Data Format
Bit
76543210
Byte
0Operation Code (4Dh)
1ReservedPPCSP (0)
command.
LOG
2PCPage Code
3 — 4Reserved
(MSB)
5 — 6
(MSB)
7 — 8
9Control
DLT-S4 Interface Reference Guide66
Parameter Pointer
(LSB)
Allocation Length
(LSB)
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.