DLT™4000 Tape Drive
Product Manual
April 4, 2001
81-60043-04
Quantum reserves the right to make changes and improvements to its products, without
incurring any obligation to incorporate such changes or improvements in units
previously sold or shipped. Quantum reserves the right to make changes to this product
manual without incurring any obligation to notify recipients of earlier versions of the
product manual.
You can request Quantum publications from your Quantum Sales Representative or order
them directly from Quantum.
Publication Number: 81-60043-04, April 4, 2001
SERVICE CENTERS
Quantum Service Center
715 Sycamore Avenue
Milpitas, California 95035
Phone (800) 826-8022
FAX: (800) 4DISKFAX
BBS: (800) 472-9799
Quantum Asia-Pacific Pte. Ltd. Quantum Customer Service
50 Tagore Lane #b1-04
Quantum Ireland, Ltd.
Singapore, 2678
Finnabair Industrial Park
Phone: (65) 450-9333
Dundalk
FAX: (65) 452-2544
County Louth, Ireland
Phone: (353) 42-55350
Fax: (353) 45-55355
Copyright  1995-2001 by Quantum Corporation. All rights reserved. Printed in U.S.A.
Quantum and the Quantum logo are trademarks of Quantum Corporation, registered in
the U.S.A. and other countries. DLTtape and the DLTtape logo are trademarks of
Quantum Corporation. Products mentioned herein are for identification purposes only
and may be trademarks or registered trademarks of their respective companies.
USER MANUAL STATEMENTS FOR CLASS A EQUIPMENT (INTEGRATIBLE TAPE SYSTEM)
This equipment generates, uses, and may emit radio frequency energy. The equipment has been
type tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of
FCC rules, which are designed to provide reasonable protection against such radio frequency
interference.
Operation of this equipment in a residential area may cause interference in which case the user at
his own expense will be required to take whatever measures may be required to correct the
interference.
Any modifications to this device - unless expressly approved by the manufacturer - can void the
user’s authority to operate this equipment under part 15 of the FCC rules.
Note: Additional information on the need to interconnect the device with shielded (data) cables or
the need for special devices, such as ferrite beads on cables, is required if such means of interference
suppression was used in the qualification test for the device. This information will vary from device
to device and needs to be obtained from the EMC group or product manager.
Warning!
This is a Class A product. In a domestic environment this product may cause radio interference in
which case the user may be required to take adequate measures.
Achtung!
Dieses ist ein Gerät der Funkstörgrenzwertklasse A. In Wohnbereichen können bei Betrieb dieses
Gerätes Rundfunkstörungen auftreten, in welchen Fällen der Benutzer für entsprechende
Gegenmaßnahmen verantwortlich ist.
Warning!
This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
Attention!
Ceci est un produit de Classe A. Dans un environnement domestique, ce produit risque de créer des
interférences radioélectriques, il appartiendra alors à l'utilisateur de prendre les mesures spécifiques
appropriées.
USER MANUAL STATEMENTS FOR CLASS A EQUIPMENT (continued)
USER MANUAL STATEMENTS FOR CLASS B EQUIPMENT (TABLETOP VERSION)
This equipment has been tested and found to comply with the limits for a Class B digital device,
pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection
against harmful interference in a residential installation. Any modifications to this device unless expressly approved by the manufacturer - can void the user’s authority to operate this
equipment under part 15 of the FCC rules. Operation is subject to the following two conditions:
(1) This device may not cause harmful interference and (2) This device must accept any
interference that may cause undesirable operation.
This equipment generates, uses, and can radiate radio frequency energy and, if not installed
and used in accordance with the instructions, may cause harmful interference to radio
communications. However, there is no guarantee that interference will not occur in a particular
installation. If this equipment does cause harmful interference to radio or television reception,
which can be determined by turning the equipment off and on, the user is encouraged to try to
correct the interference by one or more of the following measures:
•
Reorient or relocate the receiving antenna.
•
Increase the separation between the equipment and receiver.
•
Connect the equipment into an outlet on a circuit different from that to which the receiver is
connected
•
Consult the dealer or an experienced radio/TV technician for help.
Note: Additional information on the need to interconnect the device with shielded (data) cables
or the need for special devices, such as ferrite beads on cables, is required if such means of
interference suppression was used in the qualification test for the device. This information will
vary from device to device and needs to be obtained from the EMC group or product manager.
This Class B digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe B est conforme à la norme NMB-003 du Canada.
USER MANUAL STATEMENTS FOR CLASS B EQUIPMENT (continued)
TABLE OF CONTENTS
Revision History........................................................................................................
About This Manual ..................................................................................................
xix
xxi
Chapter 1: General Description and Specifications....................................................
1.1 Product Description..............................................................................
1.2 Product Features .................................................................................
1.3 Product Specifications ..........................................................................
1.3.1 Physical Specifications .................................................................
1.3.2 Interface Type.............................................................................
1.3.3 Storage Capacity.........................................................................
1.3.4 Performance Data.......................................................................
1.3.5 Environmental Specifications.......................................................
1.3.6 Power Requirements...................................................................
1.3.7 Electromagnetic Emissions...........................................................
1.3.8 EMI and Safety Certifications.......................................................
1.3.9 Reliability (Projected) ...................................................................
1.3.10 Acoustic Noise Emissions..............................................................
1.3.11 Tape Drive Recording Type ..........................................................
1.3.12 DLTtape Recording Media Specifications......................................
1-1
1-1
1-3
1-3
1-3
1-4
1-4
1-4
1-5
1-7
1-7
1-8
1-8
1-9
1-9
1-10
Chapter 2: Hardware Implementation .....................................................................
2.1 Safety, Handling and Electrostatic Discharge (ESD) Protection ................
2.1.1 Safety Precautions ......................................................................
2.1.2 Handling ....................................................................................
2.1.3 Electrostatic Discharge (ESD) Protection .......................................
2.2 Drive Setup ..........................................................................................
2.2.1 Set the Rackmount Drive SCSI ID..................................................
2.2.2 Configure the Rackmount Drive for TERMPWR
(Single-Ended Only).....................................................................
2.2.3 Configure the Rackmount Drive for Parity Checking .....................
2.2.4 Configure the Tabletop Drive ......................................................
2.3 Drive Installation...................................................................................
2.4 Drive Connections ................................................................................
2.4.1 SCSI and Power Connectors (Rackmount).....................................
2.4.2 Optional Loader Connector (Rackmount) .....................................
2.4.3 Tabletop Drive Connectors..........................................................
2.5 Drive Controls and Light Emitting Diodes (LEDs).....................................
2.5.1 Front Panel Controls and LEDs.....................................................
2-1
2-1
2-2
2-2
2-3
2-3
2-4
Quantum DLT 4000 Tape Drive
2-6
2-7
2-7
2-8
2-10
2-11
2-14
2-15
2-17
2-17
vii
Table of Contents
2.5.2 Selecting Density......................................................................... 2-21
2.6 Power On Self Test (POST).................................................................... 2-23
2.7 Troubleshooting................................................................................... 2-25
Chapter 3:
3.1
3.2
3.3
SCSI Description.....................................................................................
SCSI Overview ......................................................................................
SCSI Commands....................................................................................
Signal States ........................................................................................
3.3.1 Signal Values ..............................................................................
3.3.2 SCSI ID Bits..................................................................................
3.4 SCSI Signals..........................................................................................
3.4.1 SCSI Signal Definitions.................................................................
3.4.2 Signal Bus Timing........................................................................
3.5 SCSI Bus Phases ....................................................................................
3.5.1 BUS FREE Phase ...........................................................................
3.5.2 ARBITRATION Phase .....................................................................
3.5.3 SELECTION Phase ........................................................................
3.5.4 RESELECTION Phase .....................................................................
3.5.5 Information Transfer Phases........................................................
3.6 SCSI Bus Conditions..............................................................................
3.6.1 Attention Condition....................................................................
3.6.2 Reset Condition ..........................................................................
3.6.3 Queued Unit Attentions..............................................................
3-1
3-1
3-1
3-4
3-4
3-6
3-6
3-6
3-7
3-10
3-10
3-12
3-13
3-15
3-17
3-24
3-24
3-25
3-26
Chapter 4: Messages............................................................................................... 4-1
4.1 Message Format ................................................................................... 4-1
4.2 Supported SCSI Messages..................................................................... 4-5
4.2.1 ABORT Message (06h)................................................................. 4-5
4.2.2 BUS DEVICE RESET Message (0Ch) ............................................... 4-5
4.2.3 COMMAND COMPLETE Message (00h) ........................................ 4-5
4.2.4 DISCONNECT Message (04h) ....................................................... 4-6
4.2.5 IDENTIFY Message (80h - FFh)...................................................... 4-7
4.2.6 INITIATOR DETECTED ERROR Message (05h) ................................. 4-8
4.2.7 LINKED COMMAND COMPLETE Message (0Ah) ............................. 4-9
4.2.8 LINKED COMMAND COMPLETE, with Flag Message (0Ah).............. 4-9
4.2.9 MESSAGE PARITY ERROR Message (09h)....................................... 4-9
4.2.10 MESSAGE REJECT Message (07h)................................................. 4-9
4.2.11 NO OPERATION Message (08h).................................................... 4-10
4.2.12 RESTORE POINTERS Message (03h) .............................................. 4-10
4.2.13 SAVE DATA POINTER Message (02h)............................................ 4-10
4.2.14 SYNCHRONOUS DATA TRANSFER REQUEST Message ..................... 4-10
viii
Quantum DLT 4000 Tape Drive
Table of Contents
Chapter 5: SCSI Commands.....................................................................................
5.1 Overview of Command and Status Processing........................................
5.1.1 SCSI Pointers...............................................................................
5.1.2 Command Descriptor Block..........................................................
5.1.3 Status/Error Reporting ................................................................
5.1.4 DATA-Phase Command Components............................................
5.1.5 Unit Attention Condition ............................................................
5.1.6 Behavior At Power-On and SCSI Bus Reset....................................
5.1.7 Data Cache and Tape Write Interaction........................................
5.2 SCSI Command Descriptions..................................................................
5.3 ERASE Command (19h) .........................................................................
5.4 INQUIRY Command (12h)......................................................................
5.4.1 Standard Inquiry Data Page.........................................................
5.4.2 Vendor Unique Inquiry Data........................................................
5.4.3 Supported Vital Product Data Page (00h).....................................
5.5 LOAD UNLOAD Command (1Bh)...........................................................
5.6 LOCATE Command (2Bh)......................................................................
5.7 LOG SELECT Command (4Ch).................................................................
5.7.1 Log Detection Summary in LOG SELECT Command
Descriptor Block ..........................................................................
5.7.2 Operation of LOG SELECT............................................................
5.7.3 LOG SELECT Page Format ............................................................
5.7.4 Error Detection Summary in LOG SELECT Pages............................
5.8 LOG SENSE Command (4Dh)..................................................................
5.8.1 Error Detection Summary in LOG SENSE Command
Descriptor Block ..........................................................................
5.8.2 Supported Pages Log Page (00h).................................................
5.8.3 Read (Page 03h)/Write (Page 02h) Error LOG SENSE Page..............
5.8.4 Last n Error Events Page (07h) .....................................................
5.8.5 Read/Write Compression Page (32h).............................................
5.8.6 Device Wellness Page (33h)..........................................................
5.8.7 Device Status Page (3Eh) .............................................................
5.9 MODE SELECT (6) / (10) Command (15h / 55h).......................................
5.9.1 Mode Parameter List ...................................................................
5.9.2 Read/Write Error Recovery Page (01h) ..........................................
5.9.3 Disconnect/Reconnect Page ........................................................
5.9.4 Control Mode Page (0Ah)............................................................
5.9.5 Data Compression Page (0Fh) ......................................................
5.9.6 Device Configuration Page (10h)..................................................
5.9.7 Medium Partition Page (11h).......................................................
5.9.8 EEPROM Vendor Unique Page (3Eh).............................................
5.9.9 Changeable Parameters within MODE SELECT ..............................
Quantum DLT 4000 Tape Drive
5-1
5-1
5-3
5-4
5-7
5-8
5-11
5-11
5-12
5-13
5-15
5-17
5-18
5-21
5-24
5-27
5-31
5-33
5-35
5-35
5-36
5-39
5-41
5-44
5-45
5-46
5-49
5-52
5-57
5-60
5-63
5-65
5-72
5-73
5-77
5-79
5-81
5-84
5-86
5-93
ix
Table of Contents
5.10 MODE SENSE (6) / (10) Command (1Ah / 5Ah)....................................... 5-95
5.10.1 MODE SENSE Data Headers......................................................... 5-98
5.10.2 MODE SENSE Block Descriptors....................................................5-100
5.10.3 MODE SENSE Mode Pages...........................................................5-102
5.11 PREVENT / ALLOW MEDIUM REMOVAL Command (1Eh)..........................5-119
5.12 READ Command (08h)...........................................................................5-121
5.13 READ BLOCK LIMITS Command (05h) .....................................................5-125
5.14 READ BUFFER Command (3Ch)..............................................................5-127
5.14.1 Combined Header and Data Mode ..............................................5-128
5.14.2 Data Mode ................................................................................5-129
5.14.3 Descriptor Mode ........................................................................5-129
5.15 READ POSITION Command (34h)............................................................5-131
5.16 RECEIVE DIAGNOSTIC RESULTS Command (1Ch)......................................5-135
5.17 RELEASE UNIT Command (17h)..............................................................5-137
5.18 REPORT LUNS Command (0Ah).............................................................. 5-139
5.19 REQUEST SENSE Command (03h)...........................................................5-141
5.20 RESERVE UNIT Command (16h).............................................................5-151
5.21 REWIND Command (01h).......................................................................5-153
5.22 SEND DIAGNOSTIC Command (1Dh).......................................................5-155
5.23 SPACE Command (11h)........................................................................5-161
5.24 TEST UNIT READY Command (00h).........................................................5-163
5.25 VERIFY Command (13h).........................................................................5-165
5.26 WRITE Command (0Ah).........................................................................5-167
5.27 WRITE BUFFER Command (3Bh)..............................................................5-169
5.27.1 Write Combined Header and Data Mode (000b) ...........................5-170
5.27.2 Write Data Mode (010b)..............................................................5-170
5.27.3 Download Microcode Mode (100b)..............................................5-171
5.27.4 Download Microcode and Save Mode (101b) ...............................5-171
5.28 WRITE FILEMARKS Command (10h) .......................................................5-173
Appendix A: Definition of Vendor Unique Sense Data Information ......................................................
Appendix B: EEPROM-Resident Bugcheck and Event Logs ....................................................................
B.1 EEPROM Packets (Last n Events)........................................................................................
B.2 Bugcheck Packets................................................................................................................
B.2.1 POST Failure Packets...............................................................................................
B.2.2 Event Log Packets...................................................................................................
Appendix C: Updating the Firmware..........................................................................................................
C.1 Overview ..............................................................................................................................
C.2 Creating a Firmware Update Tape ....................................................................................
C.3 Firmware Update Procedure..............................................................................................
C.4 Interpreting the Results of a Firmware Update ...............................................................
Appendix D: The Tape Cartridge ................................................................................................................
D.1 Tape Cartridge Handling Guidelines ................................................................................
D.2 Tape Cartridge Inspection Procedure................................................................................
x
Quantum DLT 4000 Tape Drive
A-1
B-1
B-1
B-1
B-2
B-3
C-1
C-1
C-1
C-2
C-4
D-1
D-1
D-4
Table of Contents
D.3
D.4
D.5
D.6
Tape Cartridge Write-Protect Switch ..................................................... D-8
Loading a Tape Cartridge ..................................................................... D-10
Unloading a Tape Cartridge.................................................................. D-11
Using a Cleaning Tape Cartridge ........................................................... D-12
Index
Quantum DLT 4000 Tape Drive
xi
Table of Contents
Figures
Figure 1-1.
Figure 1-2.
Figure 2-1.
Figure 2-2.
Quantum DLT 4000 Tape Drive (Rackmount)............................................
Quantum DLT 4000 Tape Drive (Tabletop) ...............................................
DLT 4000 SCSI ID Jumper Location (Rackmount Version Shown)...............
DLT 4000 TERMPWR and Parity Check Jumper Locations
(Rackmount Version Shown) ..................................................................
Figure 2-3. Tabletop (Version 1) Back Panel Controls.................................................
Figure 2-4. Tabletop (Version 2) Back Panel Controls.................................................
Figure 2-5. Rackmount Drive Mounting Locations – Side and Bottom Views ..............
Figure 2-6. SCSI and Power Cable Connectors (Rackmount Version Shown)...............
Figure 2-7. Loader Connector Block Location (Rackmount Version Shown)................
Figure 2-8. Tabletop (Version 1) Back Panel Connectors............................................
Figure 2-9. Tabletop (Version 2) Back Panel Connectors............................................
Figure 2-10. DLT 4000 Front Panel............................................................................
Figure 4-1. Extended Message - Data Format............................................................
Figure 4-2. IDENTIFY Message - Data Format.............................................................
Figure 4-3. SYNCHRONOUS DATA TRANSFER REQUEST Message - Data Format...........
Figure 5-1. Typical Command Descriptor Block - Data Format ....................................
Figure 5-2. Command Descriptor Block Control Field - Data Format ...........................
Figure 5-3. ERASE Command Descriptor Block - Data Format.....................................
Figure 5-4. INQUIRY Command Descriptor Block - Data Format ..................................
Figure 5-5. Standard Inquiry Data Page - Data Format ..............................................
Figure 5-6. INQUIRY Vendor Unique Bytes Definitions................................................
Figure 5-7. Supported Vital Product Data Pages Page - Data Format .........................
Figure 5-8. Unit Serial Number Page - Data Format...................................................
Figure 5-9. Firmware Build Information Page - Data Format ......................................
Figure 5-10. LOAD UNLOAD Command Descriptor Block - Data Format.......................
Figure 5-11. LOCATE Command Descriptor Block - Data Format.................................
Figure 5-12. LOG SELECT Command Descriptor Block - Data Format...........................
Figure 5-13. LOG SELECT Log Page Header Format ...................................................
Figure 5-14. LOG SELECT Log Parameters Format......................................................
Figure 5-15. LOG SENSE Command Descriptor Block - Data Format............................
Figure 5-16. Supported Pages Page - Data Format....................................................
Figure 5-17. Read/Write Error LOG SENSE Header Format..........................................
Figure 5-18. Log Parameters Format for Read/Write Error LOG SENSE Page................
Figure 5-19. Last n Error Events LOG SENSE Header Format.......................................
Figure 5-20. Log Parameters Format for Last n Error Events LOG SENSE Page ............
Figure 5-21. Read/Write Compression Ratio LOG SENSE Header Format......................
Figure 5-22. Log Parameters Format for Read / Write Compression Ratio LOG SENSE
Page (Parameter Codes 00h and 01h) .....................................................
xii
Quantum DLT 4000 Tape Drive
1-2
1-2
2-4
2-6
2-7
2-8
2-9
2-11
2-14
2-15
2-16
2-17
4-4
4-7
4-11
5-4
5-6
5-15
5-17
5-19
5-22
5-24
5-25
5-26
5-28
5-31
5-33
5-36
5-37
5-41
5-45
5-46
5-47
5-50
5-51
5-52
5-53
Table of Contents
Figure 5-23 Log Parameters Format for Read / Write Compression Ratio LOG SENSE
Page (Parameter Codes 02h through 09h)............................................... 5-54
Figure 5-24. Device Wellness LOG SENSE Header Format ........................................... 5-57
Figure 5-25. Log Parameters Format for Device Wellness LOG SENSE Page
(Parameters 0000h – 000Fh) ................................................................... 5-58
Figure 5-26. Device Status LOG SENSE Header Format................................................ 5-60
Figure 5-27. Log Parameters Format for Device Status LOG SENSE Page
(Parameters 0000h, 0001h, or 0002h) ..................................................... 5-61
Figure 5-28. Log Parameters Format for Device Status LOG SENSE Page
Parameter 0001h (Cleaning Related) ....................................................... 5-62
Figure 5-29. MODE SELECT (6) and (10) Command Descriptor Blocks - Data Format ..... 5-64
Figure 5-30. MODE SELECT Mode Parameter List - Data Format.................................. 5-65
Figure 5-31. MODE SELECT Mode Parameter Header - Data Format............................ 5-66
Figure 5-32. MODE SELECT Mode Parameter Block Descriptor - Data Format............... 5-68
Figure 5-33. MODE SELECT Page Descriptor – Page Format ........................................ 5-70
Figure 5-34. Error Recovery Page - Data Format......................................................... 5-72
Figure 5-35. Disconnect / Reconnect Page - Data Format............................................ 5-74
Figure 5-36. Control Mode Page Format Descriptor - Data Format.............................. 5-77
Figure 5-37. Data Compression Page Format Descriptor - Data Format........................ 5-79
Figure 5-38. Device Configuration Page - Data Format............................................... 5-81
Figure 5-39. Medium Partition Page Format Descriptor - Data Format......................... 5-84
Figure 5-40. EEPROM Vendor Unique Page - Data Format .......................................... 5-86
Figure 5-41. EEPROM Vendor Unique Page “Vendor ID” Example - Data Format.......... 5-91
Figure 5-42. EEPROM Vendor Unique Page “Forced Density” Example - Data Format ... 5-92
Figure 5-43. MODE SENSE (6) Command Descriptor Block - Data Format..................... 5-95
Figure 5-44. MODE SENSE (10) Command Descriptor Block - Data Format ................... 5-96
Figure 5-45. MODE SENSE (6) Data Header - Data Format .......................................... 5-98
Figure 5-46. MODE SENSE (10) Data Header - Data Format......................................... 5-98
Figure 5-47. MODE SENSE (6) Block Descriptor - Data Format .....................................5-100
Figure 5-48. MODE SENSE Page Descriptor - Data Format ..........................................5-102
Figure 5-49. Read / Write Error Recovery Page - Data Format......................................5-104
Figure 5-50. Disconnect / Reconnect Page - Data Format............................................5-106
Figure 5-51. Control Mode Page - Data Format .........................................................5-108
Figure 5-52. Data Compression Page - Data Format .................................................5-110
Figure 5-53. Device Configuration Page - Data Format.............................................5-112
Figure 5-54. Medium Partition Page - Data Format ..................................................5-115
Figure 5-55. PREVENT / ALLOW MEDIUM REMOVAL Command Descriptor Block Data Format ..........................................................................................5-119
Figure 5-56. READ Command Descriptor Block - Data Format .....................................5-121
Figure 5-57. READ BLOCK LIMITS Command Descriptor Block - Data Format ................5-125
Figure 5-58. READ BLOCK LIMITS Data - Data Format .................................................5-126
Figure 5-59. READ BUFFER Command Descriptor Block - Data Format..........................5-127
Figure 5-60. READ BUFFER Header - Data Format .......................................................5-128
Quantum DLT 4000 Tape Drive
xiii
Table of Contents
Figure
Figure
Figure
Figure
5-61. READ BUFFER Descriptor - Data Format...................................................5-129
5-62. READ POSITION Command Descriptor Block - Data Format ......................5-131
5-63. READ POSITION - Data Format................................................................5-132
5-64. RECEIVE DIAGNOSTICS RESULTS Command Descriptor Block –
Data Format ..........................................................................................5-135
Figure 5-65. RECEIVE DIAGNOSTICS RESULTS - Data Format ........................................5-136
Figure 5-66. RELEASE UNIT Command Descriptor Block - Data Format.........................5-137
Figure 5-67. REPORT LUNS Command Descriptor Block - Data Format .........................5-139
Figure 5-68. LUN Reporting Parameter List — Data Format.........................................5-140
Figure 5-69. REQUEST SENSE Command Descriptor Block - Data Format......................5-141
Figure 5-70. REQUEST SENSE - Data Format...............................................................5-143
Figure 5-71. RESERVE UNIT Command Descriptor Block - Data Format.........................5-151
Figure 5-72. REWIND Command Descriptor Block - Data Format..................................5-153
Figure 5-73. SEND DIAGNOSTIC Command Descriptor Block - Data Format..................5-155
Figure 5-74. SEND DIAGNOSTIC Parameter List - Data Format .....................................5-157
Figure 5-75. SPACE Command Descriptor Block - Data Format....................................5-161
Figure 5-76. TEST UNIT READY Command Descriptor Block - Data Format....................5-163
Figure 5-77. VERIFY Command Descriptor Block - Data Format....................................5-165
Figure 5-78. WRITE Command Descriptor Block - Data Format ....................................5-167
Figure 5-79. WRITE BUFFER Command Descriptor Block - Data Format.........................5-169
Figure 5-80. WRITE FILEMARKS Command Descriptor Block - Data Format ...................5-173
Figure A-1. Internal Status Bits................................................................................. A-4
Figure B-1. Directory Failure Event Package – Data Format........................................ B-5
Figure D-1. Location of the Two Reel Lock Tabs on the DLTtape Cartridge ................ D-4
Figure D-2. Location of Reel Lock Opening and Spring-Loaded Hub on
Bottom of DLTtape Cartridge ................................................................. D-5
Figure D-3. Opening the Door on a DLTtape Cartridge Showing Tape
Leader Loop in its Correct Position ......................................................... D-6
Figure D-4. Three Examples of Tape Cartridges with Damage Visible During
Visual Inspection.................................................................................... D-7
Figure D-5. Write-Protect Switch on Tape Cartridge.................................................. D-8
xiv
Quantum DLT 4000 Tape Drive
Table of Contents
Tables
Table 1-1.
Table 1-2.
Table 1-3.
Table 1-4.
Table 1-5.
Table 1-6.
Table 1-7.
Table 1-8.
Table 1-9.
Table 1-10.
Table 1-11.
Table 1-12.
Table 2-1.
Table 2-2.
Table 2-3.
Table 2-4.
Table 2-5.
Table 2-6.
Table 2-7.
Table 2-8.
Table 2-9.
Table 2-10.
Table 2-11.
Table 3-1.
Table 3-2.
Table 3-3.
Table 3-4.
Table 3-5.
Table 3-6.
Table 3-7.
Table 4-1.
Table 4-2.
Table 4-3.
Table 4-4.
Table 4-5.
Table 4-6.
Table 5-1.
Table 5-2.
DLT 4000 Physical Dimensions.................................................................
DLT 4000 Storage Capacity.....................................................................
DLT 4000 Performance Data ...................................................................
DLT 4000 Environmental Specifications ...................................................
DLT 4000 Non-Operating Shock Specifications ........................................
DLT 4000 Non-Operating Vibration Specifications....................................
DLT 4000 Power Requirements ...............................................................
EMI Emission Certificates........................................................................
Safety Certifications...............................................................................
Acoustic Noise Emissions, Nominal (English) ...........................................
Acoustic Noise Emissions for German Noise Declaration Law....................
DLTtape Media Specifications.................................................................
SCSI ID Address Selections......................................................................
Single-Ended SCSI Pin Assignment ..........................................................
Differential SCSI Pin Assignment.............................................................
4-Pin Power Connector Pin Assignment ..................................................
LED Functionality ...................................................................................
Density LED Functionality .......................................................................
Control Functionality .............................................................................
LED Activity During Density Selection......................................................
POST/Media Ready Activity .....................................................................
Tape Drive States Following Initialization ................................................
Troubleshooting Chart...........................................................................
Implemented ANSI SCSI-2 Commands......................................................
Signal Sources.......................................................................................
SCSI-2 Bus Signal Definitions...................................................................
SCSI Bus Timing Values...........................................................................
Information Transfer Phases...................................................................
Status Bytes...........................................................................................
Drive MESSAGE OUT Phase Response ......................................................
Message Format ....................................................................................
Supported Messages..............................................................................
Extended Message - Field Description .....................................................
Drive Response to DISCONNECT Message ................................................
IDENTIFY Message - Field Description.......................................................
Drive Response to INITIATOR DETECTED ERROR Message ..........................
Supported SCSI Commands....................................................................
Command Descriptor Block - Field Descriptions........................................
Quantum DLT 4000 Tape Drive
1-3
1-4
1-4
1-5
1-6
1-6
1-7
1-8
1-8
1-9
1-9
1-10
2-5
2-12
2-13
2-14
2-18
2-19
2-20
2-23
2-24
2-24
2-25
3-2
3-5
3-6
3-8
3-19
3-23
3-25
4-2
4-3
4-4
4-6
4-7
4-8
5-1
5-5
xv
Table of Contents
Table 5-3.
Table 5-4.
Table 5-5.
Table 5-6.
Table 5-7.
Table 5-8.
Table 5-9.
Table 5-10.
Table 5-11.
Table 5-12.
Table 5-13.
Table 5-14.
Table 5-15.
Table 5-16.
Table 5-17.
Table 5-18.
Table 5-19.
Table 5-20.
Table 5-21.
Table 5-22.
Table 5-23.
Table 5-24.
Table 5-25.
Table 5-26.
Table 5-27.
Table 5-28.
Table 5-29.
Table 5-30.
Table 5-31.
Table 5-32.
Table 5-33.
Table 5-34.
Table 5-35.
Table 5-36.
Table 5-37.
Table 5-38.
Table 5-39.
xvi
Command Descriptor Block Control Field - Field Descriptions....................
Status Codes .........................................................................................
Length Field Name Units ........................................................................
DATA-Phase Command Contents............................................................
ERASE Command Descriptor Block - Field Descriptions .............................
INQUIRY Command Descriptor Block - Field Descriptions...........................
Vital Product Data - Page Codes.............................................................
Standard Inquiry Data Page - Field Descriptions.......................................
Vendor Unique Inquiry Data Page – Field Descriptions.............................
Unit Serial Number Page - Field Descriptions...........................................
Firmware Build Information Page - Field Descriptions..............................
LOAD UNLOAD Command Descriptor Block - Field Descriptions................
LOCATE Command Descriptor Block – Field Descriptions..........................
LOG SELECT Command Descriptor Block - Field Descriptions.....................
LOG SELECT Log Page Header Field Descriptions .....................................
LOG SELECT Log Parameters Field Descriptions........................................
LOG SENSE Command Descriptor Block - Field Descriptions......................
Read / Write Error LOG SENSE Header Field Descriptions..........................
Log Parameters for Read / Write Error LOG SENSE Page Field
Descriptions...........................................................................................
Last n Error Events LOG SENSE Header Field Descriptions.........................
Log Parameters for Last n Error Events LOG SENSE Page Field
Descriptions...........................................................................................
Read / Write Compression Ratio LOG SENSE Header Field Descriptions......
Log Parameters for Read / Write Compression Ratio LOG SENSE Page
Field Descriptions (Parameter Codes 00h and 01h)...................................
Log Parameters for Read / Write Compression Ratio LOG SENSE Page
Field Descriptions (Parameter Codes 02h through 09h)............................
Device Wellness LOG SENSE Header Field Descriptions .............................
Log Parameters for Device Wellness LOG SENSE Page Field Descriptions ...
Device Status LOG SENSE Header Field Descriptions.................................
Log Parameters for Device Status LOG SENSE Page Field Descriptions.......
Log Parameters for Device Wellness LOG SENSE Parameter 0001h
(Cleaning Related) Field Descriptions.......................................................
MODE SELECT (6) (10) Command Descriptor Block - Field Descriptions......
MODE SELECT Mode Parameter List - Field Definitions.............................
MODE SELECT Mode Parameter Header - Field Descriptions.....................
MODE SELECT Mode Parameter Block Descriptor - Field Descriptions........
MODE SELECT Page Descriptor - Field Descriptions..................................
Error Recovery Page - Field Descriptions..................................................
Disconnect / Reconnect Page - Field Descriptions.....................................
Control Mode Page Descriptor – Field Descriptions .................................
Quantum DLT 4000 Tape Drive
5-6
5-8
5-9
5-9
5-16
5-18
5-18
5-20
5-23
5-25
5-26
5-29
5-32
5-34
5-36
5-37
5-42
5-46
5-47
5-50
5-51
5-52
5-53
5-54
5-57
5-59
5-60
5-61
5-62
5-65
5-66
5-67
5-69
5-71
5-73
5-75
5-78
Table of Contents
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
5-40.
5-41.
5-42.
5-43.
5-44.
5-45.
5-46.
5-47.
5-48.
5-49.
5-50.
5-51.
5-52.
5-53.
5-54.
5-55.
Table 5-56.
Table 5-57.
Table 5-58.
Table 5-59.
Table 5-60.
Table 5-61.
Table 5-62.
Table 5-63.
Table 5-64.
Table 5-65.
Table 5-66.
Table 5-67.
Table 5-68.
Table 5-69.
Table 5-70.
Table 5-71.
Table 5-72.
Table 5-73.
Table 5-74.
Data Compression Page Descriptor – Field Descriptions ........................... 5-80
Device Configuration Page - Field Descriptions........................................ 5-82
Medium Partition Page Descriptor - Field Descriptions............................. 5-85
EEPROM Vendor Unique Page Parameters ............................................. 5-86
Changeable Parameters within MODE SELECT......................................... 5-93
MODE SENSE Command Descriptor Block - Field Descriptions................... 5-97
MODE SENSE Data Header - Field Descriptions........................................ 5-99
MODE SENSE Block Descriptor - Field Descriptions...................................5-101
MODE SENSE Page Descriptor - Field Descriptions ...................................5-103
Read / Write Error Recovery Page - Field Descriptions...............................5-105
Disconnect / Reconnect Error Recovery Page - Field Descriptions..............5-107
Control Mode Page – Field Descriptions..................................................5-109
Data Compression Page - Field Description..............................................5-111
Device Configuration Page - Field Descriptions........................................5-113
Medium Partition Page - Field Descriptions .............................................5-116
PREVENT/ ALLOW MEDIUM REMOVAL Command Descriptor Block –
Field Descriptions...................................................................................5-120
READ Command Descriptor Block - Field Descriptions ..............................5-122
READ BLOCK LIMITS Data - Field Descriptions .........................................5-126
READ BUFFER Command Descriptor Block - Field Descriptions...................5-128
READ BUFFER Header - Field Descriptions ................................................5-129
READ POSITION Command Descriptor Block - Field Descriptions ...............5-131
READ POSITION Data - Field Description..................................................5-133
RECEIVE DIAGNOSTIC RESULTS Command Data – Field Descriptions..........5-135
RELEASE UNIT Command Data - Field Descriptions..................................5-138
REPORT LUNS Command Data - Field Descriptions ..................................5-139
REQUEST SENSE Command Data - Field Descriptions................................5-141
REQUEST SENSE Data - Field Descriptions................................................5-143
Supported Sense Keys ...........................................................................5-146
Supported ASC / ASCQ in Hex................................................................5-147
RESERVE UNIT Command - Field Descriptions...........................................5-151
REWIND Command Data - Field Descriptions............................................5-153
SEND DIAGNOSTIC Command - Field Descriptions....................................5-155
SEND DIAGNOSTIC CDB Bits Selftest, DevOfl, and UnitOfl ........................5-157
SEND DIAGNOSTIC Parameter List – Field Descriptions .............................5-158
Sense Keys Used for SEND DIAGNOSTIC ..................................................5-159
Quantum DLT 4000 Tape Drive
xvii
Table of Contents
Table 5-75.
Table 5-76.
Table 5-77.
Table 5-78.
Table 5-79.
Table 5-80.
Table A-1.
Table A-2.
Table B-1.
Table B-2.
Table B-3.
Table C-1.
Table C-2.
Table D-1.
Table D-2.
xviii
ASC / ASCQ for SEND DIAGNOSTIC .........................................................5-159
SPACE Command Data - Field Descriptions..............................................5-161
VERIFY Command Data - Field Descriptions..............................................5-166
WRITE Command Data - Field Descriptions ..............................................5-168
WRITE BUFFER Command Data - Field Descriptions...................................5-170
WRITE FILEMARKS Command Data - Field Descriptions.............................5-174
Internal Status Codes............................................................................. A-1
Internal Status Bit Flags.......................................................................... A-4
Bugcheck Packet Error Codes (Bytes 9 - 10) ............................................. B-2
Event Log Error Codes (Bytes 9 – 10)....................................................... B-3
Directory Failure Event Package – Field Descriptions ................................ B-5
Block Size Used for Firmware Update Type.............................................. C-2
Results of Firmware Update ................................................................... C-5
Write-Protect Switch Positions................................................................ D-9
When to Use a Cleaning Tape Cartridge ................................................. D-12
Quantum DLT 4000 Tape Drive
REVISION HISTORY
This Revision History provides a concise publications record of this manual. It lists the manual’s
revision levels, release dates, and a summary of changes for each release.
Manual Number
- Revision Level
Date of Release
Summary of Changes
81-108336-01
May 5, 1995
Original issue
81-108336-02
81- 60043- 01
Caution added for unloading a tape cartridge
March 10, 1996
Part number 81-108336-02 obsoleted
Manual-wide, trademark copyrights, and other changes.
Fast Data Transfer Rate correction.
Figure 2-1 and 3-6 corrected.
Section E added to POST testing.
Table 3-2 corrected.
Description of tape cartridge corrected.
Notes added to Loading a Cartridge section.
Added a caution to Unloading a Cartridge section.
Chapter 4 rewritten.
POST description updated.
Figure 5-2 updated, page 5-6.
Table 5-1 updated, page 5-11.
Table 5-2 updated, page 5-14.
Table 7-1 added, page 7-4.
Table 7-1 consolidated, page 7-8.
Caution message added, page 7-9.
Table 8-1 modified, page 8-8.
Table 8-2 modified, page 8-15.
Table 8-6 modified, page 8-21.
Product Family description and table added, page 8-22.
Density Code updated, page 8-49.
Table 8-3, additions and modifications, pages 8-65 and 8-67.
Tables A-1, A-5, A-8, A-9, A-10, A-12, A-14, A-16, A-17, A-20,
and A30 changed (pages A-3, A-1, A-13, A-14, A-15, A-17, A-18,
A-23).
Quantum DLT 4000 Tape Drive
xix
Revision History
Manual Number
- Revision Level
Date of Release
Summary of Changes
81-60043-02
April 08, 1999
Entire manual rewritten to conform to corporate standard for product
manuals. Manual updated to include new version of the DLT4000
tape drive (Chapters 1 and 2); SCSI command updates (Chapter 5);
consolidation of Request Sense ASC/ASCQ codes into one complete
table (Chapter 5) and tape cartridge additions (Appendix D).
81-60043-03
September 18, 2000
Revised.
Chapter 2: Pinout tables corrected for 50-pin single-ended and
differential SCSI connector signals (Tables 2-2 and 2-3).
Chapter 5: Corrections made to LOG SENSE command’s DEVICE
STATUS page (Log Parameter Format and TSD, ClnQ, and ClnR bits).
Appendix A: Changed field descriptions in Table A-2.
81-60043-04
xx
April 4, 2001
Updated corporate address and reader comment address.
Quantum DLT 4000 Tape Drive
ABOUT THIS MANUAL
“About this Manual” outlines the scope and contents of this manual. It contains information about
the intended audience, purpose of the manual, document organization, and document conventions.
AUDIENCE
This manual is written for original equipment manufacturers (OEMs) that are
integrating the Quantum DLT4000 tape drive and into a system or subsystem.
Its primary audience is the OEM technical staff that makes tape drive purchase
and configuration decisions, and system integrators that are responsible for the
SCSI interface. Additionally, the manual can be used by technically astute endusers for installation and operation of the tape drive, although that is a
secondary audience.
PURPOSE
This manual describes the rackmount and tabletop versions of the DLT 4000
tape drive. It is intended to provide the information necessary to integrate the
tape drive into a computer system or subsystem.
DOCUMENT ORGANIZATION
This product manual contains five chapters, a number of appendixes of related
useful information, and an index. It includes an overview of the Small Computer
System Interface (SCSI) and detailed descriptions of the messages and SCSI
commands as used by the tape drive. The manual is organized as follows:
Chapter 1
General Description and Specifications
This chapter contains a brief description of and specifications for the
drive.
Quantum DLT 4000 Tape Drive
xxi
About This Manual
Chapter 2
Hardware Implementation
This chapter contains configuration and installation information for the
tape drive, descriptions of the drive controls and LEDs, and information
on running the self-test.
Chapter 3
SCSI Description
This chapter provides a detailed description of the logical interfaces of
the tape drive. It describes the products’ compliance with the ANSI
SCSI-2 specification. The drive’s many optional features are described
here and throughout the manual.
Chapter 4
Messages
This chapter provides a list and description of most messages supported
by the tape drive. The SCSI message system allows communication
between SCSI initiators and SCSI targets (the tape drive, in this case)
for interface management and for command elaboration and
qualification.
Chapter 5
SCSI Commands
This chapter describes in detail each command supported by the tape
drive. The SCSI command system enables an initiator to direct a tape
drive to perform a wide range of operational and diagnostic functions.
This chapter also provides sense key information for the REQUEST
SENSE SCSI command.
Appendix A
Definition of Vendor Unique Sense Data Information
Appendix A provides a list of internal status codes related to the
REQUEST SENSE SCSI command.
Appendix B
EEPROM-Resident Bugcheck and Event Logs
Appendix B provides an explanation of the error and event logs stored in
semi-permanent, non-volatile memory.
Appendix C
Updating the Firmware
Appendix C provides a step-by-step procedure for updating a tape drive’s
PCBA controller-resident firmware.
xxii
Quantum DLT 4000 Tape Drive
About This Manual
Appendix D
The Tape Cartridge
Appendix D provides tape cartridge handling and inspection procedures,
information on the write-protect switch, how to load and unload a tape
cartridge, and how to use a cleaning tape cartridge.
CONVENTIONS
This manual uses the following conventions to designate specific elements:
Element
Convention
Example
Commands
Uppercase (unless case-sensitive)
FORMAT UNIT
Messages
Uppercase
INVALID PRODUCT NUMBER
Hexadecimal Notation
Number followed by lowercase h
25h
Binary Notation
Number followed by lowercase b
101b
Decimal Notation
Number without suffix
512
Acronyms
Uppercase
POST
Abbreviations
Lowercase, except where standard
usage requires uppercase
Mb (megabits)
MB (megabytes)
READER COMMENTS
Quantum is committed to providing the best products and service. Our manuals
are important components of our products. We encourage your comments,
suggestions, and corrections for this manual. Please send all comments to:
Quantum Technical Publications
4001 Discovery Drive, Suite 1100
Boulder, CO 80303
Quantum DLT 4000 Tape Drive
xxiii
About This Manual
xxiv
Quantum DLT 4000 Tape Drive
Chapter 1
GENERAL DESCRIPTION AND SPECIFICATIONS
This chapter provides a description and gives specifications for the Quantum DLT™4000 Tape Drive.
1.1
PRODUCT DESCRIPTION
The Quantum DLT 4000 tape drive is a high-performance, high-capacity,
streaming cartridge tape product designed for efficient data back-up for midrange
and high-end computing systems. With Quantum’s DLT advanced linear
recording technology and a precision tape guide system, the drive is ideally
suited for high-end workstation, server, and network backup requirements.
Using data compression, the DLT 4000 tape drive features a formatted capacity
of 40.0 GB* and a sustained user data transfer rate of 3.0 MB/second* (native
capacity is 20.0 GB; native data transfer rate is 1.5 MB/second).
The device is an extended-length, 5.25-inch form factor, half-inch cartridge tape
drive. The design includes a two-channel read/write head, Lempel-Ziv (LZ)
high-efficiency data compression, and tape mark directory to maximize data
throughput and minimize data access time.
The tape drive is available in rackmount (Figure 1-1) or tabletop (Figure 1-2)
form. The tabletop versions of the drive are packaged in a housing that includes
its own cooling fan and power supply, requiring ac power.
Quantum DLT 4000 Tape Drive
1-1
General Description and Specifications
Figure 1-1 Quantum DLT 4000 Tape Drive (Rackmount)
Tabletop Version 1
Tabletop Version 2
Figure 1-2 Quantum DLT 4000 Tape Drive (Tabletop)
1-2
Quantum DLT 4000 Tape Drive
General Description and Specifications
1.2
PRODUCT FEATURES
The DLT 4000 tape drive offers the following product features:
1.3
•
20.0 GB Native, 40.0 GB Compressed Capacity (Formatted capacity
assuming a 2:1 data compression ratio. Note that actual compression ratio
depends on the type of data, SCSI bus limitations, and system
configuration.)
•
Superior Error Detection and Correction
•
Extensive Embedded Diagnostic/Self-Test Software
•
Tape-Loadable Firmware
PRODUCT SPECIFICATIONS
The following subsections contain full specifications for the Quantum DLT 4000
tape drive. Specifications for the DLTtape tape media cartridges are also
included.
1.3.1 Physical Specifications
The following table provides physical dimensions for the DLT 4000.
Table 1–1 DLT 4000 Physical Dimensions
Dimension
Rackmount
Tabletop
(Version 1)
Tabletop
(Version 2)
Height
3.25 in. (8.26 cm) without front
bezel; 3.40 in (8.64 cm) with front
bezel.
5.77 in.
(14.66 cm)
4.88 in.
(12.40 cm)
Width
5.70 in. (14.48 cm) behind front
bezel; 5.84 in (14.83 cm) with front
bezel.
9.25 in.
(23.50 cm)
9.06 in.
(23.01 cm)
Depth
9.00 in. (22.86 cm) measured from
back of front bezel; 9.60 in. (24.38
cm) including front bezel
13.08 in.
(33.22 cm)
12.60 in.
(32.00 cm)
Typical Weight:
6 lb., 7 oz (2.9 kg)
(14 lb., 9 oz) 6.63 kg
Note: Mounting hole pattern for the bottom and sides of the drive is industry standard.
Quantum DLT 4000 Tape Drive
1-3
General Description and Specifications
1.3.2 Interface Type
DLT 4000 tape drives are available with narrow SCSI-2 fast single-ended or
differential high voltage interfaces.
1.3.3
Storage Capacity
The following table provides the ranges of capacity (native and compressed) for
the tape drive, depending on which DLTtape cartridge is used.
Table 1–2
DLTtape Cartridge
(Length of Medium)
DLTtape IV
DLT 4000 Storage Capacity
Native
Storage Capacity
Compressed
Storage Capacity
20.0 GB User Data
40.0 GB User Data
(extended 1780 foot tape)
DLTtape IIIxt
(compressed 2:1)
15.0 GB User Data
(extended 1780 foot tape)
DLTtape III
30.0 GB User Data
(compressed 2:1)
10.0 GB User Data
(standard 1167 foot tape)
20.0 GB User Data
(compressed 2:1)
Note: A compression factor of 2:1 can be attained, depending on the data type and
subject to the limitations of the SCSI bus design and the configuration of the
system in which the tape drive is installed.
1.3.4 Performance Data
The following table provides performance data for the DLT 4000 tape drive.
Table 1–3 DLT 4000 Performance Data
Feature
Description
Transfer Rate, User Native
Transfer Rate, Raw Native
Transfer Rate, Compressed *
1.5 MB/second
2.5
MB/second
More
than 3.0 MB/second maximum write, 10 MBburst
mode; More than 2.5 MB/second maximum read, 10
MBburst mode
Error Rates
Recoverable READ Error Rate = 1 in 1x107
Recoverable WRITE Error Rate = 1 in 1x106
Uncorrected Error Rate = 1 in 1x1017 bits read
Undetected Error Rate = 1 in 1x1027 bits read
* = Depending on data type and SCSI bus limitations/system configuration.
Note that data is typical; times may be longer if error recovery time is needed.
1-4
Quantum DLT 4000 Tape Drive
General Description and Specifications
Table 1–3
DLT 4000 Performance Data (continued)
Feature
Description
Tracks
128; 64 pairs
Linear Bit Density
81,600 bpi per track
READ / WRITE Tape Speed
98 inches/second
Rewind Tape Speed
150 inches/second
Linear Search Tape Speed
150 inches/second
Average Rewind Time
70 seconds
Maximum Rewind Time
140 seconds
Average Access Time (from BOT)
45 seconds
Maximum Access Time (from BOT)
90 seconds
Load to BOT (typical)
48 seconds - previously written (slightly longer if using
a blank tape)
Load to BOT (max time using V120
firmware or greater)
5.2 minutes with blank tape that fails calibration (time
includes calibration retries)
Unload from BOT
17 seconds
Nominal Tape Tension
3.0 +/- 1 oz when stationary;
+/- 1 oz at operating speed
4.7
* = Depending on data type and SCSI bus limitations/system configuration
Note that data is typical; times may be longer if error recovery time is needed.
1.3.5
Environmental Specifications
The following table lists operating and non-operating environmental
specifications for the DLT 4000 tape drive.
Table 1–4 DLT 4000 Environmental Specifications
Specification
Operating Limits
Non-Operating Limits
(Power On; No Tape Loaded)
Wet Bulb Temperature
25°C (77°F)
25°C (77°F)
Dry Bulb Temperature
Range
10°C to 40°C (50°F to 104°F)
-40°C to 66°C (-40°F to 151°F)
Temperature Gradient
11°C (52°F) /hour (across range)
15°C (59°F) /hour (across range)
Temperature Shock
10°C (50°F) (over two minutes)
15°C (59°F) (over two minutes)
Relative Humidity
20 to 80% (noncondensing)
10 to 95% (noncondensing)
Humidity Gradient
10% / hour
10% / hour
Quantum DLT 4000 Tape Drive
1-5
General Description and Specifications
Table 1–4
DLT 4000 Environmental Specifications (continued)
Specification
Operating Limits
Non-Operating Limits
(Power On; No Tape Loaded)
Altitude
Normal pressure from -500 feet to
30,000 feet
Airflow Velocity
125 linear feet per minute
measured directly in front of the
front bezel
Shock
5 G peak, half-sine; 11 ms
duration; 10 G each direction of
each axis, 35 sec between shocks,
60 shocks total; 3 axes
See Table 1-5
Vibration
5 to 500 Hz @ 0.25 G; sweep rate
=1 octave per minute
See Table 1-6
Table 1–5 DLT 4000 Non-Operating Shock Specifications
Description
Rackmount and Tabletop
Shock (Unpackaged)
40 G, 10 ms, square wave;
140 G, 2 ms, half-sine; X,Y,Z
axes, twice in each axis, total of
6 shocks.
Shock (Packaged)
Drop:
42
inches (items < 20.0 lbs.)
16 drops total
Table 1–6 DLT 4000 Non-Operating Vibration Specifications
Description
Rackmount and Tabletop
Sine (Unpackaged)
1-500-10 Hz; 1 G acceleration level; X,Y,Z axes, sweep rate =½
octave/minute
Random (Unpackaged)
5-500 Hz; 2 G acceleration level; X,Y,Z axes, sweep rate = 60
min/axis
Random (Packaged)
Power Spectral Density
(Vertical)
1-6
5 to 10 Hz
0.003 G 2/Hz @ 5, to 0.020 @ 10
10 to 50 Hz
Flat @ 0.020 G 2/Hz
50 to 300 Hz
0.020 G 2/Hz @ 50 with 8 dB/octave rolloff
Quantum DLT 4000 Tape Drive
General Description and Specifications
Table 1–6 DLT 4000 Non-Operating Vibration Specifications (continued)
Description
Rackmount and Tabletop
Power Spectral Density
(Horizontal)
5 to 10 Hz
0.0011 G 2/Hz @ 5, to 0.007 @ 10
10 to 50 Hz
Flat @ 0.007 G 2/Hz
50 to 200 Hz
0.007 G 2/Hz @ 50 with 8 dB/octave rolloff
Each of the X, Y, and Z axes for one hour (3 hours total)
1.3.6
Power Requirements
The following table provides the applicable power requirements for rackmount
and tabletop versions of the DLT 4000 tape drive. Note that the tabletop DLT
4000 requires ac power.
Table 1–7 DLT 4000 Power Requirements
Requirement
Rackmount
Tabletop
Electrical Rating (Auto Ranging)
Not Applicable
100 to 240 VAC
Power Requirements
25 W, steady state;
27 W, maximum
50 W, maximum
+5 V (±5%) bus *
2.0 A, steady state;
2.5 A, maximum
Not applicable
+12 V (±5%) bus *
0.8 A, steady state;
1.5 A, maximum
Not applicable
Power Consumption:
* = Voltage measured at the power bus connector pins.
1.3.7
Electromagnetic Emissions
The rackmount version of the drive complies with FCC Class A in a standard
enclosure; the tabletop version complies with the FCC Class B limits.
Quantum DLT 4000 Tape Drive
1-7
General Description and Specifications
1.3.8
EMI and Safety Certifications
Table 1−8 provides the certifications held by the rackmount and tabletop
versions of the tape drive. Table 1−9 provides the safety certification held by the
tape drives.
Table 1–8 EMI Emission Certificates
Rackmount
Tabletop
CEmark Class A
CEmark Class B
VCCi Class 1
VCCi Class 2
CISPR 22 Class A
CISPR 22 Class B
FCC Class A Devices
FCC Class B Devices
Table 1–9
Safety Certifications
Rackmount and Tabletop
UL
TÜV
MARK
1.3.9
CSA
“BG”
IEC
Reliability (Projected)
Mean time between failures (MTBF) for the tape drive is projected to be 200,000
hours at 100% duty cycle. Head life is 10,000 tape motion hours.
Media durability is projected to be 1,000,000 passes of the tape medium across
the read/write heads (15,000 uses).
Quantum Corporation does not warrant that predicted MTBF is representative
of any particular unit installed for customer use. Actual figures vary from unit
to unit.
1-8
Quantum DLT 4000 Tape Drive
General Description and Specifications
1.3.10 Acoustic Noise Emissions
The following tables provide the tape drive’s acoustic noise emission levels, both
as noise power and sound pressure. Information about acoustic emissions is also
provided in German to fulfill an international requirement.
Table 1-10 Acoustic Noise Emissions, Nominal (English)
Acoustics – Preliminary declared values per ISO9296 and ISO 7779/EN27779
Product
Rackmount
Tabletop
Noise Power Emission Level
Sound Pressure Level
(LNPEc)
(LPAc)
Idle
Streaming
Idle
Streaming
Not applicable
Not applicable
Not applicable
Not applicable
4.6 B
5.1 B
30.0 dB
41.0 dB
[Current values for specific configurations are available from Quantum representatives.
1B = 10 dBA.]
Table 1-11 Acoustic Noise Emissions for German Noise Declaration Law
Schallemissionswerte - VorläufigeWerteangaben nach ISO 9296 und
7779/DIN EN27779:
Gerfdt
Rackmount
Tabletop
ISO
Schalleistungspegel
Schalldruckpegel
LwAd, B
LpAm, dBA (Zuschauerpositionen)
Leerauf
Betrieb
Leerauf
Betrieb
N/A
5,5 B
N/A
45,0 B
5,2 B
5,3 B
39,0 dB
40,0 dB
[Aktuelle Werte für spezielle Ausrüstungsstufen sind über die Quantum Equipment
Vertretungen erhältlich. 1 B = 10 dBA]
1.3.11 Tape Drive Recording Type
The tape drive uses 2 - 7 RLL code with DLT 2000, DLT 2000xt, or DLT 4000
formats; MFM with 2.6 GB / 6.0 GB DLT 260 and DLT 600 formats.
Quantum DLT 4000 Tape Drive
1-9
General Description and Specifications
1.3.12 DLTtape Recording Media Specifications
The following table provides specifications for tape media.
Table 1-12 DLTtape Media Specifications
DLTtape
Media Type
Specifications
DLTtape III
Width:
0.5 in., metal particle
Length: 1200 feet (standard 1167 ft. tape)
Cartridge Dimensions: 4.1 in x 4.1 in x 1.0 in
Shelf Life: 30 years min. @ 20°C & 40% RH (non-condensing)
Usage: 1,000,000 passes (typical office/computer environment)
DLTtape IIIxt
Width:
0.5 in., metal particle
Length: 1800 feet (extended 1780 ft tape)
Cartridge Dimensions: 4.1 in x 4.1 in x 1.0 in
Shelf Life: 30 years min. @ 20°C & 40% RH (non-condensing)
Usage: 1,000,000 passes (typical office/computer environment)
DLTtape IV
Width:
0.5 in., metal particle
Length: 1800 feet (extended 1780 ft. tape)
Cartridge Dimensions: 4.1 in x 4.1 in x 1.0 in
Shelf Life: 30 years min. @ 20°C & 40% RH (non-condensing)
Usage: 1,000,000 passes (typical office/computer environment)
1-10
Quantum DLT 4000 Tape Drive
Chapter 2
HARDWARE IMPLEMENTATION
This chapter describes how to install the internal tape drive or “brick” into a rackmount system. This
includes configuration jumper settings, connector pin assignments, installation instructions, power
and signal cabling descriptions, and operating instructions. This chapter also includes information
on configuring and connecting the tabletop version of the drive into a system.
This chapter covers the following topics:
•
Safety, Handling and Electrostatic Discharge (ESD) Protection (Section 2.1)
describes appropriate guidelines when working with the tape drive.
•
Drive Setup (Section 2.2) describes how to set up the tape drive for SCSI ID,
TERMPWR, and parity checking.
•
Drive Installation (Section 2.3) describes how to mount and install the tape
drive into the system.
•
Drive Connections (Section 2.4) identifies the connectors on the tape drive
including the SCSI, power and optional loader connectors.
•
Drive Controls and Light Emitting Diodes (LED’s) (Section 2.5) identifies
the front panel controls and LED’s and describes their functionality. It also
explains density selection.
•
Power On Self Test (POST) (Section 2.6) describes the activities that occur
when power is first applied to the drive.
•
Troubleshooting (Section 2.7) lists troubleshooting tips in the event that the
tape drive fails.
2.1 SAFETY, HANDLING AND ELECTROSTATIC DISCHARGE (ESD) PROTECTION
Inappropriate or careless handling of tape drives may result in damage to the
product. Follow the precautions and directions to prevent damaging the tape
drive.
Quantum DLT 4000 Tape Drive
2-1
Hardware Implementation
2.1.1 Safety Precautions
For your safety, follow all safety procedures described here and in other sections of
the manual.
2.1.2
•
Remove power from the computer system (or expansion unit) before
installing or removing the tape drive to prevent the possibility of electrical
shock or damage to the tape drive. Unplug the unit that contains or is to
contain the drive from ac power to provide an added measure of safety.
•
Read, understand, and observe any and all label warnings.
Handling
Damage to the drive can occur as the result of careless handling, vibration, shock,
or electrostatic discharge (ESD). Always handle the tape drive with care to avoid
damage to the precision internal components.
Follow these guidelines to avoid damage to the drive:
2-2
•
Always observe prescribed ESD precautions.
•
Keep the drive in its anti-static bag until ready to install.
•
Always use a properly fitted wrist strap or other suitable ESD protection
when handling the drive.
•
Hold drive only by its sides. Do not touch any components on the PCBA.
•
Always handle the drive carefully and gently. A drop of ¼ inch onto a bench
or desktop may damage a drive.
•
Do not bump, jar, or drop the drive. Use care when transporting the drive.
•
Always gently place the drive flat, PCB side down, on an appropriate ESDprotected work surface to avoid the drive being accidentally knocked over.
•
Do not pack other materials with the drive in its anti-static bag.
•
Place the drive in the anti-static bag before placing it in a shipping
container.
•
Do not stack objects on the drive.
•
Do not expose the drive to moisture.
•
Do not place hands or foreign objects inside the tape drive’s door/receiver
area.
Quantum DLT 4000 Tape Drive
Hardware Implementation
2.1.3
Electrostatic Discharge (ESD) Protection
Various electrical components on/within the tape drives are sensitive to static
electricity and Electrostatic Discharge (ESD). Even a static buildup or discharge
that is too slight to feel can be sufficient to destroy or degrade a component's
operation.
To minimize the possibility of ESD-related damage to the drive, we strongly
recommend using both a properly installed workstation anti-static mat and a
properly installed ESD wrist strap. When correctly installed, these devices reduce
the buildup of static electricity that might harm the drive.
Observe the following precautions to avoid ESD-related problems:
2.2
•
Use a properly installed anti-static pad on your work surface.
•
Always use a properly fitted and grounded wrist strap or other suitable ESD
protection when handling the drive and observe proper ESD grounding
techniques.
•
Hold the drive only by its sides. Do not touch any components on the
PCBA.
•
Leave the drive in its anti-static bag until you are ready to install it in the
system.
•
Place the drive on a properly grounded anti-static work surface pad when it
is out of its protective anti-static bag.
•
Do not use the bag as a substitute for the work surface anti-static pad. The
outside of the bag may not have the same anti-static properties as the
inside. It could actually increase the possibility of ESD problems.
•
Do not use any test equipment to check components on the PCBA. There are
no user-serviceable components on the drive.
DRIVE SETUP
Drive setup for DLT 4000 tape drive includes the following:
•
Set the SCSI ID for the drive (default = SCSI ID 5)
•
Configure the drive to provide TERMPWR
•
Set parity checking for the drive (default = parity checking enabled)
If you want to change any of the settings, go to the applicable subsection;
otherwise, proceed directly to section 2.3.
Quantum DLT 4000 Tape Drive
2-3
Hardware Implementation
2.2.1 Set the Rackmount Drive SCSI ID
Each device on the SCSI bus must have a unique SCSI ID address assigned to it.
For specific recommendations for assigning SCSI IDs, refer to the system or SCSI
controller documentation.
Rackmount drives can be configured for SCSI ID addresses that range from 0 to 7
(default=5) in one of two ways:
a) jumper the 10-pin SCSI ID jumper block shown in Figure 2-1, or
b) set the IDs through firmware. If the firmware is set to SCSI ID = 5, then no
jumpers are installed on the SCSI ID jumper block.
This subsection discusses setting the SCSI ID on the rackmount drive via the
jumper block. Table 2-1 lists the SCSI ID address and jumper settings.
NOTES
The default setting for the tape drive is SCSI ID 5; the host adapter is
typically SCSI ID 7.
A jumper must be installed across Pins 9-10 (Remote ID Present pins)
for the host to recognize any SCSI ID selections from this jumper
block.
Front Panel
SCSI ID Jumper Block (J13)
9
1
10
2
Loader Connector (J12)
(default SCSI ID 5 shown)
Figure 2-1 DLT 4000 SCSI ID Jumper Location (Rackmount Version Shown)
2-4
Quantum DLT 4000 Tape Drive
Hardware Implementation
Table 2-1 SCSI ID Address Selections
SCSI ID
0
1
2
3
4
5 (default)
6
7
Jumper Across Pins:
9-10
7-8
5-6
3-4
1-2
1
1
1
1
1
1
1
1
0
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
0 = No Jumper installed
1 = Jumper installed
Quantum DLT 4000 Tape Drive
2-5
Hardware Implementation
2.2.2 Configure the Rackmount Drive for TERMPWR (Single-Ended Only)
A SCSI bus must be terminated at each end of the bus. At least one device must
supply terminator power (TERMPWR). Quantum recommends that every device
on the SCSI bus be configured to supply TERMPWR to ensure that there is a
sufficient level of voltage along the SCSI bus.
Install a jumper across Pins 3 and 4 (Figure 2-2) to enable TERMPWR.
Front Panel
ALDR (J26)
TERMPWR (J24)
Not used
Parity Check (J25)
17
18
1
2
Install Jumper on Pins 1-2
to disable Parity Checking.
25
26
1
2
Install Jumper on Pins 3-4
to enable TERMPWR.
Figure 2-2 DLT 4000 TERMPWR and Parity Check Jumper Locations (Rackmount
Version Shown)
2-6
Quantum DLT 4000 Tape Drive
Hardware Implementation
2.2.3
Configure The Rackmount Drive for Parity Checking
The default setting for DLT 4000 tape drives is to have parity checking enabled.
If the system to which you are configuring the rackmount tape drive does not
generate SCSI parity, there are two ways that parity checking can be disabled.
You can disable parity checking by:
(a) Installing a jumper across Pins 1 and 2 on the parity check connector as
shown in Figure 2-2, or
(b) Installing a jumper across Pins 7 and 8 on the SCSI ID jumper block shown
in Figure 2-1.
2.2.4
Configure the Tabletop Drive
Figures 2-3 and 2-4 show the locations of the controls for the tabletop versions of
the drive. Note that these drives are normally configured to meet customer
specifications before they leave the factory so should not require any internal
configuration changes on-site.
SCSI ID Pushbutton
Figure 2–3 Tabletop (Version 1) Back Panel Controls
Quantum DLT 4000 Tape Drive
2-7
Hardware Implementation
SCSI ID Pushbutton
Power Switch
SCSI Signal
Connector (IN)
SCSI Signal Connector
(Out/Termination)
Power Connector
Figure 2–4 Tabletop (Version 2) Back Panel Controls
SCSI ID - The SCSI ID default for the tabletop drive is set to 5; the drive can be
configured for SCSI ID addresses that range from 0 to 7 using the SCSI ID
pushbutton. Press the button above or below the ID number display to set the
desired SCSI ID. The top button increases the ID number; the bottom button
decreases the ID number.
TERMPWR and/or Parity Check - The tabletop version of the drive can be
internally configured to supply TERMPWR or parity checking. Contact your
service representative if you want to change either of these settings on the
tabletop version of the drive.
2.3
DRIVE INSTALLATION
This section describes how to mount and secure the drive in the system. Figure 2–
5 shows the mounting locations and dimensions for the drive.
2-8
Quantum DLT 4000 Tape Drive
Hardware Implementation
9.60 (24.38)
9.00 (22.86)
3.25
(8.26)
3.40
(8.64)
3.13
(7.94)
0.82
(2.08)
1.88
(4.76)
Front Panel
Side View - Inches (Centimeters)
9.60 (24.38)
5.50
(13.97)
5.84
(14.83)
5.70
(14.48)
0.10
(0.25)
3.13
(7.94)
1.88
(4.78)
Front Panel
Bottom View - Inches (Centimeters)
Figure 2–5 Rackmount Drive Mounting Locations – Side and Bottom Views
Quantum DLT 4000 Tape Drive
2-9
Hardware Implementation
In some systems, it may be more convenient to connect the SCSI bus and power
cables to the drive before securing it in the system.
Because of the variety of mounting possibilities for tape drive, the instructions
presented here are general in nature. They should be used only as a guide for
mounting the drive in your system.
Mount the drive in the system by performing the following steps:
2.4
1.
Position the drive in the system and align the drive mounting holes (side or
bottom) with those in the system.
2.
Using four (4) screws, secure the tape drive in its bay or chassis. Note that
screws used to mount the tape drive must be 8 x 6-32 UNC-2B screws. There
is no danger of these screws touching electronic components or otherwise
damaging the tape drive.
DRIVE CONNECTIONS
The following warning applies to the bezel connector located under the front panel
of the tape drive. This connector is an internal connector so is not discussed in
detail in this manual.
WARNING
The bezel connector pinout on the DLT 4000 tape drive (Model
TH5XB-NP) is not compatible with any other DLT products. A flex
cable adapter is available to connect these tape drives to a
library/loader system that uses header pins for the bezel connection.
Do not use this flex cable adapter to connect to drives other than
the Model TH5XB-NP. The following label has been applied to the
drive to warn the user when making this connection:
WARNING
°
DLT 4000
Drive Side
2-10
DLT 7000 Library
DLT 8000 Library
Quantum DLT 4000 Tape Drive
Hardware Implementation
The three external connectors on the DLT 4000 tape drive that are discussed in
this manual are the SCSI, power and optional loader connectors. Tabletop
connectors are described in subsection 2.4.3.
2.4.1 SCSI and Power Connectors (Rackmount)
Figure 2-6 shows the pin orientation for the 50-pin SCSI connector and 4-pin
power connector located on the back of the tape drive. Pin assignments for the
single-ended and differential SCSI connectors are listed in Tables 2–2 and 2-3; pin
assignments for the power connector are listed in Table 2-4.
Align the appropriate SCSI and power cables to their matching connectors.
Carefully connect the cables, to avoid bending or damaging the connector pins.
Drive Back
Pin 1
SCSI-2 Connector
Pin 1
4-Pin Power Connector
Optional Power
Connector
(Not used)
Figure 2-6 SCSI and Power Cable Connectors (Rackmount Version Shown)
Quantum DLT 4000 Tape Drive
2-11
Hardware Implementation
Table 2–2 Single-Ended SCSI Pin Assignment
Signal Name
Pin Number
Pin Number
Signal Name
Ground
1
2
-DB(0)
Ground
3
4
-DB(1)
Ground
5
6
-DB(2)
Ground
7
8
-DB(3)
Ground
9
10
-DB(4)
Ground
11
12
-DB(5)
Ground
13
14
-DB(6)
Ground
15
16
-DB(7)
Ground
17
18
-DB(P)
Ground
19
20
Ground
Ground
21
22
Ground
Reserved
23
24
Reserved
Open
25
26
TERMPWR
Reserved
27
28
Reserved
Ground
29
30
Ground
Ground
31
32
-ATN
Ground
33
34
Ground
Ground
35
36
-BSY
Ground
37
38
-ACK
Ground
39
40
-RST
Ground
41
42
-MSG
Ground
43
44
-SEL
Ground
45
46
-C/D
Ground
47
48
-REQ
Ground
49
50
-I/O
Note: The minus sign (-) next to a signal indicates active low.
2-12
Quantum DLT 4000 Tape Drive
Hardware Implementation
Table 2–3 Differential SCSI Pin Assignment
Signal Name
Pin Number
Pin Number
Signal Name
Open
1
2
Ground
DB(0)
3
4
-DB(0)
DB(1)
5
6
-DB(1)
DB(2)
7
8
-DB(2)
DB(3)
9
10
-DB(3)
DB(4)
11
12
-DB(4)
DB(5)
13
14
-DB(5)
DB(6)
15
16
-DB(6)
DB(7)
17
18
-DB(7)
DB(P)
19
20
-DB(P)
DIFFSENS
21
22
Ground
Ground
23
24
Ground
TERMPWR
25
26
TERMPWR
Ground
27
28
Ground
ATN
29
30
-ATN
Ground
31
32
Ground
BSY
33
34
-BSY
ACK
35
36
-ACK
RST
37
38
-RST
MSG
39
40
-MSG
SEL
41
42
-SEL
C/D
43
44
-C/D
REQ
45
46
-REQ
I/O
47
48
-i/O
Ground
49
50
Ground
Quantum DLT 4000 Tape Drive
2-13
Hardware Implementation
Table 2–4 4-Pin Power Connector Pin Assignment
Pin Number
Signal Name
1
2
3
4
+12 VDC
Ground (+12 V return)
Ground (+5 V return)
+5 VDC
2.4.2 Optional Loader Connector (Rackmount)
The loader connector provides signals to be used when the tape drive is part of a
loader/library configuration. Figure 2-7 shows the location of the connector.
Front Panel
SCSI ID Jumper Block (J13)
10-Pin Loader Connector (J12)
Figure 2–7 Loader Connector Block Location (Rackmount Version Shown)
2-14
Quantum DLT 4000 Tape Drive
Hardware Implementation
2.4.3
Tabletop Drive Connectors
Figures 2-8 and 2-9 show the locations of the connectors for the tabletop version
of the drive.
SCSI ID Pushbutton
Figure 2–8 Tabletop (Version 1) Back Panel Connectors
Quantum DLT 4000 Tape Drive
2-15
Hardware Implementation
SCSI ID Pushbutton
Power Switch
SCSI Signal
Connector (IN)
SCSI Signal Connector
(Out/Termination)
Power Connector
Figure 2–9 Tabletop (Version 2) Back Panel Connectors
Align the appropriate SCSI and power cables to their matching connectors.
Carefully connect the cables and avoid bending or damaging the connector pins.
1.
Make sure the power switch is in the off (0) position.
2.
Connect one end of the SCSI cable to the SCSI IN connector on the back
panel of the drive. Connect the other end of the SCSI cable to the SCSI
connector on your system, or for daisy-chained configurations, to another
SCSI device.
3.
Snap the wire cable clamps into place to secure the cables.
4.
Be sure to terminate the SCSI bus. If the tabletop drive is the last or only
device on the bus, terminate the bus by connecting the SCSI terminator to
the SCSI OUT connector on the back of the drive. Depending on the
terminator supplied, snap the wire cable clamps into place or tighten the
screws to secure the terminator.
If the tabletop drive is not the last or only device on the bus, install a
terminator on the last device on the SCSI bus.
5.
2-16
Connect one end of the power cord to the power connector on the back of the
drive. Connect the other end of the cord to the ac outlet.
Quantum DLT 4000 Tape Drive
Hardware Implementation
2.5 DRIVE CONTROLS AND LIGHT EMITTING DIODES (LEDS)
This section identifies the front panel controls and LED’s and describes their
functionality. It also explains density selection.
2.5.1
Front Panel Controls and LED’s
This section describes the front panel controls and Light Emitting Diodes
(LED’s) used to operate the tape drive; all controls and LED’s are located on the
tape drive’s front panel. Figure 2-10 shows the locations of the controls and
LED’s on the front panel.
In addition to the controls and LED’s, the tape drive also has an audible beeper
that signals when the drive’s cartridge insert/release handle can be safely used.
Use these controls and LED’s to operate the tape drive and monitor the tape
drive’s activities.
Density LED’s
2.6
Write-Protected LED
6.0
10.0/15.0
Tape In Use LED
20.0
Use Cleaning Tape LED
Compress LED
Operate Handle LED
Density Override LED
Unload Button
Density Select Button
Cartridge Insert/Release
Handle
Figure 2-10 DLT 4000 Front Panel
Quantum DLT 4000 Tape Drive
2-17
Hardware Implementation
Table 2–5 LED Functionality
LED
LED Color
Description
Density 2.6, 6.0,
10.0/15.0, 20.0
Amber
Refer to Table 2-6 and subsection 2.5.2.
Compress
Amber
On = Compression mode enabled (compression only valid for
10, 15, or 20 GB densities only).
Off = Compression mode disabled.
Blinking = Compress mode manually overridden by operator.
Density Override
Amber
On = Operator selected a density from the density Select
Button on the front panel.
Off = Density to be selected by the host (automatic).
Refer to subsection 2.5.2 for Density Select information.
Write-Protected
Orange
On = Tape is Write-Protected
Off = Tape is Write-Enabled
Tape In Use
Amber
Irregular Blinking = Tape is moving; the drive is calibrating,
reading, writing, or rewinding the tape.
Regular Blinking = The tape is loading, unloading, or
rewinding.
On = A cartridge is loaded in the tape drive, but the tape is not
moving; the drive is ready for use. This may also mean no
application is communicating with the tape drive’s controller,
or that the application is communicating but is not delivering
any command that impact tape motion.
2-18
Quantum DLT 4000 Tape Drive
Hardware Implementation
Use Cleaning
Tape
Amber
On = Tape drive needs cleaning or tape is bad.
Remains on after cleaning tape unloads = Cleaning tape
attempted to clean the drive head, but the tape expired so
cleaning was not done.
After cleaning, LED lights again when (data) tape cartridge is
reloaded = Problem tape cartridge. Try another cartridge. If
problem persists, contact service representative.
Off = Cleaning is complete or cleaning is unnecessary.
Appendix D has more information on cleaning tape usage.
Quantum DLT 4000 Tape Drive
2-19
Hardware Implementation
Table 2–5 LED Functionality (continued)
LED
Operate Handle
LED Color
Green
Description
On = Insert/Release handle can be operated.
Off = Do not operate Insert/Release handle.
Blinking = Close the Insert/Release handle and wait for
Operate Handle LED to light steadily.
Table 2–6 Density LED Functionality
Density LED
(Amber)
Description
2.6
On = Tape is recorded in 2.6 GB format.
Blinking = Tape is being forced by operator to record in this density; 2.6 GB
has been selected for a WRITE from BOT.
6.0
On = Tape is recorded in 6.0 GB format.
Blinking = Tape is being forced by operator to record in this density; 6.0 GB
has been selected for a WRITE from BOT.
10.0 / 15.0
On = Tape is recorded in 10.0 GB (DLTtape III cartridge) / 15.0 GB (DLTtape
IIIxt cartridge) format.
Blinking = Tape is being forced by operator to record in this density, 10.0
GB / 15.0 GB has been selected for a WRITE from BOT.
20.0
On = Tape is recorded in 20.0 GB (DLTtape IV cartridge) format.
Blinking = Tape is being forced by operator to record in this density, 20.0 GB
has been selected for a WRITE from BOT.
Note that these LED’s operate only if the correct media is loaded in the drive. For example,
the default density of a DLTtape IV cartridge is 20.0 GB; if you are using a DLTtape IV
cartridge, the density must be set to 20.0 GB. If you set the density to a different setting, the
LED’s do not light and the density function does not work properly.
2-20
Quantum DLT 4000 Tape Drive
Hardware Implementation
Table 2-7 Control Functionality
Control
Description
Density Select Button
Refer to subsection 2.5.2.
Unload Button
Use the Unload button to unload the tape cartridge. When you
push the Unload button, the tape drive waits until any active
writing of data to tape is completed, then begins its unload
sequence.
The tape drive rewinds the tape medium back into the cartridge.
The tape must be completely rewound and unloaded into the
cartridge before the cartridge can be removed from the tape drive.
A complete unload operation may take 17 seconds from Beginning
of Tape (BOT).
Note that if the tape drive is in an error state (all LED’s on the righthand side of the front panel are flashing), pushing the Unload
button causes the tape drive to reset and unload the tape, if
possible. The Operate Handle LED will be lit steady if this is
possible.
Cartridge Insert/Release
Handle
Use the Cartridge Insert/Release Handle to load or eject a tape
cartridge only when the tape drive’s Operate Handle LED is lit and
after the beeper sounds its tone. Lift the handle to its open
position, or lower it to its closed position.
Audible Beeper
A beeper sound indicates that the cartridge insert/release handle
can be safely operated. When the drive emits its single beep tone,
verify that the green Operate Handle LED is lit steadily before
opening the handle.
CAUTION: To prevent damage to the tape drive, never operate the
insert/release handle unless the green Operate Handle LED is lit and
you have heard the beep tone that signals that the tape drive’s
handle can be opened.
Quantum DLT 4000 Tape Drive
2-21
Hardware Implementation
2.5.2
Selecting Density
This subsection describes the drive’s density select features.
CAUTION
If a prerecorded tape is reused and a WRITE from the beginning of
tape (BOT) executes (No Append Write), any data already recorded
on the tape will be lost. This includes density changes, since they
occur only when writing from BOT.
NOTES
On all READ and all WRITE APPEND operations, the data density that
already exists on the tape cartridge remains the density.
Default density of a DLTtapeTM III cartridge is 10.0 GB, native. The
only optional selections for DLTtape III cartridges are 2.6 GB, 6.0 GB,
10.0 GB (compression OFF), or 20.0 GB (compression ON).
Default density of a DLTtape IIIxt cartridge is 15.0 GB, native
(compression OFF), or 30.0 GB (compression ON). No other density is
supported.
Default density of a DLTtape IV cartridge is 20.0 GB, native
(compression OFF). A density of 40.0 GB is user-selectable. No other
density is supported.
When writing from BOT, tape density may be changed by:
2-22
•
Using the Density Select Button on the front panel of the tape drive. Using
the Density Select Button always overrides density selection via the host.
•
Using the operating system to issue a density designation. In this case, the
amber Density Override LED on the tape drive’s front panel turns off,
indicating an automatic or host density selection.
•
Native default density for the DLTtape IV is 20.0 GB. The only available
option is compression on or off.
Quantum DLT 4000 Tape Drive
Hardware Implementation
Selecting Density on the Tape Drive
To select density on the tape drive:
1.
Load the tape cartridge into the tape drive. The amber Tape in Use LED
blinks while the tape loads and calibrates.
2.
After calibration is complete, the Tape In Use LED remains steadily lit. The
appropriate tape density LED along the left edge of the drive’s front panel
lights to indicate the tape’s prerecorded density (if any), such as 2.6 GB or
6.0 GB.
3.
Use the tape drive’s density Select Button to select the desired density, if
different than that indicated by the lighted tape density LED. Density
selection is inactive until a WRITE from BOT is issued. The controller
retains the selected density until 1) the density selection is changed, or 2)
the tape is unloaded.
Selecting Density via the Host over the SCSI Bus
1.
Use the SCSI MODE SELECT command to indicate the desired density
(Chapter 5).
2.
Write data to the tape from BOT.
For Example:
A user loads a tape cartridge previously recorded at 2.6 GB density. The user then
presses the Density Select button to select 10.0 GB density. The following events
take place:
•
The amber 2.6 LED remains lit – the density has not yet changed and the
steadily lit LED reflects the tape’s recorded density.
•
The amber 10.0 LED blinks – this signals that a density change is pending.
•
The amber Density Override LED lights.
When a WRITE from BOT occurs:
•
The amber 2.6 LED turns off
•
The amber 10.0/15.0 LED lights steadily
•
The amber Density Override LED remains lit
Table 2-8 explains the activity of LED’s during density selection.
Quantum DLT 4000 Tape Drive
2-23
Hardware Implementation
Table 2–8 LED Activity During Density Selection
2.6
If…
Then…
The density Select Button
is not used
The lighted LED’s show the actual density when the tape is
being read from and written to. The LED’s light steadily;
Density Override LED remains off.
The density Select Button
is used and the actual
tape density is the same
as the density selected
via the button
The LED’s that reflect the actual density and the Density
Override both are lit. For example, if the actual density is
10.0 GB and 10.0 GB is selected via the Select Button, the
LED next to “10.0” lights.
The density Select Button
is used and the actual
tape density differs from
the density selected via
the button
The LED that reflects the actual density lights steadily. The
LED that reflects the SELECTED density blinks. The Density
Override lights steadily.
For example, if the actual tape density is 10.0 GB and the
selected density is 6.0 GB, the 10.0 LED lights steadily, the
6.0 LED blinks, and the Density Override LED lights steadily.
POWER ON SELF TEST (POST)
When power is applied to the tape drive, the drive performs a POST. POST
completes in about 15 seconds and the tape drive should respond normally to all
commands; POST is complete after Stage 2 in Table 2-9. However, it might take
longer for the media to become ready.
After a bus reset, the tape drive responds within a bus selection time-out period
(per the ANSI SCSI specification).
The following table lists the sequence of events:
2-24
Quantum DLT 4000 Tape Drive
Hardware Implementation
Table 2–9 POST/Media Ready Activity
Stage
Activity
1
The LED’s along the right-hand side of the front panel light in sequence from
top to bottom. All LED’s remain lit for a few seconds.
2
The LED’s along the left-hand side of the front panel light together for about
three seconds, then turn off. POST is complete after this stage.
3
The green Operate Handle, orange Write Protected, and amber User Cleaning
Tape LED’s turn off. The amber Tape in Use LED blinks while the tape drive
initializes.
4
Following initialization, the tape drive is in one of the states described in Table
2-10. Upon completion, the POST is successful. If the POST is not successful,
refer to Section 2.8 Troubleshooting.
Table 2–10 Tape Drive States Following Initialization
State
LED Display and Activity
A tape cartridge is present and
the handle is down.
The tape drive loads the medium from the cartridge. The
Tape In Use LED stops blinking and remains on. The LED next
to the tape’s actual density is on. When the Density Override
LED blinks, a density may be selected. The tape drive is ready
for use and the media is positioned at BOT.
No tape cartridge present.
The Tape in Use LED = Off. The Operate Handle LED = On.
Insert/Release Handle is unlatched. Tape drive beeper sounds
tone to signal that the handle may be raised and a tape
cartridge inserted.
A tape cartridge is present, but
the handle is up (not
recommended).
The Tape In Use LED = Off. The Operate Handle LED flashes.
When the Insert/Release Handle is lowered, the cartridge
loads. If handle will not lower, ensure the tape cartridge is
pushed all the way into the tape drive.
The tape drive detects an error
condition.
Right- or left-hand LED’s blink repeatedly. Try to unload the
tape and reinitialize the tape drive by pressing the Unload
button or turn the drive power off then back on. The LED’s
stop blinking and the drive attempts to reinitialize. Note that
after pressing the Unload button you may have to wait five
minutes before the Operate Handle LED lights due to the
retry. The LED’s light steadily, then turn off if the test
succeeds.
The drive is powered on with
the handle in open position.
Operate Handle LED is blinking. Close the Insert/Release
Handle and wait for LED to light steadily.
Quantum DLT 4000 Tape Drive
2-25
Hardware Implementation
2.7 TROUBLESHOOTING
Table 2-11 lists troubleshooting tips in the event that your tape drive fails its
power-on self test or if it signals a problem via its front panel LED’s.
If, after attempting the recommended actions listed in Table 2-11, the problem still
exists or recurs, a hardware failure may be the cause. Contact your service
representative.
Table 2–11 Troubleshooting Chart
If…
Then…
You Should…
System does not
recognize the tape
drive.
System may not be
configured to recognize the
SCSI ID.
Configure system to recognize the tape
drive’s ID.
SCSI ID may not be unique
Change the SCSI ID and reconfigure the
system. The new ID becomes effective at
the next power on.
SCSI adapter parameters may
not be correct
Check SCSI adapter documentation.
SCSI signal cable may be loose
Ensure SCSI cable is fully seated at each
connector end.
SCSI terminator may be loose
or not present on the bus
Ensure correct, secure termination of
bus.
SCSI bus may not be
terminated correctly
If tape drive is last or only device on bus
(except for adapter), make sure
terminator is installed on tape drive.
If tape drive is not the last or only device
on the bus, check the cable connections
and ensure that the bus is properly
terminated at each end.
2-26
SCSI terminator may not be at
end of bus or more than two
terminators may be present.
Ensure that a terminator is installed at
each end of the bus. One terminator is
usually installed at the host end of the
bus.
SCSI bus may be too long.
Limit bus length to ANSI SCSI standard
for the SCSI interface being used.
Too many devices on the bus.
Limit the number of devices on the bus
(including the SCSI adapter) to match the
limits of the interface being used.
Quantum DLT 4000 Tape Drive
Hardware Implementation
Table 2–11 Troubleshooting Chart (Continued)
If…
Then…
You Should…
System does not
recognize the tape
drive (cont.)
A device may not have been
turned on and a valid SCSI ID
may not have been
configured prior to the system
powering on and loading
BIOS.
Turn drives power on first, and then turn
on power to the system. Do this so that
the drive is properly recognized by the
system.
The tape drive does
not power up.
No power is reaching the tape
drive.
Check the tape drive’s power cable
connection at the rear of the drive.
All LED’s on the right
or on the left side of
the tape drive front
panel are blinking.
A drive fault has occurred.
If a tape was loaded, try to unload the
tape and reinitialize the drive by pressing
the Unload button, or by turning power
to the drive off then back on. The LED’s
stop blinking as the drive attempts to
reinitialize. The LED’s light steadily again,
then extinguish if the test succeeds. Be
sure to isolate the tape that was loaded
in the drive and perform the Tape
Cartridge Inspection Procedure described
in appendix D.2.
When loading a tape
cartridge, the LED’s on
the right side of the
tape drive front panel
are blinking.
The tape drive has detected a
possible drive leader problem.
Isolate the tape cartridge from all other
tape devices; not doing so may damage
another tape device. Perform the Tape
Cartridge Inspection Procedure described
in appendix D.2 on the tape cartridge.
Contact your service representative.
Nonfatal or fatal errors
occur for which the
cause cannot be
determined.
SCSI bus termination or the
SCSI bus cable connections
may be incorrect.
Ensure the SCSI bus is terminated and
that all connections are secure.
The ac power source
grounding may be incorrect
(tabletop version).
Use
an ac outlet for the tabletop tape unit on
the same ac line used by the host system.
Quantum DLT 4000 Tape Drive
2-27
Hardware Implementation
2-28
Quantum DLT 4000 Tape Drive
Chapter 3
SCSI DESCRIPTION
This chapter provides a detailed description of the logical interfaces of the tape drive. The drive is
fully compliant with the ANSI SCSI-2 standard for tape drive devices and implements many optional
features.
3.1
SCSI OVERVIEW
The Small Computer System Interface (SCSI) is a specification for a peripheral
bus and command set that is an ANSI standard. The standard defines an I/O
bus that supports up to eight devices (narrow SCSI).
ANSI defines three primary objectives of SCSI-2:
1.
To provide host computers with device-independence within a class of
devices
2.
To be backward-compatible with SCSI-1 devices that support bus parity
and that meet conformance level 2 of SCSI-1
3.
To move device-dependent intelligence to the SCSI-2 devices
Important features of SCSI-2 implementation include the following:
•
•
3.2
Efficient peer-to-peer I/O bus with up to 16 devices
Asynchronous transfer rates that depend only on device implementation
and cable length
•
Logical addressing for all data blocks (rather than physical addressing)
•
Multiple initiators and multiple targets
•
Distributed arbitration (bus contention logic)
•
Command set enhancement
SCSI COMMANDS
ANSI classifies SCSI commands as mandatory, optional, or vendor-specific. The
mandatory and optional commands implemented for the drives are summarized
in Table 3–1 and described fully in Chapter 5, SCSI Commands.
Quantum DLT 4000 Tape Drive
3-1
SCSI Description
Table 3–1 Implemented ANSI SCSI-2 Commands
3-2
Command
Code
Class
Description
Erase
19h
Mandatory
Causes all of the tape medium to be
erased, beginning at the current position
on the logical unit.
INQUIRY
12h
Mandatory
Requests that drive information be sent
to the initiator. The initiator may also
request additional information about
the drive.
LOAD UNLOAD
1Bh
Optional
Requests that the target enable or
disable the logical unit for further
operations. Prior to performing the load
unload, the target ensures that all data,
filemarks, and/or setmarks shall have
transferred to the tape medium.
LOCATE
2Bh
Optional
Causes the target to position the logical
unit to the specified block address in a
specified partition. When complete, the
logical position is before the specified
position. Prior to performing the load
unload, the target ensures that all data,
filemarks, and/or setmarks shall have
transferred to the tape medium.
LOG SELECT
4Ch
Optional
Provides a means for the initiator to
manage statistical information
maintained by the drive about the drive.
This standard defines the format of the
log pages but does not define the exact
conditions and events that are logged.
LOG SENSE
4Dh
Optional
Provides a means for the initiator to
retrieve statistical information
maintained by the drive about the drive.
Quantum DLT 4000 Tape Drive
SCSI Description
Table 3–1 Implemented ANSI SCSI-2 Commands (continued)
Command
Code
Class
Description
MODE SELECT (6)
15h
Optional
Provides a means for the initiator to
specify device parameters.
MODE SENSE (6)
1Ah
Optional
Provides a means for a drive to report
parameters to the initiator.
PREVENT ALLOW
1Eh
Optional
Requests that the target enable or
disable the removal of the medium in
the logical unit. Medium cannot be
removed if any initiator has medium
removal prevented.
READ
08h
Mandatory
Requests the drive to transfer data to the
initiator.
READ BLOCK LIMITS
05h
Mandatory
Requests that the logical unit’s block
length limits capability be returned
READ BUFFER
3Ch
Optional
Used in conjunction with the WRITE
BUFFER command as a diagnostic
function for testing target memory and
the integrity of the SCSI bus. This
command does not alter the medium.
READ POSITION
34 h
Optional
Reports the current position of the
logical unit and any data blocks in the
buffer.
RECEIVE DIAG
RESULTS
1Ch
Optional
Requests analysis data to be sent to the
initiator after completion of a SEND
DIAGNOSTIC Command.
RELEASE UNIT
17h
Mandatory
Used to release a previously reserved
logical unit.
REQUEST SENSE
03h
Mandatory
Requests the drive to transfer sense data
to the initiator.
RESERVE UNIT
16h
Mandatory
Used to reserve a logical unit.
SEND DIAGNOSTIC
1Dh
Mandatory
Requests the drive to perform diagnostic
operations on itself.
MEDIUM REMOVAL
Quantum DLT 4000 Tape Drive
3-3
SCSI Description
Table 3–1 Implemented ANSI SCSI-2 Commands (continued)
Command
Code
Class
Description
SPACE
11h
Mandatory
Provides a selection of positioning
functions (both forward and backward)
that are determined by the code and
count.
TEST UNIT READY
00h
Mandatory
Provides a means to check if the logical
unit is ready.
VERIFY
2Fh
Optional
Requests the drive to verify the data
written to the medium.
WRITE
0Ah
Optional
Requests the drive to write the data
transferred from the initiator to the
medium.
WRITE BUFFER
3Bh
Optional
Used in conjunction with the READ
BUFFER command as a diagnostic for
testing target memory and the integrity
of the SCSI bus.
Used to update drive firmware from the
host via the SCSI bus.
WRITE FILEMARKS
3.3
10h
Mandatory
Requests that the target write the
specified number of filemarks or
setmarks to the current position on the
logical unit.
SIGNAL STATES
The following paragraphs describe signal values and SCSI ID bits.
3.3.1 Signal Values
All signal values are actively driven true (low voltage). Because the signal
drivers are OR-tied, the bus terminator’s bias circuitry pulls false when it is
released by the drivers at every SCSI device. If any device asserts a signal, (e.g.,
OR-tied signals), the signal is true. Table 3–2 shows the ANSI-specified and
defined signal sources. Any device can assert RST at any time.
3-4
Quantum DLT 4000 Tape Drive
SCSI Description
Table 3–2 Signal Sources
Signals
Bus Phase
BSY
SEL
C/D I/O
MSG REQ
ACK ATN
DB(7–0)
DB(P)
DB(15-8)
DB(P1)
BUS FREE
None
None
None
None
None
None
ARBITRATION
All
Winner
None
None
S ID
S ID
SELECTION
I&T
Init
None
Init
Init
Init
RESELECTION
I&T
Targ
Targ
Init
Targ
Targ
COMMAND
Targ
None
Targ
Init
Init
None
DATA IN
Targ
None
Targ
Init
Targ
Targ
DATA OUT
Targ
None
Targ
Init
Init
Init
STATUS
Targ
None
Targ
Init
Targ
None
MESSAGE IN
Targ
None
Targ
Init
Targ
None
MESSAGE OUT
Targ
None
Targ
Init
Init
None
All:
The signal is driven by all SCSI devices that are actively arbitrating.
SCSI ID: Each SCSI device that is actively arbitrating asserts its unique SCSI ID bit. The other
seven (or fifteen) data bits are released. The parity bit DB (P or P1) can be released or
driven true, but is never driven false during this phase.
I&T:
The signal is driven by the initiator, drive, or both, as specified in the SELECTION and
RESELECTION phase.
Init:
If driven, this signal is driven only by the active initiator.
None:
The signal is released; that is, not driven by any SCSI device. The bias circuitry of the bus
terminators pulls the signal to the false state.
Winner: The signal is driven by the winning SCSI device.
Targ:
If the signal is driven, it is driven only by the active drive.
Quantum DLT 4000 Tape Drive
3-5
SCSI Description
3.3.2 SCSI ID Bits
SCSI permits a maximum of eight SCSI devices on a SCSI bus (16 devices are
permitted when using wide SCSI). Each SCSI device has a unique SCSI ID
assigned to it. This SCSI ID provides an address for identifying the device on the
bus. On the drive, the SCSI ID is assigned by configuring jumpers or connecting
remote switches to the option connector. Chapter 2, Hardware Implementation
has full instructions for setting the SCSI ID.
3.4
SCSI SIGNALS
The following paragraphs define SCSI signals and bus timing values.
3.4.1 SCSI Signal Definitions
Table 3–3 defines the SCSI bus signals.
Table 3–3 SCSI-2 Bus Signal Definitions
3-6
Signal
Definition
ACK
(acknowledge)
A signal driven by the initiator as an acknowledgment of receipt of
data from a target or as a signal to a target indicating when the target
should read the data (out) lines.
ATN (attention)
A signal driven by an initiator to indicate that it has a message to send.
BSY (busy)
An OR-tied signal that indicates that the bus is in use.
C/D
(control/data)
A signal driven by a target that indicates whether CONTROL or DATA
information is on the DATA BUS. True (low voltage) indicates
CONTROL.
DB(7–0,P)
(data bus)
Eight data-bit signals, plus a parity-bit signal that form a DATA BUS.
DB(7) is the most significant bit and has the highest priority (8 or 16bit) during ARBITRATION. Bit number, significance, and priority
decrease downward to DB(0). A data bit is defined as 1 when the
signal value is true (low voltage) and 0 when the signal value is false
(high voltage). Data parity DB(P) is odd. Parity is undefined during
ARBITRATION.
Quantum DLT 4000 Tape Drive
SCSI Description
Table 3–3 SCSI-2 Bus Signal Definitions (continued)
Signal
Definition
DB(15–8,P1)
(data bus)
Eight data-bit signals, plus one parity-bit signal, that forms an
extension to the DATA BUS. They are used for 16-bit (wide) interfaces.
DB(15) is the most significant bit and has the higher priority (but
below bit DB(0) during ARBITRATION. Bit number, significance, and
priority decrease downward to DB(8). Data Parity DB (P1) is odd.
I/O
(input/output)
A signal driven by a target that controls the direction of data
movement on the DATA BUS with respect to an initiator. True indicates
input to the initiator.
Also used to distinguish between SELECTION and RESELECTION modes.
MSG (message)
A signal driven by a target during the MESSAGE phase.
REQ (request)
A signal driven by a target to indicate a request for an information
transfer to or from the initiator. Each byte of data transferred is
accompanied with a REQ/ACK “handshake”. See also, ACK.
RST (reset)
An OR-tied signal that initiates a RESET condition.
SEL (select)
An OR-tied signal used by an initiator to select a target or by a target to
reselect an initiator.
3.4.2 Signal Bus Timing
The ANSI SCSI-2 standard defines the SCSI bus timing values shown in Table
3–4.
Quantum DLT 4000 Tape Drive
3-7
SCSI Description
Table 3–4 SCSI Bus Timing Values
Timing Description
Value
Description
Arbitration Delay
2.4 µs
Minimum time a SCSI device waits from asserting BSY
for arbitration until the DATA BUS can be examined to
see if arbitration has been won; there is no maximum
time.
Assertion Period
90 ns
Minimum time a drive asserts REQ while using
synchronous data transfers; also, the minimum time
that an initiator asserts ACK while using synchronous
data transfers.
Bus Clear Delay
800 ns
Maximum time for a SCSI device to stop driving all
bus signals after:
1.
BUS FREE is detected.
2.
SEL is received from another SCSI device during
ARBITRATION.
3. Transition of RST to true.
For condition 1, the maximum time for a SCSI device
to clear the bus is 1200 ns (1.2 µs) from BSY and SEL
first becoming both false.
If a SCSI device requires more than a bus settle delay
to detect BUS FREE, it clears the bus within a bus clear
delay minus the excess time.
Bus Free Delay
800 ns
Maximum time a SCSI device waits from its detection
of BUS FREE until its assertion of BSY when going to
ARBITRATION.
Bus Set Delay
1.8 µs
Maximum time for a device to assert BSY and its SCSI
ID bit on the DATA BUS after it detects BUS FREE to
enter ARBITRATION.
Bus Settle Delay
400 ns
Minimum time to wait for the bus to settle after
changing certain control signals as called out in the
protocol definitions.
Cable Skew Delay
10 ns
Maximum difference in propagation time allowed
between any two SCSI bus signals measured between
any two SCSI devices.
1
3-8
Recommended Time.
Quantum DLT 4000 Tape Drive
SCSI Description
Table 3–4 SCSI Bus Timing Values (continued)
Timing Description
Value
Description
Data Release Delay
400 ns
Maximum time for an initiator to release the DATA
BUS signals following the transition of the I/O signal
from false to true.
Deskew Delay
45 ns
Minimum time required to wait for all signals
(especially data signals) to stabilize at their correct,
final value after changing.
Disconnection Delay
200 µs
Minimum time that a drive waits after releasing BSY
before participating in an ARBITRATION when
honoring a DISCONNECT message from the initiator.
Hold Time
45 ns
Minimum time added between the assertion of REQ
or ACK and changing the data lines to provide hold
time in the initiator or drive while using standard
(slow) synchronous data transfers.
Negation Period
90 ns
Minimum time that a drive negates REQ while using
synchronous data transfers; also, the minimum time
than an initiator negates ACK while using
synchronous data transfers. 1
Power-On to
Selection
10 s1
Recommended maximum time from power
application until a drive is able to respond with
appropriate status and sense data to the TEST UNIT
READY, INQUIRY, and REQUEST SENSE commands.
Reset to Selection
Time
250
ms1
Recommended maximum time after a hard RESET
condition until a drive is able to respond with
appropriate status and sense data to the TEST UNIT
READY, INQUIRY, and REQUEST SENSE commands.
Reset Hold Time
25 µs
Minimum time for which RST is asserted; there is no
maximum time.
Selection Abort Time
200 µs
Maximum time that a drive (or initiator) takes from its
most recent detection of being selected (or
reselected) until asserting a BSY response.
1
Recommended Time.
Quantum DLT 4000 Tape Drive
3-9
SCSI Description
Table 3–4 SCSI Bus Timing Values (continued)
Timing Description
Value
Description
Selection Time-Out
Delay
250
ms1
Recommended minimum time a SCSI device should
wait for a BSY response during SELECTION or
RESELECTION before starting the time-out procedure.
Transfer Period
(set during an SDTR
message.)
1
3.5
Minimum time allowed between the leading edges of
successive REQ pulses and of successive ACK pulses
while using standard or fast synchronous data
transfers. The period range is 200 to 500ns minimum,
standard, or 100 to 500ns minimum, fastsynchronous.
Recommended Time.
SCSI BUS PHASES
The SCSI architecture includes eight distinct phases:
1.
BUS FREE phase
2.
ARBITRATION phase
3.
SELECTION phase
4.
RESELECTION phase
5.
COMMAND phase
6.
DATA phases (In/Out)
7.
STATUS phase
8.
MESSAGE phases (In/Out)
The last four phases are called the “information transfer phases”.
The SCSI bus can never be in more than one phase at any given time. In the
following descriptions, signals that are not mentioned are not asserted.
3.5.1 BUS FREE Phase
The BUS FREE phase indicates that there is no current I/O process and that the
SCSI bus is available for a connection.
SCSI devices detect the BUS FREE phase after the SEL and BSY signals are
both false for at least one bus settle delay.
3-10
Quantum DLT 4000 Tape Drive
SCSI Description
During normal operation, the BUS FREE phase is entered when the drive
releases the BSY signal. However, the BUS FREE phase can be entered following
the release of the SEL signal after a SELECTION or RESELECTION phase timeout. BUS FREE might be entered unexpectedly. If, for example, an internal
hardware or firmware fault makes it unsafe for the tape drive to continue
operation without a full reset (similar to a power-up reset), or if ATN is asserted
or a bus parity error is detected during non-tape data transfers.
CAUTION
Any occurrence of a bus parity error (i.e., a single-bit error) should
be considered serious: it implies the possibility of undetected
double-bit error may exist on the bus. This may cause undetected
data corruption. On properly configured SCSI buses, parity errors
are extremely rare. If any are detected they should be addressed by
improving the configuration of the SCSI bus. A well-configured SCSI
bus in a normal environment should be virtually free of bus parity
errors.
Bus parity errors cause the tape drive to retry the operation, go to
the STATUS phase, or go to BUS FREE and prepare Sense Data.
Retrying of parity errors during Data Out Phase when writing is
normally not done, but can be enabled by changing the
EnaParErrRetry parameter in the VU EEROM Mode Page. This feature
is not enabled by default because of possible negative impact on
device performance (the data stream on writes cannot be pipelined
as well).
Initiators normally do not expect the BUS FREE phase to begin because of the
drive’s release of the BSY signal unless it has occurred after the detection of a
reset condition or after a drive has successfully transmitted or received one of
the following messages:
Messages Transmitted from Drive:
•
DISCONNECT
•
COMMAND COMPLETE
Quantum DLT 4000 Tape Drive
3-11
SCSI Description
Messages Received by Drive:
•
ABORT
•
BUS DEVICE RESET
•
RELEASE RECOVERY
If an initiator detects the release of the BSY signal by the drive at any other
time, the drive is indicating an error condition to the initiator. The drive can
perform this transition to the BUS FREE phase independently of the state of the
ATN signal. The initiator manages this condition as an unsuccessful I/O
process termination. The drive terminates the I/O process by clearing all pending
data and status information for the affected nexus. The drive can optionally
prepare sense data that can be retrieved by a REQUEST SENSE command.
Bus Free Sequence
1.
BSY and SEL signals are continuously false for one bus settle delay.
2.
SCSI devices release all SCSI bus signals within one bus clear delay.
If a SCSI device requires more than one bus settle delay to detect the BUS FREE
phase, then it releases all SCSI bus signals within one bus clear delay minus the
excess time to detect the BUS FREE phase.
The total time to clear the SCSI bus cannot exceed one bus settle delay plus one
bus clear delay.
3.5.2 ARBITRATION Phase
The ARBITRATION phase allows one SCSI device to gain control of the SCSI
bus so that it can initiate or resume an I/O process.
The SCSI device arbitrates for the SCSI bus by asserting both the BSY signal
and its own SCSI ID after a BUS FREE phase occurs.
Arbitration Sequence
3-12
1.
The SCSI device waits for the BUS FREE phase to occur.
2.
The SCSI device waits a minimum of one bus free delay after detection of the
BUS FREE phase before driving any signal.
3.
The SCSI device arbitrates for the SCSI bus by asserting the BSY signal and
its SCSI ID.
Quantum DLT 4000 Tape Drive
SCSI Description
4.
The SCSI device waits at least an arbitration delay to determine arbitration
results.
NOTE
Step 4 requires that every device complete the arbitration phase to
the point of SEL being asserted (for a SELECTION or RESELECTION
phase) to avoid hanging the bus.
•
If a higher priority SCSI ID bit is true on the DATA BUS, the SCSI
device loses the arbitration.
•
The losing SCSI device releases the BSY signal and its SCSI ID bit
within one bus clear delay after the SEL signal asserted by the
arbitration winner becomes true.
•
The losing SCSI device waits for the SEL signal to become true
before releasing the BSY signal and SCSI ID bit when arbitration is
lost.
•
The losing SCSI device returns to Step 1.
•
If no higher priority SCSI ID bit is true on the DATA BUS, the SCSI
device wins the arbitration and asserts the SEL signal.
•
The winning SCSI device waits at least one bus clear delay plus one
bus settle delay after asserting the SEL signal before changing any
signals.
3.5.3 SELECTION Phase
The SELECTION phase allows an initiator to select a drive to initiate a drive
function.
The SCSI device that won the arbitration has both the BSY and SEL signals
asserted and has delayed at least one bus clear delay plus one bus settle delay
before ending the ARBITRATION phase. The SCSI device that won the
arbitration becomes an initiator by not asserting the I/O signal.
During SELECTION, the I/O signal is negated so that this phase can be
distinguished from the RESELECTION phase.
Quantum DLT 4000 Tape Drive
3-13
SCSI Description
3.5.3.1 Selection Sequence
The initiator:
1.
Sets the DATA BUS to the OR of its SCSI ID bit and the drive’s SCSI ID
bit.
2.
Asserts the ATN signal (signaling that a MESSAGE OUT phase is to follow
the SELECTION phase).
3.
Waits at least two deskew delays.
4.
Releases the BSY signal.
5.
Waits at least one bus settle delay.
6.
Looks for a response from the drive.
The drive:
7.
Determines that it is selected when the SEL signal and its SCSI ID bit are
true and the BSY and I/O signals are false for at least one bus settle delay.
8.
Can examine the DATA BUS to determine the SCSI ID of the selecting
initiator.
9.
Asserts the BSY signal within a selection abort time of its most recent
detection of being selected (this is required for correct operation of the
selection time-out procedure).
The drive does not respond to a selection if bad parity is detected. Also, if more
than two SCSI ID bits are on the DATA BUS, the drive does not respond to
selection.
Note that the initiator will release the SEL signal and may change the DATA
BUS no less than two deskew delays after it detects that the BSY signal is true.
The drive waits until the SEL signal is false before asserting the REQ signal to
enter an information transfer phase. Other signals (e.g., MSG, C/D) may also
be asserted.
3.5.3.2 Selection Time-Out
Two optional time-out procedures are specified for clearing the SCSI bus if the
initiator waits a minimum of a selection time-out delay and there has been no
BSY signal response from the drive.
3-14
Quantum DLT 4000 Tape Drive
SCSI Description
The initiator asserts the RST signal.
1.
The initiator follows these steps:
a) Continues asserting the SEL and ATN signals and releases the DATA
BUS.
b) If it has not detected the BSY signal to be true after at least a selection
abort time plus two deskew delays, the drive releases the SEL and ATN
signals, allowing the SCSI bus to go to the BUS FREE phase.
When responding to selection, SCSI devices ensure that the selection was still
valid within a selection abort time of their assertion of the BSY signal. Failure
to comply with the requirement could result in an improper selection.
3.5.4 RESELECTION Phase
RESELECTION is an optional phase that allows a drive to reconnect to an
initiator to continue an operation that was previously started by the initiator
but was suspended by the drive.
The initiator determines that it is reselected when the SEL and I/O signals and
its SCSI ID bit are true, and the BSY signal is false for at least one bus settle
delay.
3.5.4.1 Reselection Sequence
The drive:
1.
Upon completing the ARBITRATION phase, asserts both the BSY and SEL
signals.
2.
Delays at least one bus clear delay plus one bus settle delay.
3.
Asserts the I/O signal.
4.
Sets the DATA BUS to the logical OR of its SCSI ID bit and the initiator’s
SCSI ID bit.
5.
Waits at least two deskew delays.
6.
Releases the BSY signal.
7.
Waits at least one bus settle delay before looking for a response from the
initiator.
Quantum DLT 4000 Tape Drive
3-15
SCSI Description
The initiator:
8.
Determines that it is selected when the following occur for at least one bus
settle delay: SEL, I/O, and the initiator’s SCSI ID bit are true and BSY is
false.
9.
Examines the DATA BUS to determine the SCSI ID of the reselecting drive.
10. Asserts the BSY signal within a selection abort time of its most recent
detection of being reselected.
The initiator does not respond to a RESELECTION phase if bad parity is
detected or if more than two SCSI ID bits are on the DATA BUS.
The drive:
11. Detects the BSY signal is true.
12. Asserts the BSY signal.
13. Waits at least two deskew delays.
14. Releases the SEL signal.
15. The drive can then change the I/O signal and the DATA BUS.
The initiator:
16. Detects the SEL signal is false.
17. Releases the BSY signal.
The drive:
18. Continues asserting the BSY signal until it relinquishes the SCSI bus.
3.5.4.2 Reselection Time-Out
Two optional time-out procedures are specified for clearing the SCSI bus if the
initiator waits a minimum of a selection time-out delay and there has been no
BSY signal response from the drive.
1.
2.
3-16
The initiator asserts the RST signal.
The initiator follows these steps:
a) Continues asserting the SEL and ATN signals and releases the DATA
BUS.
b) If it has not detected the BSY signal to be true after at least a selection
abort time plus two deskew delays, releases the SEL and ATN signals,
allowing the SCSI bus to go to the BUS FREE phase.
Quantum DLT 4000 Tape Drive
SCSI Description
SCSI devices that respond to the RESELECTION phase must ensure that the
reselection is still valid within a selection abort time of asserting the BSY
signal.
3.5.5
Information Transfer Phases
NOTES
1.
The tape drive supports narrow asynchronous and synchronous data transfers.
2.
Both differential and single-ended versions of the tape drive are available.
3.
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 tape drive. Parity checking can be
disabled (Chapter 2).
4.
The ANSI SCSI specification refers to mini-libraries as “medium changers.” In this
chapter the term “mini-libraries” is used to describe these devices.
5.
The DLT 4000 supports block size of 1byte to 16 Mbytes.
6.
Disconnects from the SCSI bus are done at regular intervals during information
transfer phases to allow other devices to access the bus. These disconnects are
user-configurable via the Disconnect-Reconnect Page of the SCSI MODE SELECT
command.
7.
The 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, and 3) assert bus reset.
8.
A mini-library subsystem is assigned two logical unit numbers (LUNs): the tape
drive is always LUN 0, and the mini-library component has a default LUN of 1, but
may be reconfigured to any LUN from 0 to 15 via the SCSI MODE SELECT command.
Quantum DLT 4000 Tape Drive
3-17
SCSI Description
The COMMAND, DATA, STATUS, and MESSAGE phases are known as the
Information Transfer Phases because they are used to transfer data or control
information.
The C/D, I/O, and MSG signals are used to distinguish between the different
information transfer phases (Table 3−5). The drive asserts these three signals
and so controls all information transfer phase changes. The drive can also cause
a BUS FREE phase by releasing the MSG, C/D, I/O, and BSY signals. The
initiator can request a MESSAGE OUT phase by asserting the ATN signal.
The information transfer phases use one or more REQ/ACK handshakes to
control the information transfer. Each REQ/ACK handshake allows the transfer
of one byte of information. During the information transfer phases, the BSY
signal remains true and the SEL signal remains false. Additionally, the drive
continuously envelopes the REQ/ACK handshake(s) with the C/D, I/O, and
MSG signals in such a manner that these control signals are valid for one bus
settle delay before the assertion of the REQ signal of the first handshake and
remain valid after the negation of the ACK signal at the end of the handshake of
the last transfer of the phase.
After the negation of the ACK signal of the last transfer of the phase, the drive
can prepare for a new phase by asserting or negating the C/D, I/O, and MSG
signals. These signals can be changed together or individually. They can be
changed in any order and can be changed more than once (although each line
should change only once). A new phase does not begin until the REQ signal is
asserted for the first byte of the new phase.
A phase ends when the C/D, I/O, or MSG signal changes after the negation of
the ACK signal. The time between the end of a phase and the assertion of the
REQ signal beginning a new phase is undefined. An initiator is allowed to
anticipate a new phase based on the previous phase, the expected new phase,
and early information provided by changes in the C/D, I/O, and MSG signals.
However, the anticipated phase is not valid until the REQ signal is asserted at
the beginning of the next phase.
Information Transfer Direction
True I/O Signal: from drive to initiator
False I/O Signal: from initiator to drive
3-18
Quantum DLT 4000 Tape Drive
SCSI Description
Table 3–5 Information Transfer Phases
Signal
MSG
C/D
I/O
0
0
0
Phase Name
Direction of Transfer/ Definition
DATA OUT
Initiator to drive.
Allows the drive to request that data be sent from
the initiator to the drive.
0
0
1
DATA IN
Drive to initiator.
Allows the drive to send data to the initiator.
0
1
0
COMMAND
Initiator to drive.
Allows the drive to request a command from the
initiator.
0
1
1
STATUS
Drive to initiator.
Allows the drive to send status information be
sent from the drive to the initiator.
1
1
0
MESSAGE OUT
Initiator to drive.
Allows the drive to request that message(s) be
sent from the initiator to the drive; the drive
invokes this phase in response to the attention
condition created by the initiator.
The drive handshakes byte(s) until the ATN signal
is negated, except when rejecting a message.
See 3.5.5.4 Message Out — Additional
Conditions.
1
1
1
MESSAGE IN
Drive to initiator.
Allows the drive to send message(s) to the
initiator.
Quantum DLT 4000 Tape Drive
3-19
SCSI Description
3.5.5.1 Asynchronous Data Transfer
Drive to Initiator Transfer Procedure
1.
The drive drives the DB (7–0, P) signals to their desired values.
2.
Drive delays at least one deskew delay plus a cable skew delay.
3.
Drive asserts the REQ signal.
4.
Initiator reads the DB (7–0, P) signals.
5.
Initiator indicates its acceptance of the data by asserting the ACK signal.
6.
When ACK is true at the drive, drive can change or release the DB (7–0, P)
signals.
7.
Drive negates the REQ signal.
8.
Initiator negates the ACK signal.
9.
Drive can continue the transfer by driving the DB (7–0, P) signals and
asserting the REQ signal (Steps 1 – 3).
Initiator-to-Drive Transfer Procedure
1.
Drive asserts the REQ signal.
2.
Initiator drives the DB (7–0, P) signals to their desired values.
3.
Initiator delays at least one deskew delay plus a cable skew delay.
4.
Initiator asserts the ACK signal.
5.
When ACK is true at the drive, drive reads the DB (7–0, P) signals.
6.
Drive negates the REQ signal.
7.
Initiator can change or release the DB (7–0, P) signals.
8.
Initiator negates the ACK signal.
9.
Drive can continue the transfer by asserting the REQ signal (Step 1).
3.5.5.2 Synchronous Data Transfer
3-20
Synchronous Data Transfer is optional and is only used in DATA phases and
only if a synchronous data transfer agreement is established. The REQ/ACK
offset specifies the maximum number of REQ pulses that can be sent by the
drive in advance of the number of ACK pulses received from the initiator,
establishing a pacing mechanism. If the number of REQ pulses exceeds the
number of ACK pulses by the REQ/ACK offset, the drive does not assert the
Quantum DLT 4000 Tape Drive
SCSI Description
REQ signal until after the leading edge of the next ACK pulse is received. For
successful completion of the data phase, the number of ACK and REQ pulses
must be equal.
The initiator sends one ACK signal pulse for each REQ pulse received. The ACK
signal can be asserted as soon as the leading edge of the corresponding REQ
pulse has been received.
Drive-to-Initiator Transfer Procedure
1.
The drive sets the DB (7–0, P) signals to the desired values. The DB (7–0,
P) signals are held valid for a minimum of one deskew delay plus one cable
skew delay after REQ is asserted.
2.
Drive delays at least one deskew delay plus a cable skew delay.
3.
Drive asserts the REQ signal for a minimum of one assertion period. Drive
can negate the REQ signal and change or release the DB (7-0, P) signals.
4.
Initiator reads the DB (7-0, P) signals within one hold time of the
transition of the REQ signal to true.
5.
Initiator indicates its acceptance of the data by asserting an ACK pulse.
6.
The drive waits at least the greater or these periods before again asserting
REQ:
c) A transfer period from the last transition of the REQ signal to true, or
d) A negation period from the last transition of the REQ signal to false.
7.
The initiator waits at least the greater of these periods before reasserting
ACK:
a) A transfer period from the last transition of the ACK signal to true, or
b) A negation period from the last transition of the ACK signal to false.
Initiator-to-Drive Transfer Procedure
Initiator transfers one byte for each REQ pulse received.
1.
Drive asserts the REQ signal.
2.
After receiving the leading edge of the REQ signal, initiator drives the DB
(7–0, P) signals to their desired values. The DB (7-0, P) signals are held
valid for at least one deskew delay plus one cable skew delay plus one hold
time delay after the assertion of the ACK signal.
3.
Initiator delays at least one deskew delay plus a cable skew delay.
4.
Initiator asserts the ACK signal for a minimum of one assertion period.
5.
Initiator can negate the ACK signal and change or release the DB (7-0, P)
signals.
Quantum DLT 4000 Tape Drive
3-21
SCSI Description
6.
Drive reads the DB (7-0, P) signals within one hold time of the transition of
the ACK signal to true.
7.
The drive waits at least the greater of these periods before again asserting
the REQ signal:
a) A transfer period from the last transition of the REQ signal to true, or
b) A negation period from the last transition of the REQ signal to false.
8.
The initiator waits at least the greater of the following periods before again
asserting the ACK signal:
a) A transfer period from the last transition of the ACK signal to true, or
b) A negation period from the last transition of the ACK signal to false.
3.5.5.3 Signal Restrictions Between Phases
When the SCSI bus is between two information transfer phases, the following
restrictions apply to the SCSI bus signals:
•
The BSY, SEL, REQ, and ACK signals do not change.
•
The C/D, I/O, MSG, and DATA BUS signals can change.
•
•
•
When changing the DATA BUS direction from out (initiator-driving) to in
(drive-driving), the drive delays driving the DATA BUS by at least a data
release delay plus one bus settle delay after asserting the I/O signal. The
initiator releases the DATA BUS no later than a data release delay after the
transition of the I/O signal to true.
When switching the DATA BUS from in to out, the drive releases the DATA
BUS no later than a deskew delay after negating the I/O signal.
The ATN and RST signals can change as defined under the descriptions for
the attention condition (Section 3.6.1) and reset condition (Section 3.6.2).
3.5.5.4 STATUS Phase
The tape drive enters the status phase just once per command unless a retry is
requested by the initiator. The only exception is during error cases when the
device goes immediately to bus free, as defined in the ANSI SCSI-2 specification.
Status bytes the tape drive can return are listed in the following table:
3-22
Quantum DLT 4000 Tape Drive
SCSI Description
Table 3–6 Status Bytes
Status Bytes Returned from Tape Drive
Definition
GOOD (00h)
This status indicates that the drive successfully completed
the command.
CHECK CONDITION (02h)
A contingent allegiance condition occurred. The REQUEST
SENSE command should be sent following this status to
determine the nature of the event.
BUSY (08h)
Target is busy. This status is returned whenever the device
is unable to accept a command from an otherwise
acceptable initiator. The initiator should reissue the
command at a later time.
INTERMEDIATE GOOD (10h)
This status is returned instead of GOOD for commands
issued with the LINK bit set = 1. Following the return of
this status, the drive proceeds to the COMMAND phase for
the transfer of the next linked command.
RESERVATION CONFLICT (18h)
This status is returned by the drive whenever a SCSI device
attempts to access the drive when it has been reserved for
another initiator with a RESERVE UNIT command.
COMMAND TERMINATED (22h)
This status is returned for a command that was terminated
via a TERMINATE I/O PROCESS message. This status also
indicates that a contingent allegiance condition has
occurred.
Quantum DLT 4000 Tape Drive
3-23
SCSI Description
NOTES
In contrast to the BUSY status condition, the DRIVE NOT READY
Sense Key is returned as part of the Sense data following a REQUEST
SENSE command and indicates that a media access command has
been issued but that the media is not ready to be accessed. For
example, the tape cartridge is not installed, the tape medium has
been unloaded, the tape drive is currently initializing the tape
medium to prepare it for access, etc.
In the DRIVE NOT READY state, the initiator cannot perform any
operation that would cause tape motion (READ, WRITE, VERIFY, for
example). These commands return a CHECK CONDITION status with a
DRIVE NOT READY sense key. The initiator may execute commands
that do not require tape motion or access to the tape medium, and
a GOOD status may be the result.
3.6
SCSI BUS CONDITIONS
The SCSI bus has two asynchronous conditions: Attention and Reset.
3.6.1 Attention Condition
The attention condition informs a 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 the drive detects that the initiator failed to meet this requirement, then
the drive goes to BUS FREE.
Before transition 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 cannot be honored until a later bus phase and then cannot result in
the expected action.
The drive responds with MESSAGE OUT as described in the following table:
3-24
Quantum DLT 4000 Tape Drive
SCSI Description
Table 3–7 Drive MESSAGE OUT Phase Response
ATN Signal True in Phase...
The Drive Enters MESSAGE OUT…
COMMAND
After transferring part or all of the command descriptor block
bytes.
DATA
At the drive’s earliest convenience (often on a logical block
boundary). The initiator continues REQ/ACK handshakes until it
detects the phase change.
STATUS
After the status byte has been acknowledged by the initiator.
MESSAGE IN
Before it sends another message. This permits a MESSAGE
PARITY ERROR message from the initiator to be associated with
the appropriate message.
SELECTION1
Immediately after that SELECTION phase.
RESELECTION2
After the drive has sent its IDENTIFY message for that
RESELECTION phase.
1Before 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 BUS
DEVICE RESET or DISCONNECT message.
The initiator keeps the ATN signal asserted if more than one byte is to be
transferred. The initiator can negate the ATN signal at any time, except it does
not negate the ATN signal while the ACK signal is asserted during a MESSAGE
OUT phase. 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.
3.6.2 Reset Condition
The tape drive responds to power-on and/or bus reset conditions as described:
•
•
•
All tape drive SCSI lines assert high impedance when the tape drive is
powered off.
The drive does not generate any spurious signals on the SCSI bus when the
drive is powered on.
Within five (5) seconds of power-on, and within 250 milliseconds (typically
under 4 milliseconds) after a bus reset, the tape drive responds to SCSI bus
selections and returns the appropriate normal responses. Tape motion
Quantum DLT 4000 Tape Drive
3-25
SCSI Description
commands are returned with Check Condition status, Sense Key of Not
Ready, until the medium has been made ready.
•
The tape medium is rewound to Beginning of Partition (BOP, i.e.,
Beginning of Tape [BOT]).
Note that the tape drive does not implement the hard reset alternative for bus
RESET processing.
The tape drive recognizes multiple bus resets in succession as well as bus resets
of arbitrarily long duration (powering on conditions). It recovers within the time
limits specified above following the last bus reset.
3.6.3 Queued Unit Attentions
Queued Unit Attentions are implemented on the tape drive and are maintained
separately for each valid LUN for each initiator. Unit Attentions are created as a
result of the following circumstances:
•
Power on
•
Bus reset
•
Bus device reset message
•
When the media may have changed asynchronously
•
When another initiator has changed the mode parameters
•
When a firmware (microcode) update has completed
Two (2) queued Unit Attentions are not unusual. For example, if a drive is
powered up and a cartridge is loaded, “power up” and “not ready to ready
transition” Unit Attention messages are created. Due to a limited number of
Unit Attention buffers, if an initiator does not clear Unit Attentions queued for
it, the tape drive at some point stops generating new Unit Attention messages
for the Initiator-Logical Unit (I-L) combination (existing messages remain
queued).
A LOAD command does not generate a Unit Attention message for the initiator
that issued the command, since the transition to ready is synchronous.
3-26
Quantum DLT 4000 Tape Drive
Chapter 4
MESSAGES
The SCSI message system allows communication between an initiator and the drive for interface
management and command qualification. Messages can be originated by either the initiator or the
drive. This section contains a detailed description of the messages supported by the drives.
4.1
MESSAGE 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 over
MESSAGE phases. The initiator is required to end the MESSAGE OUT phase
(by negating ATN) when it sends certain messages that are identified in Table
4–2.
When a connection to the drive is established (i.e., the drive is selected with
ATN asserted), the first message byte passed by the initiator must be either an
IDENTIFY, ABORT, or BUS DEVICE RESET message. If not, the drive discards
the message, saves no status information, and goes to the BUS FREE phase.
If an initiator supplies an unsupported message (for example, COMMAND
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).
The first byte of the message, as defined in Table 4–1, determines the format of
the message.
Quantum DLT 4000 Tape Drive
4-1
Messages
Table 4–1 Message Format
Message Code
Message
00h
One-byte message (COMMAND COMPLETE)
01h
Extended message
02h – 1Fh
One-byte message
20h – 2Fh
Two-byte message
40h – 7Fh
Reserved
80h – FFh
One-byte message (IDENTIFY)
The DLT 4000 tape drive supports the messages listed in Table 4–2. The
message code and the direction of the message flow is also included in the table
(In = target to initiator, Out = initiator to target).
4-2
Quantum DLT 4000 Tape Drive
Messages
Table 4–2 Supported Messages
Message
Message Code
Direction
ABORT
06h
Out
BUS DEVICE RESET
0Ch
Out
COMMAND COMPLETE
00h
In
DISCONNECT
04h
In
Out
EXTENDED MESSAGE (Synchronous Data
Transfer Request, or SDTR) *
01h
In
Out
80h – FFh
In
Out
IDENTIFY
INITIATOR DETECTED ERROR
05h
Out
LINKED COMMAND COMPLETE
0Ah
In
LINKED COMMAND COMPLETE (with flag)
0Bh
In
MESSAGE PARITY ERROR
09h
MESSAGE REJECT
07h
NO OPERATION
08h
RESTORE POINTERS
03h
In
SAVE DATA POINTER
02h
In
Out
In
Out
*Extended message (Figure 4–1); described in Section 4.2.14.
Two-byte messages consist of two consecutive bytes. The value of the first byte,
as defined in Table 4–1, determines which message is to be transmitted. The
second byte is a parameter byte that is used as defined in the message
description.
A value of 1 in the first byte indicates the beginning of a multiple-byte extended
message. The minimum number of bytes sent for an extended message is three.
The extended message format is shown in Figure 4–1 and the data fields are
described in Table 4–3.
Quantum DLT 4000 Tape Drive
4-3
Messages
Bit
Byte
7
6
5
4
3
0
Extended Message (01h)
1
Extended Message Length
2
Extended Message Code
3 to n-1
Extended Message Arguments
2
1
0
Figure 4–1 Extended Message - Data Format
Table 4–3 Extended Message - Field Description
Field
Description
Extended Message
Length
This field specifies the length, in bytes, of the Extended
Message Code plus the Extended Message Arguments that
follow. Therefore, the total length of the message is equal to
the Extended Message Length plus 2.
A value of 0 for the Extended Message Length indicates that
256 bytes follow.
Extended Message Code
The drive supports some Extended Messages. They are:
01h SYNCHRONOUS DATA TRANSFER REQUEST
80h – FFh Vendor Unique (for more information, refer to the
section for the INQUIRY command in Chapter 5).
4-4
Quantum DLT 4000 Tape Drive
Messages
4.2
SUPPORTED SCSI MESSAGES
Following are descriptions of each of the messages supported by the drive.
4.2.1 ABORT Message (06h)
This message is sent from the initiator to the target to clear the current I/O
process on the selected unit. Buffered (cached) write operations are completed if
possible. The target goes directly to the BUS FREE phase after successful receipt
of this message. Current settings of MODE SELECT parameters and
reservations are not affected. Commands, data, and status for other initiators
are not affected.
This message can be sent to a logical unit that is not currently performing an
operation for the initiator. If no unit has been selected, the target goes to BUS
FREE phase and no commands, data, or status on the target are affected.
4.2.2 BUS DEVICE RESET Message (0Ch)
The BUS DEVICE RESET message is sent from an initiator to direct the drive to
clear all I/O processes on the drive. The message causes the drive to:
1.
Flush the contents of cache to tape and go to the BUS FREE phase.
2.
Execute a hard reset, leaving it as if a Bus Reset had occurred.
The drive creates a Unit Attention condition for all initiators after accepting and
processing a Bus Device Reset message. The additional sense code is set to
POWER ON, RESET, or BUS DEVICE RESET OCCURRED.
4.2.3 COMMAND COMPLETE Message (00h)
The COMMAND COMPLETE message is sent by the drive to an initiator to
indicate that an I/O process has completed and that valid status has been sent
to the initiator. After successfully sending this message, the drive goes to 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
COMMAND COMPLETE message with the ATN signal false. If a COMMAND
COMPLETE message is received by the tape drive, it is handled as an illegal
message: the drive returns MESSAGE REJECT and enters its STATUS phase,
reporting CHECK CONDITION with the sense key set to COMMAND
ABORTED.
Quantum DLT 4000 Tape Drive
4-5
Messages
4.2.4 DISCONNECT Message (04h)
The DISCONNECT message is sent from the drive to inform the initiator that
the present connection is going to be broken (the drive plans to disconnect by
releasing the BSY signal) and a later reconnect will be required to complete the
current I/O process. The message does not cause the initiator to save the data
pointer. After sending the message, the drive goes to the BUS FREE phase by
releasing the BSY signal.
The DISCONNECT message can also be sent by the initiator 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 introduces the DISCONNECT message. Table 4–4
summarizes the drive’s response.
Table 4–4 Drive Response to DISCONNECT Message
BUS Phase
Drive Response
SELECTION
The drive discards the DISCONNECT message and goes to BUS FREE.
COMMAND
The drive discards the DISCONNECT message and goes to BUS FREE. The
ATTENTION request is ignored while the Command Descriptor Block is fetched.
The drive does not switch to MESSAGE OUT until the current DMA completes.
DATA
The ATTENTION request is ignored 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.
STATUS
The drive sends a MESSAGE REJECT message, then sends COMMAND
COMPLETE.
MESSAGE IN
The drive sends a MESSAGE REJECT message and switches to the BUS FREE
phase.
4-6
Quantum DLT 4000 Tape Drive
Messages
4.2.5 IDENTIFY Message (80h - FFh)
The IDENTIFY message is sent by either the initiator or the drive to establish or
re-establish the physical connection path between an initiator and target for a
particular logical unit, under the conditions listed below. Figure 4–2 shows the
format of the IDENTIFY message and Table 4–5 describes the data field
contents.
Bit
Byte
7
6
5
Identify
DiscPriv
LUNTAR
4
3
2
Reserved
1
0
LUNTRAN
Figure 4–2 IDENTIFY Message - Data Format
Table 4–5 IDENTIFY Message - Field Description
Field
Description
Identify
The Identify bit must be set to 1. This identifies the message as an IDENTIFY
message.
DiscPriv
Disconnect Privilege. The DiscPriv can be 0, provided that no other I/O process is
currently active in the drive. If not set to 1 and other I/O processes are currently
active in the drive, the drive returns BUSY status.
LUNTAR
The Logical Unit/Target Routine (LUNTAR) field must be set to zero. The drive
supports a single Logical Unit Number (LUN 0 ). A LUNTAR bit of one causes the
drive to send a MESSAGE REJECT message and switch to the BUS FREE phase.
Reserved
The Reserved bits must be zero. If a Reserved bit is non-zero, the drive returns a
MESSAGE REJECT message and switches to the BUS FREE phase.
LUNTRN
Logical Unit Number.
Quantum DLT 4000 Tape Drive
4-7
Messages
4.2.6 INITIATOR DETECTED ERROR Message (05h)
The INITIATOR DETECTED ERROR message is sent from an initiator to
inform the drive that an error has occurred that does not preclude the drive from
retrying the operation (a bus parity error, for example). The source of the error
may either be related to previous activities on the SCSI bus or may be only driverelated. When received, the tape drive attempts to re-transfer the last command,
data, or status bytes by using the RESTORE POINTER 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 introduces the
message. Table 4–6 summarizes the drive’s response.
Table 4–6 Drive Response to INITIATOR DETECTED ERROR Message
BUS Phase
Drive Response
SELECTION
The drive discards the INITIATOR DETECTED ERROR message and then goes
to the BUS FREE phase.
COMMAND
The drive discards any Command Descriptor Block bytes fetched from the
initiator, sets the Sense Key to ABORTED COMMAND, sets the Additional
Sense Code to INITIATOR DETECTED ERROR MESSAGE RECEIVED. It sends
the CHECK CONDITION status and the COMMAND COMPLETE message and
then goes to the BUS FREE phase.
DATA
The drive discards the INITIATOR DETECTED ERROR message and sets the
Sense Key to ABORTED COMMAND, sets the Additional Sense Code to
INITIATOR DETECTED ERROR MESSAGE RECEIVED. It sends the CHECK
CONDITION status and the COMMAND COMPLETE message and then goes
to the BUS FREE phase.
STATUS
The drive sends a RESTORE POINTERS message, returns to the STATUS
phase, resends the STATUS command, and continues the I/O process.
MESSAGE IN
The drive discards the INITIATOR DETECTED ERROR message and sets the
Sense Key to ABORTED COMMAND, sets the Additional Sense Code to
INITIATOR DETECTED ERROR MESSAGE RECEIVED. It sends the CHECK
CONDITION status and the COMMAND COMPLETE message and then goes
to the BUS FREE phase.
4-8
Quantum DLT 4000 Tape Drive
Messages
4.2.7 LINKED COMMAND COMPLETE Message (0Ah)
This message is sent from a target to an initiator to indicate that the execution
of a linked command (with the FLAG bit set to zero) is complete and that
status has been sent. The initiator then sets the pointers to the initial state for
the next command.
If received by a target, this message is handled as an illegal message; the drive
enters the MESSAGE IN phase and returns MESSAGE REJECT.
4.2.8 LINKED COMMAND COMPLETE, with Flag Message (0Ah)
This message is sent from a target to an initiator to indicate that the execution
of a linked command (with the FLAG bit set to one) is complete and that status
has been sent.
4.2.9 MESSAGE PARITY ERROR Message (09h)
This message is sent from the initiator to tell the drive that the last message
byte the drive passed on to the initiator contained a parity error.
To indicate that it intends to send the message, the initiator sets the ATN
signal before it releases ACK for the REQ/ACK handshake of the message that
has the parity error. This provides an interlock so that the target can determine
which message has the parity error. If the target receives this message under any
other condition, it proceeds directly to the BUS FREE state by releasing the BSY
signal, signifying a catastrophic error.
The target’s response to this message is to switch to the MESSAGE IN phase
and re-send from the beginning all the bytes of the message that precipitated the
MESSAGE PARITY ERROR message.
4.2.10 MESSAGE REJECT Message (07h)
This message is sent from the initiator or target to indicate that the last
message received was inappropriate or has not been implemented.
To indicate its intention to send this message, the initiator asserts the ATN
signal before it releases ACK for the REQ/ACK handshake of the message that
is to be rejected. MESSAGE REJECT is issued in response to any message the
drive considers to be illegal or not supported. When sending to the initiator, the
tape drive does so before requesting any additional message bytes.
Quantum DLT 4000 Tape Drive
4-9
Messages
4.2.11 NO OPERATION Message (08h)
If a target requests a message, the initiator sends a NO OPERATION message if
it does not currently have any other valid message to send. The message is
accepted when the drive is acting as a target and may be sent when it is an
initiator. If a NO OPERATION message is received during a selection, the drive
proceeds to the COMMAND phase (provided ATN does not continue as
asserted); the NO OPERATION message is ignored by the tape drive.
4.2.12 RESTORE POINTERS Message (03h)
The RESTORE POINTERS message is sent from the drive to the initiator to
direct the initiator to copy the most recently saved command, data, and status
pointers for the I/O process to the corresponding current pointers. The command
and status pointers are restored to the beginning of the present command and
status areas. The data pointer is restored to the value at the beginning of the
data area in the absence of a SAVE DATA POINTER message or to the value at
the point at which the last SAVE DATA POINTER message occurred for that
logical unit.
When the RESTORE POINTERS message is received as a target, the target
switches to the message in phase and returns MESSAGE REJECT.
4.2.13 SAVE DATA POINTER Message (02h)
The SAVE DATA POINTER message is sent from the drive to direct the
initiator to copy the current data pointer to the saved data pointer for the
current I/O process.
When functioning as a target, the tape drive sends this message before a
disconnect during a data transfer. It does not send a SAVE DATA POINTER
message if it intends to move directly to STATUS phase. When received as a
target, it switches to message in phase and returns MESSAGE REJECT.
4.2.14 SYNCHRONOUS DATA TRANSFER REQUEST Message (01h)
This extended message allows the target and initiator to agree on the values of
the parameters relevant to synchronous transfers. The tape drive will not initiate
the Synchronous Data Transfer Request message; it relies on the initiator to do
so. The Synchronous Data Transfer Request command has the format shown in
Figure 4-3.
4-10
Quantum DLT 4000 Tape Drive
Messages
Bit
Byte
7
6
5
4
3
0
Extended Message Identifier (01h)
(Figure 4-1)
1
Length (03h)
2
Message Code (01h)
3
Transfer Period: Min. = 50 (32h)
4
Transfer REQ/ACK Offset: Max. = 15
2
1
0
Figure 4–3 Synchronous Data Transfer Request Message - Data Format
NOTE
The tape drive supports initiating synchronous transfer negotiations
with the host, but this feature is disabled by default. To enable it,
set the MODE SELECT VU ERROM parameter EnaInitSyncNeg.
Quantum DLT 4000 Tape Drive
4-11
Messages
4-12
Quantum DLT 4000 Tape Drive
Chapter 5
SCSI COMMANDS
This chapter describes the SCSI protocol features implemented in the DLT 4000 tape drive. Note that
the sections included in this chapter do not fully reiterate every ANSI SCSI message, option, and/or
command code specification; the sections do describe the supported commands, messages,
options, and error recovery procedures.
5.1
OVERVIEW OF COMMAND AND STATUS PROCESSING
The Quantum DLT 4000 tape drive supports the SCSI commands listed in Table
5-1. The subsection of this chapter that details each of the SCSI commands is
listed in the “Section” column.
Table 5-1 Supported SCSI Commands
Command
Operation Code
Section
ERASE
19h
5.3
INQUIRY
12h
5.4
LOAD UNLOAD
1Bh
5.5
LOCATE
2Bh
5.6
LOG SELECT
4Ch
5.7
LOG SENSE
4Dh
5.8
MODE SELECT (6 / 10)
15h / 55h
5.9
MODE SENSE (6 / 10))
1Ah / 5Ah
5.10
PREVENT ALLOW MEDIUM REMOVAL
1Eh
5.11
READ
08h
5.12
READ BLOCK LIMITS
05h
5.13
READ BUFFER
3Ch
5.14
READ POSITION
34h
5.15
Quantum DLT 4000 Tape Drive
5-1
SCSI Commands
Table 5-1 Supported SCSI Commands (continued)
Command
5-2
Operation Code
Section
RECEIVE DIAGNOSTIC RESULTS
1Ch
5.16
RELEASE UNIT
17h
5.17
REPORT LUNS
A0h
5.18
REQUEST SENSE
03h
5.19
RESERVE UNIT
16h
5.20
REWIND
01h
5.21
SEND DIAGNOSTIC
1Dh
5.22
SPACE
11h
5.23
TEST UNIT READY
00h
5.24
VERIFY
13h
5.25
WRITE
0Ah
5.26
WRITE BUFFER
3Bh
5.27
WRITE FILEMARKS
10h
5.28
Quantum DLT 4000 Tape Drive
SCSI Commands
NOTES
1.
Relative Addressing is not supported by the tape drive. Therefore,
in all I/O commands, the RelAdr bit must be 0.
2.
RESERVE UNIT and RELEASE UNIT by Logical Unit Number are
supported, as are third-party reservations. Extent reservations are
not supported.
3.
The RECEIVE DIAGNOSTIC RESULTS and SEND DIAGNOSTIC DATA
commands implement vendor-unique pages to test the drive during
the manufacturing process. It is recommended that initiators specify
only the non-page format variants of these commands (PF=0),
except for page 0x40.
4.
The DLT tape drive does not act as an initiator on the SCSI bus.
Therefore, the drive will not 1) generate unsolicited interrupts to
the host, 2) initiate its own SCSI commands, or 3) assert bus reset.
5.
Linked commands are supported.
6.
Untagged queuing is supported.
5.1.1 SCSI Pointers
SCSI architecture provides a set of three pointers (called saved pointers) for
each I/O process. The three pointers are: Command, Status, and Data. When an
I/O process becomes active, the three saved pointers are copied to the initiator
as current pointers. There is only one set of current pointers in the initiator at
one time. The current pointers point to the next command, data, or status byte
to be transferred between the initiator's memory and the drive. The saved and
current pointers reside in the initiator.
The saved command pointer always points to the start of the Command Descriptor
Block for the I/O process. The saved status pointer always points to the start of
the status area of the I/O process. The saved data pointer always points to the
start of the data area until the drive sends a SAVE DATA POINTER message for
the I/O process back to the initiator.
Quantum DLT 4000 Tape Drive
5-3
SCSI Commands
In response to the SAVE DATA POINTER message, the initiator stores the
value of the current data pointer into the saved data pointer for that I/O
process. The drive can restore the current pointer from the saved pointer value
for the active I/O process by sending a RESTORE POINTERS message to the
initiator. The initiator then copies the set of saved pointers into the set of
current pointers. Whenever a drive disconnects from the SCSI Bus, only the set
of saved pointers is retained in the initiator. The set of current pointers is
restored from the set of saved pointers when the I/O process is reconnected.
5.1.2 Command Descriptor Block
An initiator communicates with the drive by sending a 6- or 10-byte Command
Descriptor Block that contains the parameters for the specific command. The
SCSI command's operation code is always the first byte in the Command
Descriptor Block and a control field is the last byte. For some commands, the
Command Descriptor Block is accompanied by a list of parameters sent during
the DATA OUT phase. Figure 5–1 shows the format of a typical 6-byte
Command Descriptor Block. Table 5-2 contains a description of the Command
Descriptor Block fields.
Bit
Byte
7
6
5
0
4
3
2
1
0
Operation Code
(MSB)
1
2-3
Logical Unit Number
(LUN)
Logical Block Address
(LBA)
Logical Block Address
(LBA)
4
Transfer Length, Parameter List Length, or Allocation Length
5
Control
NOTE: Unless otherwise specified, all reserved bits indicated in the commands are 0.
Figure 5–1 Typical Command Descriptor Block - Data Format
5-4
Quantum DLT 4000 Tape Drive
(LSB)
SCSI Commands
Table 5–2 Command Descriptor Block - Field Descriptions
Field
Description
Operation Code
The operation code specifies the command being requested. The list of
supported SCSI commands and their operation codes are contained in Table
5-1.
Logical Unit Number
The Logical Unit Number contains the number of the device being
addressed. It must be set to 0. The Logical Unit Number is ignored if the
Command Descriptor Block is preceded by an IDENTIFY Message.
Logical Block
Address
The 6-byte READ, SEEK, and WRITE Command Descriptor Blocks contain a
21-bit Logical Block Address. The 10-byte READ, SEEK, and WRITE Command
Descriptor Blocks contain a 32-bit Logical Block Address.
Commands that require additional parameter data specify the length of the
Logical Block Address that is needed. See the specific command descriptions
for more detailed information.
Relative Addressing indicates a technique used to determine the next Logical
Block Address to be operated on. The drive does not support Relative
Addressing. It defaults to a value of 0, which specifies that the Logical Block
Address specifies the first logical block of a range of logical blocks to be
operated on by the command.
Transfer Length
The transfer length field normally specifies the number of blocks to be
transferred between the initiator and the drive. For several commands, the
transfer length indicates the number of bytes (not blocks) to be sent. For
these commands, this field may be identified by a different name.
Parameter List
Length
The Parameter List Length is used to specify the number of bytes sent during
the DATA OUT phase. This field is typically used for parameters that are sent
to a drive (for example, mode, diagnostic, and log parameters). A parameter
list length of 0 indicates that no data is to be transferred.
Allocation Length
The Allocation Length field specifies the number of bytes that the initiator
has allocated for returned data. The Allocation Length is used to limit the
amount of data returned to the initiator.
An Allocation Length of 0 indicates that no data is to be transferred from the
drive to the initiator. The drive terminates the DATA IN phase when the
specified number of bytes have been transferred to the initiator or when all
available data has been transferred, whichever is less.
Quantum DLT 4000 Tape Drive
5-5
SCSI Commands
Table 5–2 Command Descriptor Block - Field Descriptions (continued)
Field
Description
Control Field
The Control Field is the last byte of every command descriptor block. Its
format is shown in Figure 5–2 and it contains the Flag and Link bits. Use of
these bits is initiator-dependent. Setting the Link bit = 1 provides an
automatic link to the next command, bypassing the usual ARBITRATION,
SELECTION, and MESSAGE OUT phases that would normally occur between
commands. Other bits in the Control Field are considered to be reserved.
Relative Address
(RelAdr)
Must be 0 (not supported).
Bit
Byte
5
7
6
5
Vendor Specific
4
3
Reserved
2
1
0
Flag
Link
Figure 5–2 Command Descriptor Block Control Field - Data Format
Table 5–3 Command Descriptor Block Control Field - Field Descriptions
Field
Description
Vendor Specific Bits
These bits must be 0.
Flag Bit
The Flag bit is used in conjunction with the Link bit to notify the initiator in
an expedient manner that a command has been completed.
Link Bit
A Link bit set to 1 indicates that the initiator requests continuation of a task
(an I/O process) across two or more SCSI commands.
If the Link bit is 1 and the Flag bit is 0, and the task completes successfully,
the drive continues the task and returns a status of INTERMEDIATE and a
LINKED COMMAND COMPLETE message.
If the Link bit and the Flag bit within a Control word are both set to 1, and
the drive complete a command with a status of INTERMEDIATE, the drive
returns a LINKED COMMAND COMPLETE message (with Flag).
5-6
Quantum DLT 4000 Tape Drive
SCSI Commands
5.1.3 Status/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 4 for more detailed message-handling information.
SCSI command-level errors are communicated by a status code that is returned
by the drive during the STATUS phase. This phase occurs at the end of each
command, unless the command is terminated by one of the following events:
•
ABORT message
•
BUS DEVICE RESET message
•
Hard 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 5–4 describes the status codes returned by the drive.
NOTE
In contrast to the BUSY status condition, the DRIVE NOT READY
Sense Key is returned as part of the Sense data following a REQUEST
SENSE command and indicates that a media access command has
been issued and the medium is not ready to be accessed. For
example, the medium is not installed, the medium has been
unloaded, and the drive is currently initializing the medium to
prepare it for access).
Quantum DLT 4000 Tape Drive
5-7
SCSI Commands
Table 5–4 Status Codes
Status
Code
Definition
Meaning
00h
GOOD
The drive successfully completed the command.
02h
CHECK CONDITION
A Contingent Allegiance condition occurred.
08h
BUSY
The drive cannot service the command at the moment, and
its Command Descriptor Block has been discarded. The
initiator can retry the command at a later time.
10h
INTERMEDIATE
GOOD
This status is returned instead of a GOOD status for
commands issued with the LINK bit set. Following the
return of this status, the drive proceeds to the COMMAND
phase for the transfer of the next linked command.
18h
RESERVATION
CONFLICT
Another initiator has reserved the drive when it has been
reserved for another initiator with a RESERVE UNIT
command (this status is never returned for INQUIRY or
REQUEST SENSE commands).
28h
QUEUE FULL
The drive cannot service the command at the moment, and
its Command Descriptor Block has been discarded.
(Returned for a tagged command when all of the drive's
internal command buffers are in use, for instance.)
5.1.4 DATA-Phase Command Components
Many of the SCSI commands cause data to be transferred between the initiator
and the drive. The content and characteristics of this data are commanddependent. Table 5–5 lists the information transmitted for all of the commands.
The "Length in CDB" column of Table 5–6 identifies the Command Descriptor
Block field used by the drive to determine how much command-related data are
to be transferred. The units (bytes or logical blocks) for the different Length
fields are implied by the Length Field Name as follows:
5-8
Quantum DLT 4000 Tape Drive
SCSI Commands
Table 5–5 Length Field Name Units
Field Name
Units Implied
Allocation Length
Bytes of data the drive is allowed to send to the initiator
Parameter List Length
Bytes of data the initiator has available for the drive
Transfer Length
Logical number of data blocks or data bytes the initiator
wants transferred or verified
Byte Transfer Length
Bytes of data the initiator wants transferred
The DATA OUT column in Table 5–6 lists the information passed to the drive
by the initiator as part of the command. The DATA IN column lists the
information sent to the initiator by the drive. Numbers in parentheses after an
item indicate the item’s length in bytes. In some cases, additional length
information is communicated during the DATA phase.
Table 5–6 DATA-Phase Command Contents
Command
Length in CDB
Data Out (To Drive)
Data In (To Initiator)
ERASE
0
INQUIRY
Allocation
---
Standard Inquiry or a
Vital Product Data
page
LOAD UNLOAD
0
---
---
LOCATE
0
---
---
LOG SELECT
Parameter List
(must be 0)
---
---
LOG SENSE
Allocation
---
Log Page
MODE SELECT (6)
Parameter List
Mode Parameter
Header (4) Block
Descriptor (8)
Page(s)
---
MODE SENSE (6)
Allocation
---
Mode Parameter
Header (4) Block
Descriptor (8)
Page(s)
Quantum DLT 4000 Tape Drive
5-9
SCSI Commands
Table 5–6 DATA-Phase Command Contents (continued)
Command
Length in CDB
Data Out (To Drive)
Data In (To Initiator)
PREVENT ALLOW
MEDIUM REMOVAL
0
---
---
READ (6)
Transfer
---
Data
READ BLOCK LIMITS
Allocation
---
Block Length Limits
READ BUFFER
Allocation
---
Buffer Offset and
Allocation Length
READ POSITION
Allocation
---
Position Identifier or
SCSI Logical Address
RECEIVE DIAGNOSTIC
RESULTS
Allocation
---
Diagnostic Page
RELEASE UNIT
0
---
---
REPORT LUNS
Allocation
---
Supported LUNS List
REQUEST SENSE
Allocation
---
Sense Data (18)
RESERVE UNIT
0
(Extent List Option
not supported)
---
---
REWIND
0
---
---
SEND DIAGNOSTIC
Parameter List
Diagnostic Page
---
SPACE
0
---
---
TEST UNIT READY
0
---
---
VERIFY
Transfer
Data
---
WRITE (6)
Transfer
Data
---
WRITE BUFFER
Parameter List
Microcode Image
Data
---
WRITE FILEMARKS
---
---
---
5-10
Quantum DLT 4000 Tape Drive
SCSI Commands
5.1.5 Unit Attention Condition
Queued Unit Attentions are implemented on the Quantum DLT 4000 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
•
At 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
Two queued Unit Attentions are not unusual. For example, if a unit is powered
up and a tape cartridge is loaded, Power Up and Not-Ready to Ready Transition
Unit Attentions are created. Due to the limited number of Unit Attention
buffers, if an initiator does not clear Unit Attentions queued for it, at some
point the tape drive stops generating new Unit Attentions for that initiatorlogical unit combination (existing ones will be left queued, however).
A LOAD command does not generate a Unit Attention for the initiator that
issued the command since the transition to Ready is synchronous.
5.1.6 Behavior at Power-On and SCSI Bus Reset
The following apply to the DLT 4000 tape drive’s behavior at power-on and/or
SCSI bus reset:
•
•
•
When the Quantum DLT 4000 is powered up, all device SCSI lines are set to
high impedance.
The design of the DLT 4000 tape drive does not allow it to generate any
spurious signals on the SCSI bus at power-on.
Within five seconds of power-on, and within 250 milliseconds (typically
under 4 milliseconds) after a SCSI bus reset, the DLT 4000 tape drive
responds to SCSI bus selections and returns appropriate, normal responses.
Tape motion commands will be returned with CHECK CONDITION status,
Sense Key Not Ready, until the tape medium has been made ready.
•
The tape drive implements the hard bus reset option.
•
The tape medium is rewound to Beginning of Tape (BOT).
Quantum DLT 4000 Tape Drive
5-11
SCSI Commands
The DLT 4000 tape drive recognizes multiple, successive SCSI bus resets and
SCSI bus resets of arbitrarily long duration. The tape drive recovers within the
time limits specified above following the last SCSI bus reset.
5.1.7 Data Cache and Tape Write Interaction
The Quantum DLT 4000 drive contains a data cache that buffers blocks
(records) until they are written to tape. This section describes when those blocks
are written, or “flushed” 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 STATUS byte and the
COMMAND COMPLETE message are returned to the host.
NOTE
Unbuffered mode is NOT recommended due to the poor
performance that may result.
The contents of the write data cache are written to the tape medium under the
following circumstances:
•
•
•
•
5-12
When two or more WRITE FILEMARKS commands are issued without
intervening tape motion commands.
When a WRITE 0 FILEMARKS command is issued.
When data has been in the cache longer than the maximum time specified by
the value of the Mode Parameter “Write Delay Time.”
When a non-write type media access command is received (for example,
SPACE, READ, UNLOAD).
Quantum DLT 4000 Tape Drive
SCSI Commands
5.2
SCSI COMMAND DESCRIPTIONS
The SCSI commands are presented in alphabetical order. Each command starts
on a new, odd-numbered page. Because information about a particular command
may span multiple pages, the command name is repeated, in Italics, at the top of
every page that concerns that command. Blank pages in the chapter can be used
for note-taking.
The SCSI command descriptions that make up the rest of Chapter 5 contain
detailed information about each command supported by the Quantum DLT 4000
tape drive. Fields common to many of the SCSI commands are supported as
follows:
Name of Field:
How Field is Supported in SCSI Commands:
Logical Unit
Number
LUN for tape drive is 0.
Reserved
Reserved 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 command is terminated with a CHECK CONDITION
status and the sense key is set to ILLEGAL REQUEST.
RelAdr
Relative Address. Unused.
Explanations for those common fields are not repeated for every command in
which they appear.
Throughout this manual, multiple bytes that contain information about specific
command parameters are portrayed as shown in the example of the Parameter
List Length field (bytes 7 and 8) of the Log Select command shown as follows:
Quantum DLT 4000 Tape Drive
5-13
SCSI Commands
Bit
Byte
7
6
5
0-6
4
3
2
1
0
(Bytes 0 – 6)
(MSB)
7-8
Parameter List Length
(LSB)
As shown, this sample indicates that the most significant bit (MSB) of the field
is bit 7 of byte 7; the least significant bit (LSB) is bit 0 of byte 8.
This is an alternate, “shorthand” presentation for:
Bit
Byte
7
0-6
6
5
4
3
2
1
0
(Bytes 0 – 6)
(MSB)
7
Parameter List Length
8
(LSB)
The shorthand version of presentation is used in this manual due to space
constraints.
5-14
Quantum DLT 4000 Tape Drive
SCSI Commands
5.3
ERASE COMMAND (19H)
The ERASE command causes data on the tape medium to be erased. Any WRITE
data currently held in buffer memory and not yet written to tape is written to
tape before the ERASE command is executed. ERASE command must be issued
while at BOT.
Bit
Byte
7
6
0
1
5
4
3
1
0
Operation Code (19h)
Logical Unit Number
Reserved
2
Reserved
3
Reserved
4
Reserved
5
2
Unused
Reserved
Immed
Long (1)
Flag
Link
Figure 5–3 ERASE Command Descriptor Block - Data Format
Quantum DLT 4000 Tape Drive
5-15
SCSI Commands
ERASE Command (19h) (continued)
Table 5–7 ERASE Command Descriptor Block - Field Descriptions
Field
Description
Immed
Immediate. If the Immediate bit = 0, the target does not return status until the
selected operation has completed.
If set to 1, status is returned as soon as the operation has been initiated.
Long
Must be set to 1. The Long bit controls the distance of tape to be erased. Filler and
End of Data (EOD) blocks are written if needed, then the entire rest of the tape is
erased.
NOTE: The ERASE command results in no operation for the tape drive unless the Long
bit is set to 1. Issuing the ERASE command away from Beginning of Tape (BOT) is an
ILLEGAL REQUEST.
5-16
Quantum DLT 4000 Tape Drive
SCSI Commands
5.4
INQUIRY COMMAND (12H)
The INQUIRY command allows the initiator to determine the kind of SCSI
devices attached to its SCSI Bus. It causes a device that is attached to a SCSI
Bus to return information about itself. The drive identifies itself as a Direct
Access Storage Device that implements the SCSI-2 protocol. The drive does not
need to access its tape medium to respond to the inquiry.
The drive can provide two categories of data in response to an INQUIRY
command: Standard Inquiry Data and Vital Product Data. Standard Inquiry
Data contains basic data about the drive, and Vital Product Data comprises
several pages of additional data. Each Vital Product Data page requires a
separate INQUIRY command from the initiator.
An INQUIRY command is not affected by, nor does it clear, a Unit Attention
condition.
Bit
Byte
7
6
0
1
5
4
3
1
0
Operation Code (12h)
Logical Unit Number
Reserved
2
Page Code
3
Reserved
4
Allocation Length
5
2
Unused
Reserved
EVPD
Flag
Link
Figure 5–4 INQUIRY Command Descriptor Block - Data Format
Quantum DLT 4000 Tape Drive
5-17
SCSI Commands
INQUIRY Command (12h) (continued)
Table 5–8 INQUIRY Command Descriptor Block - Field Descriptions
Field
Description
EVPD
Enable Vital Product Data. If 0, the drive returns the Standard Inquiry Data
page. If 1, the drive returns the Vital Product Data page specified in Page
Code.
Page Code
Specifies which Vital Product Data page is to be returned by the drive. This
field must be 0 if EVPD is 0. A CHECK CONDITION with ILLEGAL REQUEST
status is returned if this field specifies an unsupported page code.
Table 5–9 lists the page codes for the Vital Product Pages supported by the
drive.
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. Error status is
not returned if the value in this field truncates the requested information.
Table 5–9 Vital Product Data - Page Codes
Page Code
Description
00h
Supported Vital Product Pages Page
80h
Unit Serial Number Page
C0h
Code Build Information Page
5.4.1 Standard Inquiry Data Page
Figure 5–5 shows the format of the Standard Inquiry Data page returned by the
drive.
5-18
Quantum DLT 4000 Tape Drive
SCSI Commands
INQUIRY Command (12h) (continued)
Bit
Byte
7
6
0
1
2
3
5
4
3
Peripheral Qualifier
1
0
Peripheral Device Type
RMB
Device Type Modifier
ISO Version
AENC
2
TrmIOP
ECMA Version
ANSI Version
Reserved
Response Data Format
4
Additional Length = 33h
5
Reserved
6
Rsvd
MChngr
7
RelAdr
Wbus32
Reserved
Wbus16
Sync
Linked
8 - 15
Vendor Identification
“Quantum ”
16 - 31
Product Identification
“DLT4000 ”
32 - 35
Product Revision Level = “hhss”
36 - 55
Vendor Unique Bytes
Rsvd
CmdQue
SftRe
Figure 5–5 Standard Inquiry Data Page - Data Format
Quantum DLT 4000 Tape Drive
5-19
SCSI Commands
INQUIRY Command (12h) (continued)
Table 5–10 contains field descriptions for the data returned by the drive.
Table 5–10 Standard Inquiry Data Page - Field Descriptions
Field Name
Value
Description
Peripheral Qualifier
0
Non-zero if initiator selects an invalid logical unit (see below)
Peripheral Device Type
1
1 indicates that this is a sequential access device (see below).
Note that the Peripheral Device Type entry for a medium
changer is 8.
RMB
1
Removable Medium Bit. Set to 1.
Device Type Modifier
1
Set to 1 to specify a sequential access device.
ISO Version
0
International Standardization Organization Version level. Set
to 0.
ECMA Version
0
European Computer Manufacturers Organization Version
level. Set to 0.
ANSI Version
2
ANSI SCSI Level 2 (SCSI-2) is supported.
AENC
0
Asynchronous Event Notification is not supported.
TrmlOp
0
Terminate I/O Process. The tape drive does not support the
TERMINATE I/O PROCESS message.
Response Data Format
2
This Standard Inquiry Data is in SCSI-2 format.
Additional Length
33h
Tape drive uses this field to indicate the number of additional
bytes of INQUIRY Response Data available.
Mchnger
-
Set to 1 if a Media Changer (Loader) is present and EEPROM
parameter EnbIngMedChgr is set to 1. This SCSI-3 bit
indicates that the Read Element Status and Move Medium
commands can be issued to the drive (LUN0). By default, this
bit is set to 0 on the DLT 4000.
RelAdr
0
Relative Addressing is not supported.
WBus 32
0
Set to 0 since the drive does not support 32-bit transfer.
WBus 16
0
The WBus bit is 0 since the drive supports only 8-bit data
transfer.
5-20
Quantum DLT 4000 Tape Drive
SCSI Commands
INQUIRY Command (12h) (continued)
Table 5–10 Standard Inquiry Data Page - Field Descriptions (continued)
Field Name
Value
Description
Sync
1
The drive supports Synchronous Data Transfers.
Linked
1
Linked Commands are supported.
CmdQue
0
The drive does not support Tagged Command Queuing.
SftRe
0
The drive implements the hard reset option in response to
assertion of the SCSI Bus reset line.
Vendor Identification
The value in this field is “Quantum”
Product Identification
The value in this field is “DLT4000”
Product Revision Level
This field contains 4 bytes of ASCII data that provides the
drive’s software revision levels. The first two bytes are the
version number of servo code. The second two bytes are the
version number of the SCSI/read/write code. When a
firmware update is performed on the DLT drive, this part of
the revision level will change to reflect that update.
Vendor Specific
See Section 5.4.2 for details.
NOTE:
Vendor Information, Product Identification, and Product Revision Level are returned as
shown in Figure 5–5.
5.4.2 Vendor Unique Inquiry Data
The following information can be used to precisely identify the revision of
subsystem components.
Quantum DLT 4000 Tape Drive
5-21
SCSI Commands
INQUIRY Command (12h) (continued)
Bit
Byte
36
7
6
5
4
3
Product Family (4)
2
Released Firmware
37
Firmware Major Version #
38
Firmware Minor Version #
39
EEPROM Format Major Version #
40
EEPROM Format Minor Version #
41
Firmware Personality
42
Firmware Sub-Personality
43
Firmware Subtype
44
Controller Hardware Version #
45
Drive EEPROM Version #
46
Drive Hardware Version #
47
Media Loader Firmware Version #
48
Media Loader Hardware Version #
49
Media Loader Mechanical Version #
50
Media Loader Present Flag
51
Library Present Flag
52 - 55
Module Revision
Figure 5–6 INQUIRY Vendor Unique Bytes Definitions
5-22
1
Quantum DLT 4000 Tape Drive
0
SCSI Commands
INQUIRY Command (12h) (continued)
Table 5–11 Vendor Unique Inquiry Data Page - Field Descriptions
Field Name
Description
Product Family
This field indicates the drive’s data density as follows:
Released Firmware
Bit
Drive Density
0
Not Specified
1
2.6 GB
2
6.0 GB
3
10.0 / 20.0 GB
4
20.0 / 40.0 GB
5
15.0 / 30.0 GB
This flag differentiates between released and test versions of
firmware. When set to 1, indicates released code (Vxxx); 0 indicates
field test code (Txxx). Released code has no minor firmware version
number (byte 38 = 0). Field test and engineering versions of code
have non-zero minor firmware version numbers for tracking
purposes.
… Version #
These field display the various version numbers in binary, not ASCII
Firmware Personality
Numeric indicator of firmware personality. For example, firmware
personality of 4 indicates OEM family, 15 indicates OML family, and
18 indicates OMX family.
Firmware Subpersonality
Set to 1, indicating standard SCSI device firmware.
Loader Present
Set to 0 indicates no loader present. Non-zero indicates loader is
present.
Library Present
Set to 0 indicates no library present. Non-zero indicates library is
present.
Module Revision
A four byte ASCII string representing the revision level of the tape
drive’s module (the controller PCBA attached to the tape drive).
Quantum DLT 4000 Tape Drive
5-23
SCSI Commands
INQUIRY Command (12h) (continued)
5.4.3 Supported Vital Product Data Page (00h)
The Supported Vital Product Data Pages page (Figure 5–7) provides a directory
of the Vital Product Data Pages that are supported by the drive. The pages that
are supported are:
Bit
Byte
0
•
The Unit Serial Number Page (80h)
•
The Firmware Build Information Page (C0h)
7
6
5
4
3
Peripheral Qualifier
2
1
Peripheral Device Type
1
Page Code (00h)
2
Reserved
3
Page Length (3 or more bytes)
4
00h - (this page)
5
80h - Unit Serial Number Page
6
C0h - Firmware Build Information Page (VU)
Figure 5–7 Supported Vital Product Data Pages Page - Data Format
5-24
Quantum DLT 4000 Tape Drive
0
SCSI Commands
INQUIRY Command (12h) (continued)
Bit
Byte
0
7
6
5
4
3
Peripheral Qualifier
2
1
0
Peripheral Device Type
1
Page Code (80h)
2
Reserved
3
Page Length (0Ah)
4 - 13
Serial Number
Figure 5–8 Unit Serial Number Page - Data Format
Table 5–12 Unit Serial Number Page - Field Descriptions
Field Name
Description
Serial Number
The serial number given is the serial number of the module or the drive. If the
drive serial number is valid, then it is reported; otherwise, the module serial
number is reported. The serial number can be found on the bar code label. The
serial number is returned in ASCII.
Quantum DLT 4000 Tape Drive
5-25
SCSI Commands
INQUIRY Command (12h) (continued)
Bit
Byte
7
0
6
5
4
3
Peripheral Qualifier
2
1
0
Peripheral Device Type
1
Page Code (C0h)
2
Reserved
3
Page Length (20h)
4-5
Servo Firmware Checksum
6-7
Servo EEPROM Checksum
8 - 11
Read/Write Firmware Checksum
12 - 35
Read/Write Firmware Build Data
Figure 5–9 Firmware Build Information Page - Data Format
Table 5–13 Firmware Build Information Page - Field Descriptions
Field Name
Description
…Checksum
Servo Firmware, Servo EEPROM, and READ/WRITE Firmware checksums are
given as binary numbers and are for positive firmware and EEPROM
identification.
Firmware Build
Date
Firmware Build Date is an ASCII string in the DD-MMM-YYYY HH:MM:SS
format.
5-26
Quantum DLT 4000 Tape Drive
SCSI Commands
5.5
LOAD UNLOAD COMMAND (1BH)
The LOAD UNLOAD command tells the target to load or unload the tape
media in the tape cartridge. If no cartridge is in the tape drive both LOAD and
UNLOAD return a CHECK CONDITION status with a NOT READY sense key
set. Likewise, if the drive has received an UNLOAD command with the
Immediate bit set and then it receives another command that would require tape
motion or if it receives a TEST UNIT READY command, the drive returns a
CHECK CONDITION STATUS with a NOT READY sense key set.
NOTES
Operation of the UNLOAD version of this command is different if a
media loader is present.
Two modes of operation are possible if a media loader is
configured. If none of the media loader-specific commands have
been issued, the device operates in the sequential mode of
operation described below. Once a media loader-specific command
has been issued, however, the sequential mode of operation is
disabled and the UNLOAD command becomes a NO OPERATION.
If the tape drive is in the default sequential mode of operation and
an UNLOAD command is received by the subsystem, the current
cartridge is unloaded and automatically moved to the magazine slot
from which it was received. The cartridge from the next magazine
slot (if the slot is not empty) automatically moves from the magazine
into the drive, is loaded, and made ready. If the next magazine slot
is empty, no CHECK CONDITION status is created.
When the cartridge is unloaded into the last magazine slot, the
subsystem does not cycle back to slot 0. This prevents accidental
overwriting of data when using a media loader subsystem in
sequential auto-loading mode. The next cartridge in the cycle must
be selected and loaded manually, or with a SCSI MOVE MEDIUM
command.
Quantum DLT 4000 Tape Drive
5-27
SCSI Commands
LOAD UNLOAD Command (1Bh) (continued)
NOTES
The sequential loading feature of the loader can be
enabled/disabled by modifying the ENALDRAUTOLD and
DISLDRAUTOLDMC parameters of EEPROM (mode page 3Eh of the
MODE SELECT command).
A media loader does not affect the tape drive’s processing of the
LOAD portion of the LOAD UNLOAD command.
Bit
Byte
7
6
5
0
1
4
3
1
Logical Unit Number
Reserved
Reserved
3
Reserved
4
Reserved
Unused
Immed
EOT
Reserved
Re-Ten
Load
Flag
Link
Figure 5–10 LOAD UNLOAD Command Descriptor Block - Data Format
5-28
0
Operation Code (1Bh)
2
5
2
Quantum DLT 4000 Tape Drive
SCSI Commands
LOAD UNLOAD Command (1Bh) (continued)
Table 5–14 LOAD UNLOAD Command Descriptor Block - Field Descriptions
Field Name
Description
Immed
Immediate. If this bit is set to 1, status is returned as soon as the operation is
started. If set to 0, status is returned after the operation has completed.
Re-Ten
Re-tension. Re-tension operations are not needed on the tape drive. This bit is
ignored (i.e., “good” status, if bit is set to 1).
Load
Load. When a cartridge is inserted, the tape medium is automatically loaded and
positioned by the drive at Beginning of Medium (BOM). Logically, the drive is
positioned at the beginning of Partition 0.
If the Load bit is set to 1, and the medium is already loaded, no action is taken. If
the medium was unloaded but the cartridge was not removed, a Load command
causes the tape to be loaded to Beginning of Partition (BOP) again and made
ready.
If the Load bit is set to 0, and the medium is loaded, the drive writes any buffered
data and filemarks to the tape and then rewinds the tape to BOM and unloads the
medium back into the cartridge. The green Operate Handle indicator on the tape
drive’s faceplate illuminates and the cartridge can be removed from the tape
drive. If the medium is already unloaded, no action is taken.
EOT
End of Tape. This bit is ignored by the tape drive unless both the EOT and Load
bits are set to 1, then the drive returns CHECK CONDITION, ILLEGAL REQUEST
data.
Quantum DLT 4000 Tape Drive
5-29
SCSI Commands
5.6
LOCATE COMMAND (2BH)
The LOCATE command is used to do high-speed positioning to the specified
block address.
The READ POSITION command can be used to obtain the block address, when
writing, when particular blocks of data (a data file, for example) are about to be
written. The LOCATE command can then be used to position the tape back at
the same logical position for high performance restore operations of particular
blocks of data.
Bit
Byte
7
6
0
5
4
3
2
1
0
BT
CP
Immed
Operation Code (2Bh)
1
Logical Unit Number
2
Reserved
Reserved
(MSB)
3-6
Block Address
(LSB)
7
Reserved
8
Partition
9
Unused
Reserved
Flag
Figure 5–11 LOCATE Command Descriptor Block - Data Format
5-30
Quantum DLT 4000 Tape Drive
Link
SCSI Commands
LOCATE Command (2Bh) (continued)
Table 5–15 LOCATE Command Descriptor Block - Field Descriptions
Field Name
Description
BT
Block Type. The Block Type bit indicates how the Block Address field is
interpreted. The first recorded object (block or filemark) is at address 0, and
Block Addresses count both data blocks and filemarks.
CP
Change Partition. Since multiple partitions are not supported, this bit must be set
to 0.
Immed
Immediate. If this bit is set to 1, status is returned as soon as the operation is
started. If set to 0, status is returned after the operation has completed.
Block Address
The Block Address field defines the SCSI Logical Block Address to which the
media will be positioned. These addresses start at address 0 and include data
blocks and filemarks. They could also be considered an object address.
Partition
Not applicable (see Change Partition field above).
Quantum DLT 4000 Tape Drive
5-31
SCSI Commands
5.7
LOG SELECT COMMAND (4CH)
The LOG SELECT command allows the host to manage statistical information
maintained by the tape drive about its own hardware parameters or about the
installed tape medium. The description should be read in conjunction with the
description of the LOG SENSE command that follows it and provides the user
with information about log page format, parameters, and supported pages.
Bit
Byte
7
6
5
0
4
3
2
1
0
PCR
SP
Operation Code (4Ch)
1
Logical Unit Number (0)
2
Reserved
PC
Reserved
3
Reserved
4
Reserved
5
Reserved
6
Reserved
(MSB)
7-8
Parameter List Length
(LSB)
9
Unused
Reserved
Flag
Figure 5–12 LOG SELECT Command Descriptor Block - Data Format
5-32
Quantum DLT 4000 Tape Drive
Link
SCSI Commands
LOG SELECT Command (4Ch) (continued)
Table 5–16 LOG SELECT Command Descriptor Block - Field Descriptions
Field Name
Description
PCR
Parameter Code Reset. If this bit is set to 1 and the parameter list length 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 is set to a non-zero value, the command terminates with a CHECK
CONDITION status with sense key of ILLEGAL REQUEST and an Additional
Sense Code (ASC) of INVALID FIELD IN CDB.
SP
Save Page. Not supported, must be set to 0. If for some reason the Save
Page bit is set, the command terminates with a CHECK CONDITION status
with a sense key of ILLEGAL REQUEST and an ASC of INVALID FIELD IN CDB.
PC
Page Control. This field defines the type of parameter values to be selected:
PC- Type of Parameter Values
00b - Current Threshold Values
01b - Current Cumulative Values
10b - Default Threshold Values
11b - Default Cumulative Values
All of these types of values are changeable using LOG SELECT.
When the PC field is set to 00b or 01b and the Parameter List Length is set
to 0, the command terminates with a CHECK CONDITION status, Sense Key
of ILLEGAL REQUEST, and ASC of INVALID FIELD IN CDB. This occurs
because modification of Current Threshold Values and Current Cumulative
Values is not supported.
When the PC field is set to 10b and the Parameter List Length field is set to
10b, then all Current Threshold Values are reset to the Default Threshold
Values. This is equivalent to no change, since Threshold Values cannot
be modified.
When the PC field is set to 11b and the Parameter List Length field is set to
0, then all Current Cumulative Values are reset to the Default Cumulative
Values. This is equivalent to clearing all log pages that can be cleared.
Quantum DLT 4000 Tape Drive
5-33
SCSI Commands
LOG SELECT Command (4Ch) (continued)
Table 5–16 LOG SELECT Command Descriptor Block - Field Descriptions (continued)
Field Name
Description
Parameter List
Length
This field specifies the length, in bytes, of the LOG SELECT parameter list to
be transferred from the initiator to the target 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.
5.7.1
Log Detection Summary in LOG SELECT Command Descriptor Block
The following conditions constitute errors that are detected by the drive in
relation to the CDB. The request sense data is set to ILLEGAL REQUEST,
INVALID FIELD IN CDB.
The conditions that constitute errors are:
•
PCR bit is set to 1 and parameter list is not set to 0.
•
SP bit is set to 1
•
5.7.2
A parameter list length that would cause a parameter within a valid page to
be truncated or otherwise incompletely initialized.
Operation of LOG SELECT
The LOG SELECT command allows the initiator to modify and initialize
parameters within the logs supported by the tape drive.
There are two ways to initialize the log parameters.
1.
Set the PCR bit 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:
Page Code
5-34
Page Description
02h
Write Error Counter Page
03h
Read Error Counter Page
32h
Compression Ratio Page
Quantum DLT 4000 Tape Drive
SCSI Commands
LOG SELECT Command (4Ch) (continued)
If multiple pages are sent during the DATA OUT phase, they must be sent in
ascending order according to page code. Otherwise, the command terminates
with a CHECK CONDITION status, sense key set to ILLEGAL REQUEST, and
additional sense code set to INVALID FIELD IN PARAMETER LIST. The same
status is returned if an unsupported Page Code appears in any header or if the
specified page cannot be cleared.
5.7.3
LOG SELECT 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 for parameter
code 05h is comprised of 8 bytes. The parameter block for code 05h is 12 bytes.
Bit
Byte
7
0
6
5
4
3
Reserved
1
2
1
0
Page Code
Reserved
(MSB)
2-3
Page Length
(LSB)
Figure 5–13 LOG SELECT Log Page Header Format
Table 5–17 LOG SELECT Log Page Header Field Descriptions
Field Name
Description
Page Code
The Page Code specifies for which Log Page this LOG SELECT command is
directed.
Page Length
The Page Length field specifies the total number of bytes contained in this log
page, not including the four bytes that make up the header.
Quantum DLT 4000 Tape Drive
5-35
SCSI Commands
LOG SELECT Command (4Ch) (continued)
Bit
Byte
7
6
5
4
3
2
1
0
(MSB)
0 -1
Parameter Code
(LSB)
2
DU
DS
TSD
ETC
3
TMC
Rsvd
LP
Parameter Length
(MSB)
4-7
Parameter Value
(LSB)
NOTE: Byte 2 is also referred to the Parameter Control Byte.
Figure 5–14 LOG SELECT Log Parameters Format
Table 5–18 LOG SELECT Log Parameters Field Descriptions
Field Name
Description
Parameter Code
Parameter Codes supported for the READ/WRITE error counter pages are as
follows:
Parameter Code
-Descriptions
00h - Errors corrected with substantial delays
01h - Errors corrected with possible delays
02h - Total rewrites or rereads
03h - Total errors corrected
04h - Total times correction algorithm processed
05h - Total bytes processed
06h - Total uncorrected errors
8000h - Vendor Unique
5-36
Quantum DLT 4000 Tape Drive
SCSI Commands
LOG SELECT Command (4Ch) (continued)
Table 5–18 LOG SELECT Log Parameters Field Descriptions (continued)
Field Name
Description
Parameter Code
(continued)
Note: Parameter codes 00h, 01h, and 04h always have a value of 0.
Parameter value for 05h is 8 bytes; the parameter length is set to 8.
DU
Disable Update. This bit is not defined for LOG SELECT; the target ignores any
value in DU.
DS
Disable Save. Not supported. DS and Target Save Disable (TSD) must be set to
1. If DS and/or TSD are set to 0, command terminates with CHECK CONDITION
status, sense key set to ILLEGAL REQUEST, and additional sense code set to
INVALID FIELD IN PARAMETER LIST.
TSD
Target Save Disable. Not supported. TDS and DS must be set to 1. If TSD and/or
DS are set to 0, command terminates with CHECK CONDITION status, sense
key set to ILLEGAL REQUEST, and additional sense code set to INVALID FIELD
IN PARAMETER LIST.
ETC
Enable Threshold Comparison. When set to 1, 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 is set to 1, then a UNIT
ATTENTION is generated for all initiators. The additional sense code is set to
THRESHOLD CONDITION MET. If the RLEC bit is 0 and the comparison is met,
then UNIT ATTENTION is not generated.
TMC
Threshold Met Criteria. Once the criteria specified in this field is met and the
ETC bit is 1 and the RLEC bit in MODE SENSE / SELECT Control Page is set to 1,
then UNIT ATTENTION is generated for all initiators.
The criteria for comparison are:
Code - Basis of Comparison
00b - Every update of the cumulative value
01b - Cumulative value equal to threshold value
10b - Cumulative value not equal to threshold value
11b - Cumulative value greater than threshold value
The Default Threshold Values are the maximum values that each parameter
can attain.
Quantum DLT 4000 Tape Drive
5-37
SCSI Commands
LOG SELECT Command (4Ch) (continued)
Table 5–18 LOG SELECT Log Parameters Field Descriptions (continued)
Field Name
Description
TMC
(cont.)
The Current Cumulative Values are the values computed since the last reset of the
device (either via power-cycle, BUS DEVICE RESET, or SCSI RESET.
The Default Cumulative Values are the values to which each parameter is initialized
at a reset condition. Default values are zero.
By default, Current Threshold Values = Default Threshold Values.
Note that all types of parameter values are changeable via LOG SELECT.
LP
List Parameter. This bit should always be set to 0 to indicate parameter codes are
treated as data counters.
Parameter
Length
This field specifies the number of bytes of the parameter value.
Parameter
Value
This field indicates the actual value of this log parameter.
5.7.4
Error Detection Summary in LOG SELECT Pages
The host issues a LOG SENSE command to initialize host-resident software
that allows determination of:
•
The log pages used by the drive
•
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 with sense data set to ILLEGAL
REQUEST and additional send code INVALID FIELD IN PARAMETER LIST:
5-38
•
A page header is received 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
Quantum DLT 4000 Tape Drive
SCSI Commands
5.8
LOG SENSE COMMAND (4DH)
The LOG SENSE command allows the host to retrieve statistical information
maintained by the tape drive about its own hardware parameters or about the
installed tape medium. It is a complementary command to LOG SELECT.
Bit
Byte
7
6
5
0
4
3
2
1
0
PPC
SP(0)
Operation Code (4Dh)
1
Logical Unit Number (0)
2
Reserved
PC
Page Code
3
Reserved
4
Reserved
(MSB)
5-6
Parameter Pointer
(LSB)
(MSB)
7-8
Allocation Length
(LSB)
9
Unused
Reserved
Flag
Link
Figure 5–15 LOG SENSE Command Descriptor Block - Data Format
Quantum DLT 4000 Tape Drive
5-39
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Table 5–19 LOG SENSE Command Descriptor Block - Field Descriptions
Field Name
Description
PPC
Parameter Pointer Control. This bit must be set to 0. A PPC of 0 indicates that the
parameter data requested from the device starts with the parameter code
specified in the Parameter Pointer field (Bytes 5 - 6) and return the number of
bytes specified in the Allocation Length field (Bytes 7 - 8) in ascending order of
parameter codes from the specified log page.
Note that the current implementation of the READ/WRITE COMPRESSION page
does not support a PPC other than 0.
If PPC bit is set, then the target terminates the command with CHECK
CONDITION status, sense key set to ILLEGAL REQUEST, and additional sense code
set to INVALID FIELD IN CDB.
SP
Save Parameters. Not supported, must be set to 0. If for some reason the Save
Parameters bit is set, the command terminates with a CHECK CONDITION status
with a sense key of ILLEGAL REQUEST and an ASC of INVALID FIELD IN CDB.
PC
Page Control. This field defines the type of parameter values to be returned:
PC - Type of Parameter Values
00b - Threshold Values
01b - Cumulative Values
10b - Default Threshold Values
11b - Default Cumulative Values
The Default Threshold Values are the maximum values that each parameter can
attain.
The Current Cumulative Values are the values computed since the last reset of
the device (either via power-cycle, BUS DEVICE RESET, or SCSI RESET.
The Default Cumulative Values are the values to which each parameter is
initialized at a reset condition. Default values are zero.
By default, Current Threshold Values = Default Threshold Values.
Note that all types of parameter values are changeable via LOG SELECT.
5-40
Quantum DLT 4000 Tape Drive
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Table 5–19 LOG SENSE Command Descriptor Block - Field Descriptions (continued)
Field Name
Description
Page Code
The Page Code field identifies which log page is being requested by the initiator.
If the page is not supported, then the command terminates with a CHECK
CONDITION status, sense key set to ILLEGAL REQUEST, and additional sense code
of INVALID FIELD IN CDB. Supported pages are:
Page Code Page Definition
Parameter
Pointer
See Section
00h
List of Supported Pages Page
5.8.2
02h
Write Error Counter Page
5.8.3
03h
Read Error Counter Page
5.8.3
07h
Last n Errors Events Page
5.8.4
32h
Compression Ratio Page
5.8.5
33h
Device Wellness Log Page
5.8.6
3Eh
Device Status Log Page
5.8.7
The Parameter Pointer field allows the host to specify at which parameter within
a log page the requested data should begin. For example, if a page supports
parameters 0 through 5, and the Parameter Pointer contains 3, then only
parameters 3, 4, and 5 are returned to the initiator. Similarly, if a page supports
parameters 1, 3, and 6, and the Parameter Pointer contains 2, then only
parameters 3 and 6 are returned to the initiator.
If the Parameter Pointer is larger than the highest numbered parameter on the
page, then the target terminates the command with CHECK CONDITION status,
sense key set to ILLEGAL REQUEST, and additional sense code set to INVALID
FIELD IN CDB.
Note that parameters within a page are always returned in ascending order
according to parameter code.
If the target does not support a parameter code within this page then it does not
return any data associated with this parameter.
Allocation
Length
The Allocation Length field is used to inform the target how much space the
initiator has allocated for data. There must be sufficient space allocated for all the
requested data, or the command terminates with a CHECK CONDITION status,
sense key set to ILLEGAL REQUEST, and additional sense code set to INVALID
FIELD IN CDB.
Quantum DLT 4000 Tape Drive
5-41
SCSI Commands
LOG SENSE Command (4Dh) (continued)
5.8.1
Error Detection Summary in LOG SENSE Command Descriptor Block
The following conditions constitute errors detected by the drive relating to the
LOG SENSE command descriptor block. The request sense data is set to
ILLEGAL REQUEST, INVALID FIELD IN CDB.
Error conditions occur when:
•
•
5-42
A page is not supported
The parameter pointer is larger than the highest numbered parameter on the
page
•
The SP bit is set to 1
•
The Allocation Length is smaller than the data being returned by the target.
•
PPC bit is set to 1
Quantum DLT 4000 Tape Drive
SCSI Commands
LOG SENSE Command (4Dh) (continued)
5.8.2
Supported Pages Log Page (Page 00h)
When page 00h is requested, the 4-byte page header is returned, followed by the
pages supported in ascending order, one byte for each.
Bit
Byte
7
0
6
5
4
3
Reserved
1
2
1
0
Page Code (00h)
Reserved
(MSB)
2-3
Page Length (07h)
(LSB)
4
00h
5
02h
6
03h
7
07h
8
32h
9
33h
10
3Eh
Figure 5–16 Supported Pages Page - Data Format
Quantum DLT 4000 Tape Drive
5-43
SCSI Commands
LOG SENSE Command (4Dh) (continued)
5.8.3
Read (Page 03h) / Write (Page 02h) Error LOG SENSE Page
Each Log page begins with a 4-byte header followed by a number of log
parameter blocks. Each block consists of 8 bytes except for parameter code 05h.
The log parameter block for the parameter total bytes processed (05h) is 12
bytes, since the parameter value is 8 bytes long.
7
6
5
4
3
2
1
0
Bit
Byte
0
Reserved
1
Page Code
Reserved
(MSB)
2-3
Page Length
(LSB)
Figure 5–17 Read / Write Error LOG SENSE Header Format
Table 5–20 Read / Write Error LOG SENSE Header Field Descriptions
Field Name
Description
Page Code
The Page Code echoes the page code that was specified in the LOG SENSE
command descriptor block.
Page Length
The Page Length field specifies the total number of bytes contained in this log
page, not including the four bytes that make up the header.
For example, if the PPC bit is 0 and the parameter pointer is 0, the target returns 4
bytes of page header with page length of 44h followed by 8 bytes of parameter
value data for each parameter code except code 05h (for code 05h, it returns 12
bytes). Therefore, for parameter codes 00h, 01h, 02h, 03h, 04h, 06h, and 8000h,
each page will be 8 bytes.
5-44
Quantum DLT 4000 Tape Drive
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Bit
Byte
7
6
5
4
3
2
1
0
(MSB)
0 -1
Parameter Code
(LSB)
2
DU
DS
TSD
3
ETC
TMC
Rsvd
LP
Parameter Length
(MSB)
4 - 11
Parameter Value
(LSB)
NOTE: Byte 2 is also referred to the Parameter Control Byte.
Figure 5–18 Log Parameters Format for Read / Write Error LOG SENSE Page
Table 5–21 Log Parameters for Read / Write Error LOG SENSE Page Field Descriptions
Field Name
Description
Parameter
Code
Parameter Codes supported for the READ/WRITE error counter pages are as follows:
Parameter Code - Description
00h - Errors corrected with substantial delays
01h - Errors corrected with possible delays
02h - Total rewrites or rereads
03h - Total errors corrected
04h - Total times correction algorithm processed
05h - Total bytes processed
06h - Total uncorrected errors
Quantum DLT 4000 Tape Drive
5-45
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Table 5–21 Log Parameters for Read / Write Error LOG SENSE Page Field Descriptions
(continued)
Field Name
Description
Parameter Code
(continued)
8000h - Vendor Unique
DU
Disable Update. This field with a value 0 indicates that the target will update all
log parameter values. This field set to 1 indicates that the target will not update
the log parameter values except in response to LOG SELECT. This bit is set by the
drive when accumulated values reach maximum. This is also returned set to 1 if
the host set the bit in the last LOG SELECT command. Default is 0.
Note: Parameter codes 00h, 01h, and 04h always return a value of 0. Parameter
value for 05h is 8 bytes; the parameter length is set to 8.
Note that for parameter types other than threshold and cumulative values, this
bit is always 0.
DS
Disable Save. Not supported; always set to 1.
TSD
Target Save Disable. Not supported; always set to 1.
ETC
Enable Threshold Comparison. When set to 1, indicates that comparison to
threshold is performed. ETC of 0 indicates that the comparison is not performed.
This bit is set to 1 by MODE SELECT. Default is 0.
TMC
Threshold Met Criteria. This field is valid only if host sets ETC to 1. It determines
the basis for comparison and is specified by host using LOG SELECT. If the result
of comparison is true (cumulative = threshold), and MODE SELECT / SENSE
CONTROL MODE page RLEC bit is set to 1, then a UNIT ATTENTION is granted for
all initiators. The sense key is set to UNIT ATTENTION, the additional sense code
to LOG EXCEPTION, and ASCQ is set to THRESHOLD CONDITION MET. If the RLEC
bit in CONTROL MODE page is 0, then UNIT ATTENTION is not generated.
Note that comparison is performed in real time. A Log Sense command need
not be issued to get the CHECK CONDITION. Once ETC is selected, RLEC bit in
control mode page, the CHECK CONDITION is issued based on the criteria
defined in the TMC bits if the criteria are met in real time. CHECK CONDITION will
not identify for which parameter code the criteria is met. Log Sense must be
issued to read the counters to determine for which parameter code criteria has
been met.
5-46
Quantum DLT 4000 Tape Drive
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Table 5–21 Log Parameters for Read / Write Error LOG SENSE Page Field Descriptions
(continued)
Field Name
Description
TMC (cont.)
The criteria for comparison are:
Code - Basis of Comparison
00b - Every update of the cumulative value
01b - Cumulative value equal to threshold value
10b - Cumulative value not equal to threshold value
11b - Cumulative value greater than threshold value
LP
List Parameter. This bit is 0 since the parameter codes are treated as data counters.
Parameter
Length
This field specifies the number of bytes of the parameter value.
Parameter
Value
This field indicates the actual value of this log parameter.
5.8.4
Last n Error Events Page (07h)
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; only a limited number of events are stored at
a given time (up to 14). The log event that is returned is the one whose
Parameter Code is equal to, or the first one greater than, the Parameter Number
specified in the command control block.
Quantum DLT 4000 Tape Drive
5-47
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Bit
Byte
7
0
6
5
4
3
Reserved
1
2
1
0
Page Code (07h)
Reserved
(MSB)
2-3
Page Length
(LSB)
Figure 5–19 Last n Error Events LOG SENSE Header Format
Table 5–22 Last n Error Events LOG SENSE Header Field Descriptions
Field Name
Description
Page Code
The Page Code echoes the page code that was specified in the LOG SENSE
command descriptor block.
Page Length
The Page Length field specifies the total number of bytes contained in this log
page, not including the four bytes that make up the header.
5-48
Quantum DLT 4000 Tape Drive
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Bit
Byte
7
6
5
4
3
2
1
0
(MSB)
0 -1
Parameter Code
(LSB)
2
DU
DS
3
TSD
ETC
TMC
Rsvd
LP
Parameter Length
(MSB)
4-n
Hex ASCII String for Event n
(LSB)
Figure 5–20 Log Parameters Format for Last n Error Events LOG SENSE Page
Table 5–23 Log Parameters for Last n Error Events LOG SENSE Page Field Descriptions
Field Name
Description
Parameter Code
Parameter Code values are assigned from 0 to 27 (decimal), where 0 is the
oldest event stored and the highest Parameter Code returned is the most
recent event.
Hex ASCII String
for Event n
The text of the parameter includes a “Packet #” that is a value from 0 to 255.
This internal number is assigned when the packet is written to EEPROM. A
value of 0 is normally the oldest packet, but packet numbers can wrap around
back to 0 after reaching 255. For a detailed description of the packet string,
see Appendix D.
Quantum DLT 4000 Tape Drive
5-49
SCSI Commands
LOG SENSE Command (4Dh) (continued)
5.8.5
Read / Write Compression Page (32h)
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
7
0
6
5
4
3
Reserved
1
2
1
0
Page Code (32h)
Reserved
(MSB)
2-3
Additional Length
(LSB)
Figure 5–21 Read / Write Compression Ratio LOG SENSE Header Format
Table 5–24 Read / Write Compression Ratio LOG SENSE Header Field Descriptions
Field Name
Description
Page Code
The Page Code echoes the page code that was specified in the LOG SENSE
command descriptor block.
Additional
Length
The Additional Length field specifies the number of bytes available and
depends on the parameters requested.
5-50
Quantum DLT 4000 Tape Drive
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Bit
Byte
7
6
5
4
3
2
1
0
(MSB)
0 -1
Parameter Code
(LSB)
2
DU
DS
TSD
ETC
3
TMC
Rsvd
LP
02h
(MSB)
4-n
Compression Ratio x 100
(LSB)
Figure 5–22 Log Parameters Format for Read / Write Compression Ratio LOG SENSE
Page (Parameter Codes 00h and 01h)
Table 5–25 Log Parameters for Read / Write Compression Ratio LOG SENSE Page Field
Descriptions (Parameter Codes 00h and 01h)
Field Name
Description
Parameter Code
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):
Parameter Code - Description
00h - READ Compression Ratio x 100
01h - WRITE Compression Ration x 100
DU
Disable Update. Always 0.
DS
Disable Save. Not supported. This bit always set to 1.
TSD
Target Save Disable. Not supported. This bit always set to 1.
ETC
Enable Threshold Comparison. Threshold checking is not supported on this
page. Always set to 0.
TMC
Threshold Met Criteria. Always 0.
LP
List Parameter. Always set to 0 (parameter codes treated as data counter).
Quantum DLT 4000 Tape Drive
5-51
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Bit
Byte
7
6
5
4
3
2
1
0
(MSB)
0 -1
Parameter Code
(LSB)
2
DU
DS
TSD
3
ETC
TMC
Rsvd
LP
04h
(MSB)
4-7
Counter Value
(LSB)
Figure 5–23 Log Parameters Format for Read / Write Compression Ratio LOG SENSE
Page (Parameter Codes 02h through 09h)
Table 5–26 Log Parameters for Read / Write Compression Ratio LOG SENSE Page Field
Descriptions (Parameter Codes 02h through 09h)
Field Name
Description
Parameter Code
Parameter Codes supported for the READ / WRITE COMPRESSION
RATIO page (codes 02h through 09h) are as follows:
Parameter Code - Description
02h - Mbytes Transferred to Host
03h - Bytes Transferred to Host
04h - Mbytes Read from Tape
05h - Bytes Read from Tape
06h - Mbytes Transferred from Host
07h - Bytes Transferred from Host
08h - Mbytes Written to Tape
09h - Bytes Written to Tape
5-52
Quantum DLT 4000 Tape Drive
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Table 5–26 Log Parameters for Read / Write Compression Ratio LOG SENSE Page Field
Descriptions (Parameter Codes 02h through 09h) (continued)
Field Name
Description
DU
Disable Update. Always 0.
DS
Disable Save. Not supported. This bit always set to 1.
TSD
Target Save Disable. Not supported. This bit always set to 1.
ETC
Enable Threshold Comparison. Threshold checking is not supported on this
page. Always set to 0.
TMC
Threshold Met Criteria. Always 0.
LP
List Parameter. Always set to 0 (parameter codes treated as data counter).
Counter
Value
Parameter Codes 02h through 09h provide a count of the number of bytes
transferred since the current tape cartridge was inserted or since the last time
the counters were reset via a MODE SELECT command.
Parameter Codes 02h and 03h -- Report the count of bytes transferred from
the tape drive to the initiator. Parameter Code 02h reports the number of full
megabytes transferred; Parameter Code 03h reports the number of bytes less
than a full megabyte that have been transferred. Multiplying the counter
returned for Parameter Code 02h by 1,048,576 and then adding the value of
the counter returned by Parameter Code 03h results in the actual total bytes
transferred to the initiator.
Parameter Codes 04h and 05h -- Report the count of bytes transferred from
the tape drive to the buffer. Parameter Code 04h reports the number of full
megabytes transferred; Parameter Code 05h reports the number of bytes less
than a full megabyte that have been transferred. Multiplying the counter
returned for Parameter Code 04h by 1,048,576 and then adding the value of
the counter returned by Parameter Code 05h results in the actual total bytes
transferred from tape to the buffer.
Quantum DLT 4000 Tape Drive
5-53
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Table 5–26 Log Parameters for Read / Write Compression Ratio LOG SENSE Page Field
Descriptions (Parameter Codes 02h through 09h) (continued)
Field Name
Description
Counter
Value
(cont.)
Parameter Codes 06h and 07h -- Report the count of bytes transferred from
the initiator to the buffer. Parameter Code 06h reports the number of full
megabytes transferred; Parameter Code 07h reports the number of bytes less
than a full megabyte that have been transferred. Multiplying the counter
returned for Parameter Code 06h by 1,048,576 and then adding the value of
the counter returned by Parameter Code 07h results in the actual total bytes
transferred from the initiator to the buffer.
Parameter Codes 08h and 09h -- Report the count of bytes written to the tape
drive. Parameter Code 08h reports the number of full megabytes transferred;
Parameter Code 09h reports the number of bytes less than a full megabyte
that have been transferred. Multiplying the counter returned for Parameter
Code 08h by 1,048,576 and then adding the value of the counter returned by
Parameter Code 09h results in the actual total bytes written to the tape drive.
5-54
Quantum DLT 4000 Tape Drive
SCSI Commands
LOG SENSE Command (4Dh) (continued)
5.8.6
Device Wellness Page (33h)
The Device Wellness Page returns information about any check conditions
related to Sense Keys 1, 3, 4, and 9 logged by the tape drive. Up to 16 entries
(parameter code 0000h to 000Fh) can be contained in the page; each entry
records a check condition (Sense Key = 1), a medium error (Sense Key = 3), or
hardware error (Sense Key = 4). Note that parameter code 000h contains the
oldest log information while parameter 000Fh contains the most recent.
Only head cleaning recovered errors (more serious recovered errors) are recorded
when Sense Key is 1; all sense data are recorded when Sense Key is 3 or 4.
This page begins with a 4-byte header followed by the log parameter blocks.
Bit
Byte
7
0
6
5
4
3
Reserved
2
1
0
Page Code (33h)
1
Reserved
(MSB)
2-3
Page Length
(LSB)
Figure 5–24 Device Wellness LOG SENSE Header Format
Table 5–27 Device Wellness LOG SENSE Header Field Descriptions
Field Name
Description
Page Code
The Page Code echoes the page code that was specified in the
LOG SENSE command descriptor block.
Page Length
The Page Length field specifies the number of bytes available and
depends on the parameters requested.
Quantum DLT 4000 Tape Drive
5-55
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Bit
Byte
7
6
5
0
4
3
2
1
0
Rsvd
LP
Parameter Code
1
Reserved
2
DU
DS
TSD
ETC
TMC
(MSB)
3-7
Time Stamp
(LSB)
(MSB)
8 - 11
Media ID
(LSB)
12
Sense Key
13
Additional Sense Key
15
Additional Error Information
Figure 5–25 Log Parameters Format for Device Wellness LOG SENSE Page (Parameters
0000h – 000Fh)
5-56
Quantum DLT 4000 Tape Drive
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Table 5–28 Log Parameters for Device Wellness LOG SENSE Page Field Descriptions
Field Name
Description
Parameter
Code
Parameter Codes 0000h through 000Fh are supported. This provides 16 log entries for
error information capture.
DU
Disable Update. Always 0.
DS
Disable Save. Not supported. This bit always set to 1.
TSD
Target Save Disable. Not supported. This bit always set to 0.
ETC
Enable Threshold Comparison. Threshold checking is not supported on this page.
Always set to 0.
TMC
Threshold Met Criteria. Always 0.
LP
List Parameter. Always set to 0.
Time
Stamp
Power-on hours when CHECK CONDITION occurred (note that this is the number of
power-on hours of the total number of hours during the lifetime of the drive).
Media ID
Internal media identifier being used when CHECK CONDITION occurred. 0 = no media
or unknown media when event occurred. Note that this is not an applicable means of
tracing media.
Quantum DLT 4000 Tape Drive
5-57
SCSI Commands
LOG SENSE Command (4Dh) (continued)
5.8.7
Device Status Page (3Eh)
The Device Status Page describes the current status of the tape drive. Three
parameters are defined in this page; each is four bytes in length.
Bit
Byte
Parameter Code
Description
0000h
Device Type (for sequential devices such as tape drives,
this value is always 00010000h)
0001h
Device Cleaning-Related Status
0002h
Number of “loads” over the life of the tape drive.
7
0
6
5
4
3
Reserved
2
1
0
Page Code (3Eh)
1
Reserved
(MSB)
2-3
Page Length
(LSB)
Figure 5–26 Device Status LOG SENSE Header Format
Table 5–29 Device Status LOG SENSE Header Field Descriptions
5-58
Field Name
Description
Page Code
The Page Code echoes the page code that was specified in the
LOG SENSE command descriptor block.
Page Length
The Page Length field specifies the number of bytes available
and depends on the parameters requested.
Quantum DLT 4000 Tape Drive
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Bit
Byte
7
6
5
4
0-1
2
3
2
1
0
Rsvd
LP
Parameter Code
DU
DS
TSD
3
ETC
TMC
Parameter Length (04h)
(MSB)
4-7
Parameter Value
(LSB)
Figure 5–27 Log Parameters Format for Device Status LOG SENSE Page
0000h, 0001h, or 0002h)
(Parameters
Table 5–30 Log Parameters for Device Status LOG SENSE Page Field Descriptions
Field Name
Description
Parameter Code
Parameter Codes 0000h through 0002h are supported.
Code - Description
0000h - Specifies device type. For sequential-type devices such as tape drives,
the value is always 00010000h.
0001h - Specifies device cleaning-related status. See Figure 5-28.
0002h - Specifies the number of “loads” over the lifetime of the tape drive.
DU
Disable Update. Always 0.
DS
Disable Save. Not supported. This bit always set to 1.
TSD
Target Save Disable. When = 0, indicates that the target provides a targetdefined method for saving log parameters. When = 1, indicates that either the
target does not provide a defined method for saving log parameters or that the
target-defined method has been disabled by the initiator.
Quantum DLT 4000 Tape Drive
5-59
SCSI Commands
LOG SENSE Command (4Dh) (continued)
Table 5–30 Log Parameters for Device Status LOG SENSE Page Field Descriptions
(continued)
Field Name
Description
ETC
Enable Threshold Comparison. Threshold checking is not supported on this
page. Always set to 0.
TMC
Threshold Met Criteria. Always 0.
LP
List Parameter. Always set to 0 (parameter codes treated as data counter).
Bit
Byte
7
6
0
5
4
3
Reserved
2
1
0
ClnR
ClnQ
ClnEx
(MSB)
1-3
Reserved
(LSB)
Figure 5–28 Log Parameters Format for Device Status LOG SENSE Page Parameter
0001h (Cleaning Related)
Table 5–31 Log Parameters for Device Status LOG SENSE Parameter 0001h (Cleaning
Related) Field Descriptions
5-60
Field Name
Description
ClnR
Set to 1 if a cleaning required condition exists.
ClnQ
Set to 1 if a cleaning request condition exists.
ClnEx
Set to 1 if the cleaning tape has expired.
Quantum DLT 4000 Tape Drive
SCSI Commands
5.9
MODE SELECT (6) / (10) COMMAND (15H / 55H)
The MODE SELECT command (available in either 6- or 10-byte format) enables
the host to configure the tape drive. Implementing MODE SELECT and MODE
SENSE requires “handshaking” between the host and the drive. Before
configuring the drive, the host should issue a MODE SENSE command to the
drive to obtain a report of the current configuration and determine what
parameters are configurable. The host interprets this information and then may
issue MODE SELECT to set the drive to the host’s preferred configuration. The
Mode Parameter List described in Section 5.8 is passed from the initiator to the
drive during the command’s DATA OUT phase.
Information for the drive is carried on a number of pages, each of which serves
to set the tape drive’s operating parameters. The MODE SELECT pages
supported, and the section of this manual that details each page, are:
Page Code
Description
Section
01h
READ/WRITE Error Recovery Page
5.9.2
02h
Disconnect / Reconnect Page
5.9.3
0Ah
Control Mode Page
5.9.4
0Fh
Data Compression Page
5.9.5
10h
Device Configuration Page
5.9.6
11h
Medium Partition Page
5.9.7
3Eh
EEPROM Vendor Unique Page
5.9.8
The tape drive always powers up with its default configurations set. This is also
true if the drive receives a BUS DEVICE RESET message or a hard reset via the
RST line on the SCSI bus.
The Command Descriptor Block is illustrated in Figure 5-29.
NOTE
For a list of changeable parameters within MODE SELECT, refer to
Sections 5.9.8 (EEPROM Vendor Unique Page 3Eh) and 5.9.9
(Changeable Parameters within MODE SELECT).
Quantum DLT 4000 Tape Drive
5-61
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Mode Select (6) Command Descriptor Block – Data Format
Bit
Byte
7
6
5
0
4
3
1
0
Operation Code (15h)
1
Logical Unit Number
PF
Reserved
2-3
Reserved
4
Parameter List Length
5
2
Unused (00)
Reserved
SP (0)
Flag
Link
1
0
Mode Select (10) Command Descriptor Block – Data Format
Bit
Byte
7
6
0
1
5
4
3
Operation Code (55h)
Logical Unit Number
PF
Reserved
2-6
Reserved
7-8
Parameter List Length
9
2
Unused (00)
Reserved
SP (0)
Flag
Link
Figure 5–29 MODE SELECT (6) and (10) Command Descriptor Blocks - Data Format
5-62
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–32 MODE SELECT (6) /(10) Command Descriptor Block - Field Descriptions
Field Name
Description
PF
Page Format. The Page Format bit indicates that the data sent by the host after the
MODE SELECT header and block descriptors complies with the definition of pages in
the SCSI-2 specification. The SCSI-1 format will not be implemented so this bit must
be set to 1. It is an ILLEGAL REQUEST to have page parameters while the PF bit is 0.
SP
Save Parameters. Must be 0. If set, this bit instructs the drive to save all savable pages,
and this is not supported on the tape drive.
5.9.1
Mode Parameter List
The following figure shows the format of the Mode Parameter List that is passed
by the initiator to the tape drive during the command’s DATA OUT phase.
Bit
Byte
7
6
5
4
3
2
0-3
Mode Parameter Header
4 - 11
Mode Parameter Block Descriptor (Optional)
4 - 11
or
12 - n
Page(s) (Optional)
1
0
Figure 5–30 MODE SELECT Mode Parameter List - Data Format
Quantum DLT 4000 Tape Drive
5-63
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–33 MODE SELECT Mode Parameter List - Field Descriptions
Field Name
Description
Mode Parameter
Header
4 bytes in length, contains information about the remainder of the
Parameter List and is always present (Figure 5-31 and Table 5-34).
Mode Parameter
Block Descriptor
8 bytes in length, allows the initiator to set the drive’s Logical Block Size
and number of Descriptor Logical Block Addresses (Figure 5-32 and Table
5-35).
Page(s)
The Page Code(s) of the pages that are a part of this MODE SELECT
command.
5.9.1.1 Mode Parameter Header
The figure and table that follow provide an illustration and description of the
fields that make up the MODE SELECT command’s Mode Parameter header.
Bit
Byte
7
6
5
4
3
0
Reserved
1
Media Type
2
3
Ignored
2
Buffered Mode
1
Speed
Block Descriptor Length (08h)
Figure 5–31 MODE SELECT Mode Parameter Header - Data Format
5-64
Quantum DLT 4000 Tape Drive
0
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–34 MODE SELECT Mode Parameter Header - Field Descriptions
Field Name
Description
Media Type
This field is ignored by the MODE SELECT command.
Buffered Mode
Default = 1. The drive implements immediate reporting on WRITE
commands through its buffered mode. With Buffered Mode set to 1, the
drive reports GOOD status on WRITE commands as soon as the data
block has been transferred to the buffer. If this field = 0, then the drive
does not report GOOD status on WRITE commands until the data blocks
have been written to tape.
When Buffered Mode is not used, the tape drive suffers significant
performance degradation, and possible capacity, depending on tape
format, block size, and compression. When writing 2.6 or 6.0 GB formats
and block size that is a multiple of 4 Kbytes, there is no capacity loss.
Likewise, when using the 10 or 20 GB format with compression disabled
and block size a multiple of 8 Kbytes, there is no capacity loss.
When writing 10 or 20 GB format with compression enabled and
Buffered Mode disabled, some capacity loss can occur. The block packing
feature is essentially disabled by turning off Buffered Mode.
If Buffered Mode is set to a number greater than 1, the command is
rejected with CHECK CONDITION, sense key of ILLEGAL REQUEST.
Speed
The tape drive supports only its default speed.
Block Descriptor
Length
This field specifies the length in bytes of all the block descriptors. Since
the drive only allows one block description, the value must be either 0 or
8. A value of 0 indicates no block description is included; a value of 8
indicates a block descriptor is present and precedes the mode page data.
Any other value other than 0 or 8 causes a CHECK CONDITION status with
sense key of ILLEGAL REQUEST to be returned.
Quantum DLT 4000 Tape Drive
5-65
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
5.9.1.2 Mode Parameter Block Descriptor
The figure and table that follow provide an illustration and description of the
fields that make up the MODE SELECT command’s Mode Parameter Block
Descriptor.
Bit
Byte
7
0
6
5
4
3
2
1
0
Density Code
(MSB)
1-3
Number of Blocks
(LSB)
4
Reserved
(MSB)
5-7
Block Length
(LSB)
Figure 5–32 MODE SELECT Mode Parameter Block Descriptor - Data Format
5-66
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–35 MODE SELECT Mode Parameter Block Descriptor - Field Descriptions
Field Name
Description
Density Code
This field should match the current tape medium density; it is set to 0 if the density
is unknown.
Density Code
00h
0Ah
16h
17h
Description
Use default density.
6667 bpi MFM serial cartridge tape X3B5/86-199 (read only).
10000 bpi MFM serial cartridge tape X3.193-1990 (read only).
42500 bpi MFM serial cartridge tape X3B5/91- 2.6 GB (DLTtape III
only).
18h
Same as 17h, but with 56 track pairs vs. 24 - 6.0 GB (DLTtape III
only).
19h
62500 bpi, 64 track pairs, serial cartridge tape - 10.0 GB (DLTtape
III only) /15.0 GB (DLTtape IIIxt only)
1Ah
81633 bpi, 64 track pairs, serial cartridge tape - 20.0 GB (DLTtape
IV only)
The density codes above are the preferred codes used to define density.
Additionally, the following codes may be used, though use of the Data
Compression Page is preferred:
80h
Number of
Blocks
62500 bpi, 64 track pairs, serial cartridge tape - 10.0 GB (DLTtape III)
/15.0 GB (DLTtape IIIxt) without compression
81h
62500 bpi, 64 track pairs, serial cartridge tape - 20.0 GB (DLTtape III)
/30.0 GB (DLTtape IIIxt) with compression
82h
81633 bpi, 64 track pairs, serial cartridge tape - 20.0 GB (DLTtape IV)
without compression
83h
81633 bpi, 64 track pairs, serial cartridge tape - 40 GB (DLTtape IV) with
compression
This MODE SENSE field is sent = 0, indicating that all of the remaining logical blocks
on the tape will have the medium characteristics specified by the block descriptor.
Quantum DLT 4000 Tape Drive
5-67
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–35 MODE SELECT Mode Parameter Block Descriptor - Field Descriptions
(continued)
Field Name
Description
Block Length
This field specifies the length, in bytes, of each logical block transferred over the
SCSI bus. A block length of 0 indicates that the length is variable (specified in the I/O
command). Any value other than 0 indicates the number of bytes per block to use
for READ, WRITE, and VERIFY commands that specify a “fixed” bit of 1 (i.e., fixed
block mode) which also causes the transfer length in the command descriptor
block to be defined as a block count. If fixed bit is not equal to 1, this field is
ignored.
5.9.1.3 Mode Page Descriptors
Following the MODE SELECT command’s Mode Parameter Block Descriptor are
the MODE SELECT pages, each of which sets a different device parameter. Each
mode page has a 2-byte header that identifies the page code and indicates the
number of bytes in that page.
Bit
Byte
0
7
6
PS (0)
0
5
4
3
2
Page Code
1
Additional Page Length
2-n
Page-Defined or Vendor Unique Parameter List
Figure 5–33 MODE SELECT Page Descriptor - Data Format
5-68
Quantum DLT 4000 Tape Drive
1
0
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–36 MODE SELECT Page Descriptor - Field Descriptions
Field Name
Description
PS
Parameters Savable. For the MODE SELECT (6) (10) commands, this field
is reserved (0).
Additional Page Length
Indicates number of bytes in that page (not including bytes 0 and 1).
Page-Defined or Vendor
Unique Parameter List
Information in this field depends on the mode page. Refer to Sections
5.9.2 through 5.9.9.
Quantum DLT 4000 Tape Drive
5-69
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
5.9.2
READ / WRITE Error Recovery Page (01h)
The READ / WRITE Error Recovery Page controls the drive’s response to error
conditions that arise during the course of READ and WRITE command
processing.
Bit
Byte
0
7
6
PS (0)
0
5
3
2
0
DTE (0)
DCR (0)
Additional Page Length (0Ah)
Rsvd
Rsvd
TB
Rsvd
EER (1)
3
Read Retry Count
4–7
Reserved
8
Write Retry Count
9 – 11
Reserved
PER
Figure 5–34 Error Recovery Page - Data Format
5-70
1
Page Code (01h)
1
2
4
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–37 Error Recovery Page - Field Descriptions
Field Name
Description
PS
Parameters Savable. For MODE SELECT, this bit must be 0.
Additional Page
Length
This field indicates the number bytes in the page. However, the value does
not include bytes 0 and 1. The length is returned in MODE SENSE
commands and must subsequently be set to the same value when
performing MODE SELECT. If the page length does not match that
expected by the drive, a CHECK CONDITION status is returned, sense key set
to ILLEGAL REQUEST.
The drive returns a CHECK CONDITION status with sense key set to ILLEGAL
REQUEST if it receives an unsupported Page Code or a Page field with
values not supported or changeable. In such cases, no parameters are
changed as a result of the command.
TB
Transfer Block. Not supported.
EER
Enable Early Recovery. Set to 1 (always enabled).
PER
Post Error. Default is 0. If set to 1, this bit enables reporting of CHECK
CONDITION to report recovered READ / WRITE errors.
DTE
Disable Transfer on Error. Must be 0. Not supported.
DCR
Disable ECC Correction. Must be 0. Not supported.
Read Retry Count
This field reports the maximum number or rereads that are attempted
before declaring an unrecoverable error.
Write Retry Count
This field reports the maximum number of overwrite retries that will be
attempted before declaring an unrecoverable error.
5.9.3
Disconnect / Reconnect Page (02h)
The Disconnect / Reconnect Page controls the drive’s behavior on the SCSI bus
and allows an initiator to tune bus performance.
Quantum DLT 4000 Tape Drive
5-71
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Bit
Byte
0
7
6
PS (0)
0
5
4
3
2
1
0
Page Code (02h)
1
Additional Page Length (0Eh)
2
Buffer Full Ratio
3
Buffer Empty Ratio
(MSB)
4-5
Bus Inactivity Limit
(LSB)
(MSB)
6-7
Disconnect Time Limit
(LSB)
(MSB)
8-9
Connect Time Limit
(LSB)
(MSB)
10 - 11
Maximum Burst Time
(LSB)
12
13 - 15
Reserved
DTDC
Reserved
Figure 5–35 Disconnect / Reconnect Page - Data Format
5-72
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–38 Disconnect / Reconnect Page - Field Descriptions
Field Name
Description
PS
Parameters Savable. For MODE SELECT, this bit must be 0.
Additional Page Length
This field indicates the number bytes in the page. However, the value
does not include bytes 0 and 1. The length is returned in MODE
SENSE commands and must subsequently be set to the same value
when performing MODE SELECT. If the page length does not match
that expected by the drive, a CHECK CONDITION status is returned,
sense key set to ILLEGAL REQUEST.
The drive returns a CHECK CONDITION status with sense key set to
ILLEGAL REQUEST if it receives an unsupported Page Code or a Page
field with values not supported or changeable. In such cases, no
parameters are changed as a result of the command.
Buffer Full Ratio
Not supported. Any value is ignored.
Buffer Empty Ratio
Not supported. Any value is ignored.
Bus Inactivity Limit
Not supported. Any value is ignored.
Disconnect Time Limit
Not supported. Any value is ignored.
Connect Time Limit
Not supported. Any value is ignored.
Maximum Burst Size
This value specifies the maximum amount of data that will be
transferred without disconnecting. A value of 0 sets no limit. Any
value is in units of 512 bytes. For example, a value of 8 represents 4
Kbytes. Values that are not multiples of 8 are rounded up to the
closest multiple of 8.
Quantum DLT 4000 Tape Drive
5-73
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–38 Disconnect / Reconnect Page - Field Descriptions (continued)
Field Name
Description
DTDC
Data Transfer Disconnect Control. This field defines further restrictions
for when disconnect is permitted.
DTDC
Description
00b
Data transfer disconnect control is not used. Disconnect is
controlled by the other fields in this page.
01b
Once the data transfer of a command has been started, a
target does not attempt to disconnect until all the data to be
transferred has been transferred.
10b
Reserved.
11b
Once the data transfer of a command has started, a target
does not attempt to disconnect until the command is
complete.
If DTDC is a non-zero value and the maximum burst size is non-zero,
the tape drive returns CHECK CONDITION status, sense key set to
ILLEGAL REQUEST and additional sense code set to ILLEGAL FIELD IN
PARAMETER LIST.
5-74
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
5.9.4
Control Mode Page (0Ah)
The Control Mode page provides control over several features such as tagged
queuing, extended contingent allegiance, asynchronous event notification, and
error logging.
Bit
Byte
0
7
6
PS (0)
Rsvd
5
4
2
1
0
Page Code (0Ah)
1
Page Length (06)
2
Reserved
3
4
3
Queue Algorithm Modifier (0)
EECA (0)
5
RLEC
Reserved
Reserved
RAENP
(0)
Qerr (0)
DQue (0)
UAAENP
EAENP
(0)
Reserved
(MSB)
6-7
Ready AEN Holdoff Period (0)
(LSB)
Figure 5–36 Control Mode Page Format Descriptor - Data Format
Quantum DLT 4000 Tape Drive
5-75
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–39 Control Mode Page Descriptor - Field Descriptions
Field Name
Description
PS
Parameters Savable. For MODE SELECT, this bit must be 0.
Page Length
The Page Length field indicates the number of bytes in the Control
Mode Page that follow this byte. The valid value for this byte is 06h.
RLEC
Report Log Exception Condition. When set to 1, specifies that the
target will report log exception conditions. When 0, specifies that the
target will not report log exception conditions.
The RLEC bit works in conjunction with the READ / WRITE Error Log
Sense Page, specifically, the TMC bit of the READ / WRITE Error Log
SENSE Page (Page 2 and 3), described earlier in this manual.
The RLEC bit indicates whether the drive should return CHECK
CONDITION status with sense key set to UNIT ATTENTION when one of
the READ and WRITE error counters of the log pages reach a specified
threshold. Thresholds can be modified using LOG SELECT.
Queue Algorithm
Modifier
Must be 0.
Qerr
Queue Error. Must be 0.
DQue
Disable Queuing. Must be 0.
EECA
Enable Extended Contingent Allegiance. Not supported; must be 0.
RAENP
Ready Asynchronous Event Notification. Not supported; must be 0.
UAAENP
Unit Attention Asynchronous Event Notification. Not supported; must
be 0.
EAENP
Enable AEN Permission. Asynchronous event notification is not
supported; must be 0.
Ready AEN Holdoff Period
Not supported; must be 0.
5-76
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
5.9.5
Data Compression Page (0Fh)
The Data Compression page specifies parameters for the control of data
compression. This page allows the user to turn the tape drive’s compressed
format on and off independently of the tape medium’s position. Additionally, it
allows the user to enable or disable decompression of the tape drive compressed
data during WRITE operations.
Bit
Byte
7
0
6
5
4
3
Reserved
2
1
0
Page Code (0Fh)
1
Page Length (0Eh)
2
DCE
3
DDE
(1)
DCC
(1)
Reserved
RED
(00)
Reserved
(MSB)
4-7
Compression Algorithm (10)
(LSB)
(MSB)
8 - 11
Decompression Algorithm (10)
(LSB)
12 - 15
Reserved
Figure 5–37 Data Compression Page Format Descriptor - Data Format
Quantum DLT 4000 Tape Drive
5-77
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–40 Data Compression Page Descriptor - Field Descriptions
Field Name
Description
Page Code
The Page Code identifies the type of MODE SELECT page being transferred. A
value of 0Fh identifies this as the Data Compression page.
Page Length
The Page Length field indicates the number of bytes in the Data Compression
page that follow this byte. The valid value for this byte is 0Eh.
DCE
Data Compression Enable. This bit specifies whether the tape drive should
enable or disable data compression. When set to 1, the drive starts in
compressed format.
DCC
Data Compression Capable. This bit is used by the MODE SENSE command to
indicate that the tape drive supports data compression.
DDE
Data Decompression Enable. Must be set to 1. When the tape drive reads
compressed data from tape, it automatically decompresses the data before
sending it to the initiator. Data compression must always be enabled.
RED
Report Exception on Decompression. The tape drive does not report exceptions
on decompression (boundaries between compressed and uncompressed data).
The RED field must be 00h.
Compression
Algorithm
The Compression Algorithm field indicates which compression algorithm the
tape drive will use to process data from the initiator when the DCE bit (byte 02,
bit 7) is set to 1. The only value currently supported for this field is 10h.
NOTE: Specifying a value other than 10h for this field causes the tape drive to
return CHECK CONDITION status, sense key set to ILLEGAL REQUEST. However, if
EEPROM parameter EnaRepDecomp is set, the parameter in this field is ignored
and no CHECK CONDITION status is returned.
Decompression
Algorithm
The Decompression Algorithm field indicates which decompression algorithm
the tape drive will use when decompressing data on the tape. The only value
currently supported is 10h.
NOTE: Specifying a value other than 10h for this field causes the tape drive to
return CHECK CONDITION status, sense key set to ILLEGAL REQUEST.
5-78
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
5.9.6
Device Configuration Page (10h)
The Device Configuration Page controls the drive’s behavior on the SCSI bus
and allows an initiator to tune bus performance.
Bit
Byte
0
7
6
PS (0)
0
5
4
2
1
0
Page Code (10h)
1
2
3
Additional Page Length (0Eh)
Res’d
CAP (0)
CAF (0)
Active Format (0)
3
Active Partition (0)
4
Write Buffer Full Ratio
5
Read Buffer Empty Ratio
(MSB)
6-7
Write Delay Time
(LSB)
8
DBR (0)
BIS
9
RSmk (0)
AVC (0)
SOCF (0)
RBO (0)
REW (0)
Gap Size (0)
10
EOD Defined (0)
EEG
SEW (1)
Reserved
(MSB)
11 - 13
Buffer Size at Early Warning (0)
(LSB)
14
15
Select Data Compression Algorithm
Reserved
Figure 5–38 Device Configuration Page - Data Format
Quantum DLT 4000 Tape Drive
5-79
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–41 Device Configuration Page - Field Descriptions
Field Name
Description
PS
Parameters Savable. For MODE SELECT, this bit must be 0.
Additional Page Length
This field indicates the number bytes in the page. However, the value
does not include bytes 0 and 1. The length is returned in MODE SENSE
commands and must subsequently be set to the same value when
performing MODE SELECT. If the page length does not match that
expected by the drive, a CHECK CONDITION status is returned, sense key
set to ILLEGAL REQUEST.
The drive returns a CHECK CONDITION status with sense key set to
ILLEGAL REQUEST if it receives an unsupported Page Code or a Page field
with values not supported or changeable. In such cases, no parameters
are changed as a result of the command.
CAP
Change Active Partition. Not supported; must be 0.
CAF
Change Active Format. Not supported; must be 0.
Active Format
Not supported. Must be 0.
Active Partition
Only partition 0 is supported. Setting this field to any other value causes
rejection by the drive with a CHECK CONDITION status, sense key ILLEGAL
REQUEST set.
Write Buffer Full Ratio
The drive sets this field to 0. The drive uses an automatic adaptive
mechanism to adjust its Full Ratio according to the average data rates
over the SCSI bus.
Read Buffer Empty
Ratio
The drive sets this field to 0. The drive uses an automatic adaptive
mechanism to adjust its Empty Ratio according to the average data rates
over the SCSI bus.
Write Delay Time
This field indicates the maximum time that the drive will wait with a
partially full buffer before forcing the data to tape (100 ms increments).
The buffer Full/Empty ratio, which is dynamic, can cause data to be
written sooner than the Write Delay Time would indicate. The Write Delay
Time defaults to 200 (C8h). This causes the buffer to be flushed in 20
seconds. Maximum value is 6500 (1964h) and the minimum is 15 (0Fh).
This represents a range from 11 minutes down to 1.5 seconds.
5-80
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–41 Device Configuration Page - Field Descriptions (continued)
Field Name
Description
Write Delay Time
(cont.)
Values between 0 and 15 on a MODE SELECT are rounded down to 0.
This causes the data to go straight to the medium without delay.
DBR
Data Buffer Recovery. Not supported, must be 0.
BIS
Block Identifiers Supported. This field is supported. Set to 1.
RSmk
Report Setmark. Not supported, must be 0.
AVC
Automatic Velocity Control. Not supported; must be 0.
SOCF
Stop on Consecutive Filemarks. Not supported; must be 0.
RBO
Recover Buffer Order. Not supported; must be 0.
REW
Report Early Warning. Not supported; must be 0 (do not report Early
Warning EOM on READ).
Gap Size
Not used; must be 0.
EOD Defined
End-of-Data Defined. This field must be set to 00h.
EEG
Enable End-of-Data Generation. Set to 1. This field indicates that the drive
will generate an EOD. The drive generates an EOD mark before any
change of direction following a WRITE-type operation. This bit is ignored,
however, on MODE SELECT.
SEW
Synchronize at Early Warning. Must be set to 1.
Buffer Size at Early
Warning
Not supported; must be 0.
SEW
Synchronize at Early Warning. Must be set to 1.
Select Data
Compression
Algorithm
When set to 1, enables data compression.
0, disables data compression.
When
The setting on the front panel of the tape drive overrides any setting of
MODE SELECT, but no error will result. If the setting is returned to the
automatic mode on the front panel of the tape drive, the value from the
last MODE SELECT command determines whether compression is
enabled or disabled.
Quantum DLT 4000 Tape Drive
5-81
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
5.9.7
Medium Partition Page (11h)
The drive supports the Medium Partitions Parameters Page that is used to
specify the medium partitions.
Bit
Byte
0
7
6
PS (0)
0
5
4
3
Additional Page Length (06)
2
Maximum Additional Partitions (0)
3
Additional Partitions Defined (0)
FDP (0)
SDP (0)
1
Page Code (11h)
1
4
2
IDP (0)
PSUM (0)
5
Medium Format Recognition (01)
6-7
Reserved
Reserved
Figure 5–39 Medium Partition Page Format Descriptor - Data Format
5-82
Quantum DLT 4000 Tape Drive
0
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–42 Medium Partition Page Descriptor - Field Descriptions
Field Name
Description
PS
Parameters Savable. For MODE SELECT, this bit must be 0.
Additional Page Length
This field indicates the number bytes in the page. However, the value
does not include bytes 0 and 1. The length is returned in MODE
SENSE commands and must subsequently be set to the same value
when performing MODE SELECT. If the page length does not match
that expected by the drive, a CHECK CONDITION status is returned,
sense key set to ILLEGAL REQUEST.
The drive returns a CHECK CONDITION status with sense key set to
ILLEGAL REQUEST if it receives an unsupported Page Code or a Page
field with values not supported or changeable. In such cases, no
parameters are changed as a result of the command.
Maximum Additional
Partitions
Not supported. Must be 0.
Additional Partitions
Defined
Must be 0. This field specifies the number of additional partitions to
be defined for the tape based on the settings of the SDP and IDP bits.
The maximum allowed is the value returned in the Maximum
Additional Partitions field. Only one partition is supported, therefore
the value of the field must be 0.
FDP
Fixed Data Partitions. Must be 0.
SDP
Select Data Partitions. Must be 0.
IDP
Initiator Defined Partitions. Must be 0.
PSUM
Partition Size Unit of Measure. Must be 0.
Medium Format
Recognition
This field is valid for MODE SENSE only, and is set to 01h, indicating
that Medium Format Recognition is supported.
Quantum DLT 4000 Tape Drive
5-83
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
5.9.8
EEPROM Vendor Unique Page (3Eh)
The drive supports a vendor unique page that enables a user to modify savable
parameters. Only one savable parameter may be changed per Mode Select
command.
Bit
Byte
0
7
6
PS
Rsvd
5
4
3
2
1
0
Page Code (3Eh)
1
Additional Page Length
2
ASCII String of Parameter Name and Value
Figure 5–40 EEPROM Vendor Unique Page - Data Format
The ASCII string has a parameter name, followed by one or more space
characters, a parameter value, and an ASCII line feed or null character. When
the string is parsed, the parameter value is interpreted as shown in the following
table. Note that the parameter name may be in upper or lower case. The savable
parameters are saved over resets and power cycles.
Table 5–43 EEPROM Vendor Unique Page Parameters
Name
Value
Rep.
Default
Length
(Bytes)
VENDORID
ASCII
QUANTUM
8
Vendor Identification field in INQUIRY
Data
PRODUCTID
ASCII
DLT4000
16
Product Identification field in INQUIRY
Data
5-84
Usage
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–43 EEPROM Vendor Unique Page Parameters (continued)
Name
CACHETMS
Value
Rep.
Default
Length
(Bytes)
ASCII
Decimal
0
1
Usage
0,1 = Do not cache filemarks unless
IMMED bit is set, if set
2 = Cache if not two in a row unless
IMMED bit is 1.
3 = Always cache filemarks.
DEFAULTCOMPON
ASCII
Binary
1
1
0 = Compression defaulted OFF at
power-up/reset
1 = Compression defaulted ON at powerup/reset
DEFIXEDBLKEN
ASCII
Decimal
0
8
Default fixed block size
DEFSEW
ASCII
Binary
1
1
To set default SEW parameter.
DISLDRAUTODMC
ASCII
Binary
1
1
To partially disable sequential loading
with loader if any media loader
command has been received.
DISUNBUFMODE
ASCII
Binary
0
1
The drive disables unbuffered mode, i.e.,
it ignores the MODE SELECT “buffered
mode” selection to turn off buffered
mode, if set.
ENACLNGLTRPT
ASCII
Binary
1
1
To report error status if cleaning indicator
is on.
ENAINITSYNCNEG
ASCII
Binary
0
1
To enable target-initiated synchronous
negotiation, if set.
ENALDRAUTOLD
ASCII
Binary
1
1
To turn on/off sequential loading with
loader
ENAMODEPG22
ASCII
Binary
0
1
To enable vendor unique Data
Compression (Status Mode Page)
Quantum DLT 4000 Tape Drive
5-85
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–43 EEPROM Vendor Unique Page Parameters (continued)
Name
Value
Rep.
Default
Length
(Bytes)
ENAPARERRRETRY
ASCII
Binary
0
1
To turn on/off parity error retry feature
ENAREPDECOMP
ASCII
Binary
0
1
If set and the drive is in READ mode, the
decompression algorithm field in Data
Compression mode will be reset if the last
block requested by the host was
decompressed, otherwise it is cleared.
ENATHIRDPTYDENS
ASCII
Binary
1
1
To make non-DLT density code act as the
default density (same as density code 0),
if set.
ENBINQMEDCHGR
ASCII
Binary
0
1
0 = Disable media changer bit.
ASCII
Binary
0
ASCII
Decimal
0
FORCECOMP
FORCEDENSITY1
Usage
1 = Enable media changer bit in byte 6 of
INQUIRY data (set if drive is in a media
changer device)
1
0 = automatic2
1 = Always compress unless front panel
selection disables it
1
0 = automatic2
1 = DLT260
2 = DLT600
3 = DLT2000
4 = DLT4000
1
Applied to DLTtape III format tape for DLT260 tape drive, DLT600 tape drive and DLT2000xt
tape drive. Applied to DLTtape IV format tape for DLT 4000 tape drive.
2
Parameter is not forced to a special format. Instead it is determined by the parameters selected
via MODE SELECT.
5-86
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–43 EEPROM Vendor Unique Page Parameters (continued)
Name
Value
Rep.
Default
Length
(Bytes)
FORCEEEREBUILD
ASCII
Binary
0
1
To force all the EEPROM parameters to
reset to default, if set.
FORCEREADSILI
ASCII
Binary
0
1
To make variable READ command
handled as if the SILI bit is set if set.
LDRCYCLRESET
ASCII
Binary
0
1
To cause the first cartridge to be loaded if
unloading the last cartridge when the
loader product is operated in sequential
mode, if set.
ASCII
Decimal
1
1
1 - 7 = LUN to report media loader
device on.
LONGXPORTPAGE
ASCII
Binary
1
1
To report 18 or 6 bytes medium transport
element status descriptor if parameter is
on or off.
NODEFERRCVDERR
ASCII
Binary
0
1
The drive reports deferred recovered error
as current recovered error, if set.
NODISCONFXDBLK
ASCII
Binary
1
1
To turn on/off feature that prevents
disconnecting on every fixed block data
transfer
NORDYUAONUNLD
ASCII
Binary
0
1
When set, Not Ready to Ready unit
attention will be removed from the unit
attention queue upon a successful
unload.
PROTECTDIRONWP
ASCII
Binary
0
1
To protect tape directory if the cartridge
write-protect switch is in its write protect
position.
LOADERLUN
Usage
Quantum DLT 4000 Tape Drive
5-87
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
Table 5–43 EEPROM Vendor Unique Page Parameters (continued)
Name
Value
Rep.
Default
Length
(Bytes)
Usage
REPBUSYINPROG
ASCII
Binary
0
1
When set, report busy status if the drive is
in the process of becoming ready.
REPORTRCVDPERRS
ASCII
Binary
1
1
To report recovered error if parity error
has been retried successfully, if set.
REPORTRCVRDERR
ASCII
Binary
0
1
This parameter sets the default value of
PER bit of READ / WRITE Error Recovery
Mode page (01h).
REWINDONRESET
ASCII
Binary
1
1
0 = Do not rewind on BUS RESET or BDR
message (CAUTION: May have partial
block data written to tape if reset occurs
during WRITE).
1 = Rewind the tape medium to BOT on
reset.
SCSIBUSDMATIMER
ASCII
Decimal
2
1
The number of seconds until the drive
times out waiting for ACK once DMA
transfer started. When set to 0, the timer
is set to infinite.
SCSIINQVS
ASCII
Binary
0
1
To return vendor unique inquiry string, if
set.
SCSIRDYEARLY
ASCII
Binary
0
1
The drive reports READY status earlier, if
set.
ASCII
Decimal
10
1
The number of reselection retries the
drive makes before giving up. Each
reselection retry occurs every 1 second.
When set to 0, the drive does infinite
reselection retries.
ASCII
Binary
0
1
SCSI Reserve / Release Unit commands are
no operation, if set.
SCSIRESELRETRIES
SCSIRESRELNOP
5-88
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
As an example of an EEPROM vendor unique page, the following figure shows a
page that will modify the VENDORID parameter to “XXXYY.”
0
1
0
0
Page Code (3Eh)
Page Length (0Fh)
2
“v”
(76h)
3
“e”
(65h)
4
“n”
(6Eh)
5
“d”
(64h)
6
“o”
(6Fh)
7
“r”
(72h)
8
“i”
(69h)
9
“d”
(64h)
10
“”
(20h)
11
“X”
(58h)
12
“X”
(58h)
13
“X”
(58h)
14
“Y”
(59h)
15
“Y”
(59h)
16
<LF>
(A0h) or (00h)
Figure 5–41 EEPROM Vendor Unique Page “Vendor ID” Example - Data Format
Quantum DLT 4000 Tape Drive
5-89
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
The following example illustrates an EEPROM vendor unique page that modifies
the FORCEDENSITY parameter to 1.
0
1
0
0
Page Code (3Eh)
Page Length (0Fh)
2
“F”
(46h)
3
“O”
(4Fh)
4
“R”
(52h)
5
“C”
(43h)
6
“E”
(45h)
7
“D”
(44h)
8
“E”
(45h)
9
“N”
(4Eh)
10
“S”
(53h)
11
“I”
(49h)
12
“T”
(54h)
13
“Y”
(59h)
14
“”
(20h)
15
“1”
(31h- ASCII)
16
<LF>
(A0h) or (00h)
Figure 5–42 EEPROM Vendor Unique Page “Forced Density” Example - Data Format
5-90
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SELECT (6) / (10) Command (15h) / (55h) (continued)
5.9.9
Changeable Parameters within MODE SELECT
The following table lists the MODE SELECT command’s changeable parameters
and their default, minimum, and maximum values. Descriptions of the various
parameters are provided in the discussions of the different mode pages within
MODE SELECT. Note that parameter rounding is supported for all parameters
except for the block descriptor length.
Table 5–44 Changeable Mode Parameters within MODE SELECT
Page: Parameter
Default
Minimum
Maximum
Header: Buffered Mode, Device Specific Byte
1
0
1
Block Descriptor Length
08h
00h
08h
2.0 GB and 6.0 GB Mode
0
0
40000h
10.0 GB and 20.0 GB Mode
0
0
FFFFFFh
READ / WRITE Error Recovery (01h): PER bit
0
0
1
Control Mode (0Ah): RLEC
0
0
1
Data Compression (0Fh): DCE
1
0
1
Disconnect / Reconnect (02h): Maximum Burst Size
0080h
0000h
FFFFh
Disconnect / Reconnect (02h): DTDC
0
0
3
Device Configuration (10h): WRITE Delay Time
C8h
Fh
1964h
Device Configuration (10h): SEW
1
0
1
Device Configuration (10h): Select Data Compression
Algorithm
1
0
1
Block Descriptor: Block Length
Quantum DLT 4000 Tape Drive
5-91
SCSI Commands
5.10
MODE SENSE (6) / (10) COMMAND (1AH / 5AH)
The MODE SENSE command allows the drive to report its media type, and
current, or changeable configuration parameters to the host. It is a
complementary command to MODE SELECT.
The command descriptor block for the 6-byte MODE SENSE (1Ah) is shown as
follows. An illustration of the command descriptor block for the 10-byte MODE
SENSE (5Ah) follows on the next page.
Bit
Byte
7
6
5
0
1
2
4
3
2
0
Operation Code (1Ah)
Logical Unit Number
Rsvd
PC
DBD
Reserved
4
Allocation Length
Unused
Reserved
Page Code
3
5
1
Reserved
Flag
Link
Figure 5–43 MODE SENSE (6) Command Descriptor Block - Data Format
The 10-byte MODE SENSE command is required to request the Vendor-Unique
EEPROM parameter page due to the large amount of data that parameter page
contains. MODE SENSE (10) can be used to retrieve the other pages as well.
Note that MODE SENSE (10) returns descriptor data in a different format than
MODE SENSE (6).
5-92
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
Bit
Byte
7
6
0
5
4
3
2
1
0
Operation Code (5Ah)
1
Logical Unit Number
2
Rsvd
PC
DBD
Reserved
Page Code
3
Reserved
4
Reserved
5
Reserved
6
Reserved
(MSB)
7-8
Allocation Length
(LSB)
5
Unused
Reserved
Flag
Link
Figure 5–44 MODE SENSE (10) Command Descriptor Block - Data Format
Quantum DLT 4000 Tape Drive
5-93
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
Table 5–45 MODE SENSE Command Descriptor Block - Field Descriptions
Field Name
Description
DBD
Disable Block Descriptors. If 0, device returns the block descriptor data. If set
to 1, block descriptor information is not returned.
PD
Page Control. The Page Control field indicates the type of page parameter
values to be returned to the host.
PC Description
00 Report Current Values
01 Report Changeable Values
10 Report Default Values
11 Report Saved Values
Page Code
This field allows the host to select any specific page or all of the pages
supported by the drive.
Allocation Length
This field specifies the number of bytes that the host has allocated for
returned MODE SENSE data. An allocation length of zero indicates that the
drive will return no MODE SENSE data. This is not considered an error, and
GOOD status is returned.
MODE SENSE may be either MODE SENSE (6) or MODE SENSE (10). MODE
SENSE (6) data contains a 4-byte header followed by one 8-byte block descriptor,
followed by zero or more variable length pages, depending on the Page Code and
Allocation Length.
5-94
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
5.10.1 MODE SENSE Data Headers
The MODE SENSE (6) and MODE SENSE (10) headers are illustrated in the
following figures.
Bit
Byte
7
6
5
4
3
0
Mode Sense Data Length
1
Media Type
2
WP
2
Buffered Mode
3
1
0
1
0
Speed (0)
Block Descriptor Length (08h)
Figure 5–45 MODE SENSE (6) Data Header - Data Format
Bit
Byte
7
6
5
4
3
2
(MSB)
0-1
Mode Sense Data Length
(LSB)
2
3
Media Type
WP
4-5
Buffered Mode
Speed (0)
Reserved
(MSB)
6-7
Block Descriptor Length (08h)
(LSB)
Figure 5–46 MODE SENSE (10) Data Header - Data Format
Quantum DLT 4000 Tape Drive
5-95
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
Table 5–46 MODE SENSE Data Header - Field Descriptions
Field Name
Description
Mode Sense Data
Length
This field specifies the length (in bytes) of the MODE SENSE data that is
available to be transferred during the DATA IN phase. Note that the
Mode Sense Data Length does not include itself.
Media Type
The media type is determined by the drive and can be one of the
following:
Media Type - Description
00h - Unknown or not present
81h - Cleaning tape
82h - DLTtape I or DLTtape II
83h - DLTtape III
84h - DLTtape IIIxt
85h - DLTtape IV
WP
Write Protect. If 0, this field indicates that the tape is write-enabled. If set
to 1, it indicates that the tape is write-protected.
Buffered Mode
This mode implements Immediate Reporting on WRITE commands via
the Buffered Mode.
If the field is 0, then the drive does not report a GOOD status on WRITE
commands until the data blocks are actually written to tape.
If the field is 1, then the drive reports GOOD status on WRITE commands
as soon as the data block has been transferred to the buffer. This is the
default configuration of the drive. Note that if Buffered Mode is not
used, the tape drive will suffer a degradation in performance, but not in
capacity.
Speed
The tape drive supports only one speed. This is the default speed (0).
Block Descriptor Length
This field specifies the length (in bytes) of all of the block descriptors.
Since the drive only supports one block descriptor, this value is 08h.
5-96
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
5.10.2 MODE SENSE Block Descriptors
The following figure describes the MODE SENSE block descriptor that follows
the MODE SENSE header. Descriptions of the MODE SENSE blocks are
provided in Table 5-47.
Bit
Byte
7
0
6
5
4
3
2
1
0
Density Code
(MSB)
1-3
Number of Blocks (000000h)
(LSB)
4
Reserved
(MSB)
5-7
Block Length
(LSB)
Figure 5–47 MODE SENSE Block Descriptor - Data Format
Quantum DLT 4000 Tape Drive
5-97
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
Table 5–47 MODE SENSE Block Descriptor - Field Descriptions
Field Name
Description
Density Code
The contents of this field match the density of the media, or 0 if the density is
unknown:
Density Code
00h
0Ah
16h
17h
18h
19h
1Ah
Description
Use default density.
6667 bpi MFM serial cartridge tape X3B5/86-199 (read only).
10000 bpi MFM serial cartridge tape X3.193-1990 (read only).
42500 bpi MFM serial cartridge tape X3B5/91- 2.6 GB (DLTtape III
only).
Same as 17h, but with 56 track pairs vs. 24 - 6.0 GB (DLTtape III
only).
62500 bpi, 64 track pairs, serial cartridge tape - 10.0 GB (DLTtape
III only) /15.0 GB (DLTtape IIIxt only)
81633 bpi, 64 track pairs, serial cartridge tape - 20.0 GB (DLTtape
IV only)
The density codes above are the preferred codes used to define density.
Additionally, the following codes may be used, though use of the Data
Compression Page is preferred (these codes are only returned if they were set using
the MODE SELECT command):
80h
Number of
Blocks
Block Length
5-98
62500 bpi, 64 track pairs, serial cartridge tape - 10.0 GB (DLTtape III)
/15.0 GB (DLTtape IIIxt) without compression
81h
62500 bpi, 64 track pairs, serial cartridge tape - 20.0 GB (DLTtape III)
/30.0 GB (DLTtape IIIxt) with compression
82h
81633 bpi, 64 track pairs, serial cartridge tape - 20.0 GB (DLTtape IV)
without compression
83h
81633 bpi, 64 track pairs, serial cartridge tape - 40 GB (DLTtape IV) with
compression
This field is sent as 0, indicating that all of the remaining logical blocks on the tape
have the medium characteristics specified by the block descriptor.
This field specifies the length (in bytes) of each logical block transferred over the
SCSI bus. A block length of 0 indicates that the length is variable (as specified in the
I/O command). Any other value indicates the number of bytes per block that are
used for READ, WRITE, and VERIFY type commands that specify a fixed bit of 1
(fixed block mode).
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
5.10.3 MODE SENSE Mode Pages
The following illustration depicts the variable length page descriptor.
Bit
Byte
0
1
2
7
6
PS
0
5
4
3
2
1
0
Page Code
Additional Page Length
Page Defined or Vendor-Unique Parameter Bytes
Figure 5–48 MODE SENSE Page Descriptor - Data Format
Descriptions of the MODE SENSE page descriptor fields are provided in the
following table. Detailed descriptions of each of the MODE SENSE Pages follow.
Quantum DLT 4000 Tape Drive
5-99
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
Table 5–48 MODE SENSE Page Descriptor - Field Descriptions
Field Name
Description
PS
Parameters Savable. When 0, the supported parameters cannot be saved
(savable pages are not supported). When set to 1, it indicates that the
page can be saved in nonvolatile memory by the drive.
Additional
Page
Length
This field indicates the number of bytes in the page. Note that this value
does not include bytes 0 and 1. The length is returned on MODE SENSE
and must subsequently be set to the same value when performing MODE
SELECT.
Page codes and pages that are supported are:
5-100
Page Code
Description
SENSE / SELECT
Section
00h
No Requested Page
SENSE
---
01h
READ / WRITE Error Recovery Page
BOTH
5.10.3.1
02h
Disconnect / Reconnect Page
BOTH
5.10.3.2
0Ah
Control Mode Page
BOTH
5.10.3.3
0Fh
Data Compression Page
BOTH
5.10.3.4
10h
Device Configuration Page
BOTH
5.10.3.5
11h
Medium Partition Page
BOTH
5.10.3.6
3Eh
EEPROM Vendor Unique Page
BOTH
5.10.3.7
3Fh
All Pages (Except EEPROM)
SENSE
---
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
5.10.3.1 READ / WRITE Error Recovery Page (01h)
The tape drive supports the Error Recovery Page for READ and WRITE
operations. The format for the page is illustrated in the following figure.
Bit
Byte
0
7
6
PS (0)
0
5
3
2
1
0
DTE (0)
DCR (0)
Page Code (01h)
1
2
4
Additional Page Length (0Ah)
Rsvd
Rsvd
TB
Rsvd
EER
3
READ Retry Count
4-7
Reserved
8
WRITE Retry Count
9 - 11
Reserved
PER
Figure 5–49 Read / Write Error Recovery Page - Data Format
Quantum DLT 4000 Tape Drive
5-101
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
Table 5–49 Read / Write Error Recovery Page - Field Descriptions
Field Name
Description
PS
Parameters Savable. Must be 0, the supported parameters cannot be
saved (savable pages are not supported).
Additional Page
Length
This field indicates the number of bytes in the page. Note that this value
does not include bytes 0 and 1. The length is returned on MODE SENSE
and must subsequently be set to the same value when performing
MODE SELECT.
TB
Transfer Block. The Transfer Block (when not fully recovered) function is
not supported.
EER
Enable Early Recovery. This function is always enabled (must be = 1).
PER
Post Error. This bit enables reporting of CHECK CONDITION to report
recovered READ / WRITE errors. Default is 0.
DTE
Disable Transfer on Error. Set to 0. This feature is not supported.
DCR
Disable ECC Correction Bit. Set to 0. This feature is not supported.
READ Retry
Count
This field reports the maximum number of re-reads that are attempted
before declaring an unrecoverable error.
WRITE Retry
Count
This field reports the maximum number of overwrite retries that are
attempted before declaring an unrecoverable error.
5.10.3.2 DISCONNECT / RECONNECT Page (02h)
The tape drive supports the DISCONNECT / RECONNECT Page. The format for
the page is illustrated in the following figure.
5-102
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
Bit
Byte
0
7
6
PS
0
5
4
3
2
1
0
Page Code (02h)
1
Additional Page Length (0Eh)
2
Buffer Full Ratio (0)
3
Buffer Empty Ratio (0)
(MSB)
4-5
Bus Inactivity Limit (0)
(LSB)
(MSB)
6-7
Disconnect Time Limit (0)
(LSB)
(MSB)
8-9
Connect Time Limit (0)
(LSB)
(MSB)
10 - 11
Maximum Burst Size
(LSB)
12
13 - 15
Reserved
DTDC
Reserved
Figure 5–50 Disconnect / Reconnect Page - Data Format
Quantum DLT 4000 Tape Drive
5-103
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
Table 5–50 Disconnect / Reconnect Error Recovery Page - Field Descriptions
Field Name
Description
PS
Parameters Savable. When 0, the supported parameters cannot be saved
(savable pages are not supported). When set to 1, it indicates that the
page can be saved in nonvolatile memory by the drive.
Additional Page Length
This field indicates the number of bytes in the page. Note that this value
does not include bytes 0 and 1. The length is returned on MODE SENSE
and must subsequently be set to the same value when performing
MODE SELECT.
Buffer Full Ratio
Not supported.
Buffer Empty Ratio
Not supported.
Bus Inactivity Limit
Not supported.
Disconnect Time Limit
Not supported.
Connect Time Limit
Not supported.
Maximum Burst Size
The value in this field specifies the maximum amount of data to be
transferred without disconnecting. A value of 0 sets no limit. This value
is given in 512 byte increments. For example, a value of 8 indicates 4K
bytes. Values that are not multiples of 8 are rounded up to the nearest
multiple of 8.
DTDC
Data Transfer Disconnect Control. The value in this field specifies the
restriction when a disconnect is permitted.
5-104
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
5.10.3.3 Control Mode Page (0Ah)
The Control Mode page allows the user to determine whether the tape drive
returns a CHECK CONDITION status when one of the WRITE and READ
counters has reached a specified threshold.
Bit
Byte
7
0
6
5
4
Reserved
2
1
0
Page Code (0Ah)
1
Page Length (06)
2
Reserved
3
4
3
Queue Algorithm Modifier (0)
EECA (0)
5
RLEC
Reserved
Reserved
RAENP
(0)
Qerr (0)
DQue (0)
UAAENP
EAENP
(0)
Reserved
(MSB)
6-7
Ready AEN Holdoff Period (0)
(LSB)
Figure 5–51 Control Mode Page - Data Format
Quantum DLT 4000 Tape Drive
5-105
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
Table 5–51 Control Mode Page - Field Descriptions
Field Name
Description
Page Length
The value in this field indicates the number of bytes in the Control
Mode page being transferred. The value for this byte is 06h.
RLEC
Report Log Exception Condition. This bit indicates whether the tape
drive returns CHECK CONDITION status with sense key set to UNIT
ATTENTION (06h) when one of its WRITE and READ error counters
reaches a specified threshold, as follows:
0 = Do not return UNIT ATTENTION when a threshold has been met.
1 = Return UNIT ATTENTION when a threshold is met.
Queue Algorithm Modifier
Must be 0.
Qerr
Queue Error. Must be 0.
Dque
Disable Queuing. Must be 0.
EECA
Enable Extended Contingent Allegiance. Not supported; must be 0.
RAENP
Ready AEN Permission. Asynchronous event notification is not
supported; must be 0.
UAAENP
Unit Attention AEN Permission. Not supported; must be 0.
EAENP
Enable AEN Permission. Asynchronous event notification is not
supported; must be 0.
Ready AEN Holdoff Period
Not supported. Must be 0.
5-106
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
5.10.3.4 Data Compression Page (0Fh)
The Data Compression page specifies parameters for the control of data
compression.
Bit
Byte
0
7
6
PS (0)
Rsvd
5
4
3
2
1
0
Page Code (0Fh)
1
Page Length (0E)
2
DCE
3
DDE (0)
DCC
Reserved
RED (0)
Reserved
(MSB)
4-7
Compression Algorithm
(LSB)
(MSB)
8 - 11
Decompression Algorithm
(LSB)
12 - 15
Reserved
Figure 5–52 Data Compression Page - Data Format
Quantum DLT 4000 Tape Drive
5-107
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
Table 5–52 Data Compression Page - Field Descriptions
Field Name
Description
PS
Parameters Savable. Not supported; must be 0.
Page Length
The value in this field indicates the number of bytes in the Control Mode
page being transferred. The value for this byte is 0Eh.
DCE
Data Compression Enable. The value returned for this bit depends on the
current WRITE density of the tape drive:
0 = Write compression is Disabled
1 = Write compression is Enabled
DCC
Data Compression Capable. The value returned for this bit indicates
whether this tape drive supports data compression:
0 = Data Compression is not supported
1 = Data Compression is supported and will process any data sent to it by
the initiator according to the setting of the DCE bit (byte 02, bit 7).
DDE
Data Decompression Enable. The value returned for this bit indicates
whether data decompression is enabled or not.
0 = Data Decompression is Disabled
1 = Data Decompression is Enabled
Note that when the tape drive reads compressed data from tape, it
automatically decompresses the data before sending it to the initiator.
The value for this bit, therefore, is always 1.
RED
Report Exception on Decompression. The tape drive does not report
exceptions on decompression (boundaries between compressed and
decompressed data). The value returned for RED is 00h.
Compression
Algorithm
The value for this field is 10h. This indicates the Lempel-Ziv high
efficiency data compression algorithm.
Decompression
Algorithm
The value for this field is 10h. This indicates the Lempel-Ziv high
efficiency data decompression algorithm. If EEPROM parameter
EnaRepDCcomp is set, a value of 0 is reported if the last block read is not
decompressed.
5-108
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
5.10.3.5 Device Configuration Page (10h)
The tape drive supports the Device Configuration Page. The format for the page
is illustrated in the following figure.
Bit
Byte
7
6
0
PS (0)
0
5
4
2
1
0
Page Code (10h)
1
2
3
Additional Page Length (0Eh)
Rsvd
CAP (0)
CAF (0)
Active Format (0)
3
Active Partition (0)
4
WRITE Buffer Full Ratio (0)
5
READ Buffer Empty Ratio (0)
(MSB)
6-7
WRITE Delay Time
(LSB)
8
DBR (0)
BIS (0)
9
RSmk
AVC (0)
SOCF (0)
RBO (0)
REW (0)
Gap Size (0)
10
EOD Defined (0)
EEG (1)
SEW (1)
Reserved
(MSB)
11 - 13
Buffer Size at Early Warning (0)
(LSB)
14
15
Select Data Compression Algorithm
Reserved
Figure 5–53 Device Configuration Page - Data Format
Quantum DLT 4000 Tape Drive
5-109
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
Table 5–53 Device Configuration Page - Field Descriptions
Field Name
Description
PS
Parameters Savable. Not supported; must be 0.
Additional Page Length
This field indicates the number of bytes in the page. Note that this
value does not include bytes 0 and 1. The length is returned on
MODE SENSE and must subsequently be set to the same value when
performing MODE SELECT.
CAP
Change Active Partition. Not supported.
CAF
Change Active Format. Not supported.
Active Format
Not supported.
Active Partition
This field indicates the current logical partition number in use. Only
partition 0 is supported.
WRITE Buffer Full Ratio
Indicates how full the buffer should be before restarting writing to
the medium. The tape drive sets this to 0 (unused) since it uses an
automatic adaptive mechanism to dynamically adjust its ratio
according to the average data rates over the SCSI bus.
READ Buffer Empty Ratio
Indicates how empty the buffer should be before restarting reading
from the medium. The tape drive sets this to 0 (unused) since it uses
an automatic adaptive mechanism to dynamically adjust its ratio
according to the average data rates over the SCSI bus.
WRITE Delay Time
Indicates the maximum time (in 100 ms increments) the drive waits
with a partially fully buffer before forcing the data to tape. Note that
the buffer full/empty ratio, which is dynamic, can cause data to be
written sooner than the WRITE delay time value indicates. The WRITE
delay time defaults to 200 ms (C8h). This causes the buffer to be
flushed in 20 seconds. Minimum value is 15 (Fh); maximum value is
6500 (1964h). This represents a range in delay from 1.5 seconds to
11 minutes.
DBR
Data Buffer Recovery. Not supported, must be 0.
BIS
Block Identifiers Supported. Set to 1.
RSmk
Report Setmarks. Not supported, must be 0.
AVC
Automatic Velocity Control. Set to 0.
5-110
Quantum DLT 4000 Tape Drive
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
Table 5–53 Device Configuration Page - Field Descriptions (continued)
Field Name
Description
SOCF
Stop on Consecutive Filemarks. Set to 0.
RBO
Recover Buffer Order. Set to 0.
REW
Report Early Warning. Set to 0 (do not report early warning EOM on
reads).
Gap Size
Not supported. Set to 0.
EOD Defined
End of Data. Set to 00h.
EEG
Enable EOD Generation Bit. Set to 1 to indicate that the drive
generates an EOD. The drive generates an EOD mark before any
change of direction following a WRITE-type operation.
SEW
Synchronize at Early Warning. Set to 1.
Buffer Size at Early
Warning
Not supported; must be 0.
Select Data Compression
Algorithm
If set to 1, data compression is enabled. If 0, data compression is
disabled.
Quantum DLT 4000 Tape Drive
5-111
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
5.10.3.6 Medium Partition Page (11h)
The tape drive supports the Medium Partition Page. The format for the page is
illustrated in the following figure.
Bit
Byte
0
7
6
PS (0)
0
5
4
3
Additional Page Length (06h)
2
Maximum Additional Partitions (0)
3
Additional Partitions Defined (0)
FDP (0)
SDP (0)
IDP (0)
PSUM (0)
5
Medium Format Recognition (01h)
6-7
Reserved
Figure 5–54 Medium Partition Page - Data Format
5-112
1
Page Code (11h)
1
4
2
Quantum DLT 4000 Tape Drive
Reserved
0
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
Table 5–54 Medium Partition Page - Field Descriptions
Field Name
Description
PS
Parameters Savable. Not supported; must be 0.
Additional Page Length
This field indicates the number of bytes in the page. Note that this
value does not include bytes 0 and 1. The length is returned on
MODE SENSE and must subsequently be set to the same value when
performing MODE SELECT.
Maximum Additional
Partitions
Not supported. Must be 0.
Additional Partitions
Defined
This field specifies the number of additional partitions to be defined
for the tape based on the settings of the SDP and IDP bits. The
maximum allowed is the value returned in the Maximum Additional
Partitions field. Since only one partition is supported, this field must
be 0.
FDP
Fixed Data Partitions. Must be 0.
SDP
Select Data Partitions. Must be 0.
IDP
Initiator Defined Patrons. Must be 0.
PSUM
Partition Size Unit of Measure. Must be 0.
Medium Format
Recognition
Set to 01h, indicating that automatic format recognition is
supported.
Quantum DLT 4000 Tape Drive
5-113
SCSI Commands
MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued)
5.10.3.7 EEPROM Vendor Unique Page (3Eh)
The tape drive supports the EEPROM vendor unique page (3Eh). All the
EEPROM parameters that are set via the MODE SELECT EEPROM Vendor
Unique page are returned.
NOTE
Because of the length of the parameter list, use MODE SENSE (10)
instead of MODE SENSE (6) to retrieve EEPROM parameters.
Because of the length of the list of EEPROM parameters, a 10-byte MODE
SENSE command is required. If a 6-byte MODE SENSE command is used for
retrieval, the data is returned as follows:
Send a 10-byte MODE SENSE command to get the Parameter List.
The data returned by the 10-byte MODE SENSE command for the EEPROM page
is in the form of a MODE SENSE (10) data header followed by block and page
descriptors.
The data in the page descriptor is organized in the form of a parameter header
followed by the actual parameter’s value. The parameter is as follows:
Name T Current Default Minimum Maximum
Name refers to the parameter name, for example, PRODUCTID or
DEFAULTCOMPON.
T designates data type: “b” indicates binary, “A” indicates string type, and if
there is no designator, the data is in decimal.
Current, Default, Minimum, and Maximum specify the current, default, minimum,
and maximum values of the parameter.
5-114
Quantum DLT 4000 Tape Drive
SCSI Commands
5.11
PREVENT / ALLOW MEDIUM REMOVAL COMMAND (1EH)
This command enables or disables the unloading of the tape cartridge.
Bit
Byte
7
6
0
1
4
3
2
1
0
Operation Code (1Eh)
Logical Unit Number
2-3
Reserved
Reserved
4
5
5
Reserved
Unused
Reserved
Prevent
Flag
Link
Figure 5–55 PREVENT / ALLOW MEDIUM REMOVAL Command Descriptor Block Data Format
Quantum DLT 4000 Tape Drive
5-115
SCSI Commands
PREVENT / ALLOW MEDIUM REMOVAL Command (1Eh)
(continued)
Table 5–55 PREVENT / ALLOW MEDIUM REMOVAL Command Descriptor Block Field Descriptions
Field Name
Description
Prevent
When set to 1, the UNLOAD button on the drive’s front panel is
effectively disabled, and the UNLOAD command does not unload the
tape medium or the cartridge. The PREVENT / ALLOW status in the
device is maintained separately by each initiator.
When set to 0, the prevent state corresponding to that initiator is
cleared. When all initiators have cleared their prevent states, the
UNLOAD button and UNLOAD commands are enabled. By default,
after power up, a hard reset, or Bus Device Reset message, the
prevent medium removal function is cleared.
If a Media Loader device is present, its MOVE MEDIUM command is
prevented from removing a cartridge if PREVENT has been enabled.
5-116
Quantum DLT 4000 Tape Drive
SCSI Commands
5.12
READ COMMAND (08H)
This command transfers one or more data blocks or bytes to the initiator
starting with the next block on the tape.
Bit
Byte
7
6
0
5
4
3
2
1
0
SILI
Fixed
Operation Code (08h)
1
Logical Unit Number
Reserved
(MSB)
2-4
Transfer Length
(LSB)
5
Unused
Reserved
Flag
Link
Figure 5–56 READ Command Descriptor Block - Data Format
Quantum DLT 4000 Tape Drive
5-117
SCSI Commands
READ Command (08h) (continued)
Table 5–56 READ Command Descriptor Block - Field Descriptions
Field Name
Description
SILI
Suppress Incorrect Length Indicator. If the SILI bit is set to 1 and the Fixed bit is set to
1, the target terminates the command with CHECK CONDITION status, sense key set to
ILLEGAL REQUEST, and additional sense code of INVALID FIELD IN CDB.
If the SILI bit is 0 and the actual block length is different than the specified transfer
length, a CHECK CONDITION status is returned. Within the sense data, the Incorrect
Length Indicator (ILI) bit and Valid bit will be set to 1. The sense key field specifies NO
SENSE. The information bytes are set to the difference (residue) between the requested
transfer length and the actual block length, or, in Fixed Block mode, the difference
(residue) between the requested number of blocks and the actual number of blocks
read. No more than transfer length blocks are transferred to the initiator and the tape
is logically positioned after the block (EOM side).
Fixed
This bit specifies whether fixed-length or variable-length blocks are to be transferred,
and gives meaning to the Transfer Length field of the READ command.
When set to 0, variable-block mode is requested. A single block is transferred with the
Transfer Length specifying the maximum number of bytes the initiator has allocated
for the returned data.
When the Fixed bit is set to 1, the Transfer Length specifies the number of blocks to be
transferred to the initiator. This is valid only if the logical unit is currently operating in
Fixed Block mode.
When the Transfer Length is 0, no data is transferred and the current position on the
logical unit does not change. This is not an error condition.
A successful READ with Fixed bit set to 1 transfers (current block length) x (# of
blocks x block size) bytes of data to the host. Upon termination of READ, the medium
is logically positioned after the last block of data transferred (EOM).
5-118
Quantum DLT 4000 Tape Drive
SCSI Commands
READ Command (08h) (continued)
Filemark, End-of-Data, and End-of-Medium/Partition Handling
If the tape drive reads a Filemark, it returns a CHECK CONDITION status.
Within the sense data, the Filemark and Valid bits are set and the Sense Key
field is set to NO SENSE. The information fields contain the residue count. The
Additional Sense Code and Additional Sense Code Qualifier fields are set to
FILEMARK DETECTED. Upon termination, the medium is logically positioned
after the Filemark (EOM).
If the drive detects End-of-Data (EOD) during a READ, the drive returns a
CHECK CONDITION status. Within the sense data, the Valid bit is set and the
Sense Key field is set to BLANK CHECK. The End-of-Medium (EOM) bit may be
set if the drive determines that the tape is positioned past the PSEN marker. The
information fields contain the residue count. The Additional Sense Code
Qualifier fields are set. Upon termination, the medium is physically positioned
before EOD and after the last block on tape.
The meaning of EOD is different for a READ command than for a WRITE-related
command. EOM is reported only when the physical EOM or End-of-Partition
(EOP) is encountered. The drive returns a CHECK CONDITION status. The
EOM and Valid bits are set and the Sense Key is set to MEDIUM ERROR. The
information fields contain the residue count and the Additional Sense Code and
Additional Sense Code Qualifier fields are set to EOM/P DETECTED. The tape
is physically positioned at EOM/P.
If any READ command cannot be successfully completed, the drive returns a
CHECK CONDITION status. Further commands should attempt to move past
the anomaly and to complete successfully.
Quantum DLT 4000 Tape Drive
5-119
SCSI Commands
5.13
READ BLOCK LIMITS COMMAND (05H)
The READ BLOCK LIMITS command directs the tape drive to report it’s block
length limits.
Bit
Byte
7
6
0
5
4
3
2
1
0
Flag
Link
Operation Code (05h)
1
Logical Unit Number
2-4
5
Reserved
Reserved
Unused
Reserved
Figure 5–57 READ BLOCK LIMITS Command Descriptor Block - Data Format
5-120
Quantum DLT 4000 Tape Drive
SCSI Commands
READ BLOCK LIMITS Command (05h) (continued)
The READ BLOCK LIMITS data shown as follows is sent during the DATA IN
phase of the command. The command does not reflect the currently selected
block size, only the available limits. MODE SENSE is the command that returns
the current block size.
Bit
Byte
7
6
5
0
4
3
2
1
0
Reserved
(MSB)
1-3
Maximum Block Length
(LSB)
(MSB)
4-5
Minimum Block Length (0001h)
(LSB)
Figure 5–58 READ BLOCK LIMITS Data - Data Format
Table 5–57 READ BLOCK LIMITS Data - Field Descriptions
Field Name
Description
Maximum Block Length
The value in this field indicates the maximum block size. The tape
drive supports a maximum block length of 16,777,215 (16 MB-1) for
10 GB or 20 GB format. A maximum block length of 256 K bytes is
supported for 2.6 GB or 6.0 GB formats.
Minimum Block Length
The value in this field indicates the minimum block size. The tape
drive supports a minimum block length of 1 byte.
Quantum DLT 4000 Tape Drive
5-121
SCSI Commands
5.14
READ BUFFER COMMAND (3CH)
The READ BUFFER command is used in conjunction with WRITE BUFFER as a
diagnostic function for testing the drive’s data buffer for possible diagnostic data
and for checking the integrity of the SCSI bus.
Bit
Byte
7
6
0
5
4
3
2
1
0
Operation Code (3Ch)
1
Logical Unit Number
2
Reserved
Mode
Buffer ID
(MSB)
3-5
Buffer Offset
(LSB)
(MSB)
6-8
Allocation Length
(LSB)
9
Unused
Reserved
Flag
Figure 5–59 READ BUFFER Command Descriptor Block - Data Format
5-122
Quantum DLT 4000 Tape Drive
Link
SCSI Commands
READ BUFFER Command (3Ch) (continued)
Table 5–58 READ BUFFER Command Descriptor Block - Field Descriptions
Field Name
Description
Mode
The tape drive supports the following values within this field. If any non-supported
value is set, the drive terminates the command with a CHECK CONDITION status,
ILLEGAL REQUEST sense key set.
Mode
Description
000b
Combined Header and Data (subsection 5.14.1)
010b
Data (subsection 5.14.2)
011b
Descriptor (subsection 5.14.3)
Buffer ID
Must be 0, 1 or 2. If any other value appears in this field, the tape drive returns a
CHECK CONDITION status with ILLEGAL REQUEST sense key set.
Buffer Offset
Not supported; must be 0. If any other value appears in this field, the tape drive
returns a CHECK CONDITION status with ILLEGAL REQUEST sense key set.
Allocation
Length
This field specifies the maximum number of bytes that the initiator has allocated
for returning data.
5.14.1 Combined Header and Data Mode
In this mode, the tape drive returns a 4-byte header followed by data bytes. The
drive terminates the DATA IN phase when the Allocation Length bytes of
header and data have been transferred or when all available data has been
transferred to the initiator, whichever is less. The 4-byte READ BUFFER header
is followed by data bytes from the target data buffer. The following figure
illustrates the format of the header.
Bit
Byte
7
0
6
5
4
3
2
1
0
Reserved
(MSB)
1-3
Available Length
(LSB)
Figure 5–60 READ BUFFER Header - Data Format
Quantum DLT 4000 Tape Drive
5-123
SCSI Commands
READ BUFFER Command (3Ch) (continued)
Table 5–59 READ BUFFER Header - Field Descriptions
Field Name
Description
Available Length
This field specifies the total number of data bytes available in the target’s
buffer. This number is not reduced to reflect the allocation length, nor is it
reduced to reflect the actual number bytes written using the WRITE BUFFER
command. Following the READ BUFFER header, the target transfers data from
its data buffer.
5.14.2 Data Mode
In this mode, the DATA IN phase contains only buffer data.
5.14.3 Descriptor Mode
In this mode, a maximum of four bytes of READ BUFFER descriptor information
is returned. The tape drive returns the descriptor information for the buffer
specified by the Buffer ID. In this mode, the drive does not reject the valid Buffer
IDs with a CHECK CONDITION status, but returns all zeros in the READ
BUFFER descriptor.
The Offset Boundary in the following figure is 12 (0Ch), indicating that buffer
offsets should be integral multiples of 4K.
Bit
Byte
7
0
6
5
4
3
2
1
0
Offset Boundaries (0Ch)
(MSB)
1-4
Buffer Capacity
(LSB)
Figure 5–61 READ BUFFER Descriptor - Data Format
5-124
Quantum DLT 4000 Tape Drive
SCSI Commands
5.15
READ POSITION COMMAND (34H)
The READ POSITION command is used to read a position identifier or SCSI
Logical Block Address (LBA). The LOCATE command uses this identifier to
position back to this same logical position in a high-performance fashion.
Bit
Byte
7
6
5
0
4
3
2
1
0
Operation Code (34h)
1
Logical Unit Number
2-8
Reserved
BT
Reserved
9
Unused
Reserved
Flag
Link
Figure 5–62 READ POSITION Command Descriptor Block - Data Format
Table 5–60 READ POSITION Command Descriptor Block - Field Descriptions
Field Name
Description
BT
Block Type. This bit indicates how the position is to be interpreted. Since the tape
drive uses the same logical block regardless of the setting of this bit, the setting is
ignored. The logical block address values include all recorded objects: blocks and
filemarks.
NOTE
The drive returns CHECK CONDITION with UNIT NOT READY sense
key with the READ POSITION command if the media is not ready to
be accessed.
Quantum DLT 4000 Tape Drive
5-125
SCSI Commands
READ POSITION Command (34h) (continued)
Data from READ POSITION takes the following format:
Bit
Byte
0
7
6
BOP
EOP
5
4
3
Reserved
1
Partition Number
2-3
Reserved
2
BPU (0)
1
0
Reserved
(MSB)
4-7
First Block Location
(LSB)
(MSB)
8 - 11
Last Block Location
(LSB)
12
Reserved
(MSB)
13 - 15
Number of Blocks in Buffer
(LSB)
(MSB)
15 - 19
Number of Bytes in Buffer
(LSB)
Figure 5–63 READ POSITION - Data Format
5-126
Quantum DLT 4000 Tape Drive
SCSI Commands
READ POSITION Command (34h) (continued)
Table 5–61 READ POSITION Data - Field Descriptions
Field Name
Description
BOP
Beginning of Partition. When set to 1, indicates that the logical unit is
at the beginning of partition in the current partition. When 0,
indicates that the current logical position is not at the beginning of
partition.
EOP
End of Partition. When set to 1, indicates that the logical unit is
positioned between early warning and the end of partition in the
current partition. When 0, it indicates that the current logical position
is not between early warning and end of partition.
BPU
Block Partition Unknown. This bit is never set: the setting of the Block
Type (BT) bit of READ POSITION CDB does not affect the block address
values returned.
First Block Location
The block address associated with the current logical position: the
next block to be transferred between the target and initiator if a READ
or WRITE command is issued.
Last Block Location
The block address associated with the current physical position: the
next block to be transferred to tape medium and form the target’s
buffer. If the buffer is empty, or has only a partial block, the same
value as First Block Location is reported. The first block or filemark
written onto the tape medium is at address 0.
Number of Bytes in Buffer
The number of data blocks in the target’s buffer.
Number of Bytes in Buffer
The number of data bytes in the buffer that have not been written to
the tape medium.
Quantum DLT 4000 Tape Drive
5-127
SCSI Commands
5.16
RECEIVE DIAGNOSTIC RESULTS COMMAND (1CH)
The RECEIVE DIAGNOSTIC RESULTS command fetches the results of the last
SEND DIAGNOSTIC command sent to the tape drive.
Bit
Byte
7
6
5
0
4
3
2
1
0
Operation Code (1Ch)
1
Logical Unit Number
Reserved
2
Reserved
(MSB)
3-4
Allocation Length
(LSB)
5
Unused
Reserved
Flag
Link
Figure 5–64 RECEIVE DIAGNOSTIC RESULTS Command Descriptor Block - Data
Format
Table 5–62 RECEIVE DIAGNOSTIC RESULTS Command Data - Field Descriptions
5-128
Field Name
Description
Allocation Length
Specifies the number of bytes of diagnostic page results
the drive is allowed to send to the initiator.
Quantum DLT 4000 Tape Drive
SCSI Commands
RECEIVE DIAGNOSTIC RESULTS Command (1Ch) (continued)
The following data is returned by the drive as a result of the RECEIVE
DIAGNOSTIC command. Note that a REQUEST SENSE command should be
used to obtain more detailed information following a CHECK CONDITION on a
SEND DIAGNOSTIC command.
Bit
Byte
7
6
5
4
3
0
Controller Present Flag
1
Controller Error Flag
2
Drive Present Flag
3
Drive Error Flag
4
Media Loader Present Flag
5
Media Loader Error Flag
2
1
0
Flag set = 1 = failure. Flag not set = 0 = not present or no error
Figure 5–65 RECEIVE DIAGNOSTIC RESULTS - Data Format
This information indicates which of the main components of the tape drive
subsystem may have failed diagnostic testing.
Quantum DLT 4000 Tape Drive
5-129
SCSI Commands
5.17
RELEASE UNIT COMMAND (17H)
The RELEASE UNIT command releases the drive if it is currently reserved by the
requesting initiator. It is not an error to release the tape drive if it is not
currently reserved by the requesting initiator. If the tape drive is reserved by
another initiator, however, it is not released; the tape drive is only released from
the initiator that issued the RELEASE command.
Bit
Byte
7
6
0
1
5
4
3
1
Logical Unit Number
3rd Pty
Reserved
3
Reserved
4
Reserved
Unused
Third Party Device ID
Reserved
Rsvd
Flag
Figure 5–66 RELEASE UNIT Command Descriptor Block - Data Format
5-130
0
Operation Code (17h)
2
5
2
Quantum DLT 4000 Tape Drive
Link
SCSI Commands
RELEASE UNIT Command (17h) (continued)
Table 5–63 RELEASE UNIT Command Data - Field Descriptions
Field Name
Description
3rdPty
The third party release option for RELEASE UNIT allows an initiator to
release a logical unit that was previously reserved using the third-party
reservation option. If this bit is 0, then the third-party release option is not
requested. If this bit is set to 1, the drive is released if it was originally
reserved by the same initiator using the third-party reservation option and
if the tape drive is the same SCSI device specified in the Third Party Device
ID field.
Third Party Device ID
Required if the 3rdPty bit is 1. This field specifies the SCSI ID of the initiator
whose third party reservation is being released. This field must be set if the
initiator of the original third party RESERVE is the source of the RELEASE.
Media Changer Considerations
The optional Element reservation feature defined for Medium Changer devices in
the SCSI-2 ANSI specification is not supported. The RELEASE command is
defined the same as for the tape drive. The whole loader unit can be released.
RESERVE / RELEASE of the Loader and Drive LUNs are handled
independently.
Quantum DLT 4000 Tape Drive
5-131
SCSI Commands
5.18
REPORT LUNS COMMAND (A0h)
The REPORT LUNS command requests that the peripheral device logical unit
numbers of known logical units in the target be sent to the applications client.
The command only returns information about the logical units to which
commands may be sent.
Bit
7
6
5
4
3
2
1
0
Byte
0
Operation Code (A0h)
1-5
Reserved
(MSB)
6–9
Allocation Length
(LSB)
10
11
Reserved
Unused
Reserved
Flag
Link
Figure 5–67 REPORT LUNS Command Descriptor Block — Data Format
Table 5-64 REPORT LUNS Command Descriptor Block—Field Description
Field
Allocation Length
Description
If the Allocation Length is not sufficient to contain the logical unit number
values for all configured logical units, the device server still reports as many
logical number values as will fit in the Allocation Length.
The format of the report of configured logical units is shown in Figure 5-68.
5-132
Quantum DLT 4000 Tape Drive
SCSI Commands
REPORT LUNS Command (0Ah) (continued)
Bit
7
6
5
4
3
2
1
0
Byte
(MSB)
0-3
LUN List Length (n – 7)
(LSB)
4-7
Reserved
(MSB)
8 - 15
LUN (first LUN)
(LSB)
•
•
•
•
•
•
n-7 – n
LUN (last LUN, if more than one)
Figure 5–68 LUN Reporting Parameter List — Data Format
The LUN List Length field contains the length in bytes of the LUN list that can
be transferred. The LUN list length equals the number of logical unit numbers
reported multiplied by eight. If the allocation length in the CDB is too small to
allow transfer of information about all of the logical units configured, the LUN
list length value is not adjusted to reflect the truncation.
Quantum DLT 4000 Tape Drive
5-133
SCSI Commands
5.19
REQUEST SENSE COMMAND (03H)
The REQUEST SENSE command causes the tape drive to transfer detailed sense
data to the initiator.
Bit
Byte
7
6
5
0
4
3
2
1
0
Flag
Link
Operation Code (03h)
1
Logical Unit Number
Reserved
2
Reserved
3
Reserved
4
Allocation Length
5
Unused
Reserved
Figure 5–69 REQUEST SENSE Command Descriptor Block - Data Format
Table 5–65 REQUEST SENSE Command Data - Field Descriptions
Field Name
Description
Allocation Length
This field specifies the maximum number of sense bytes to be
returned. The tape drive terminates the transfer when this number of
bytes has been transferred or when all available sense data has been
transferred to the host, whichever is less.
5-134
Quantum DLT 4000 Tape Drive
SCSI Commands
REQUEST SENSE Command (03h) (continued)
The REQUEST SENSE command causes the tape drive to transfer detailed sense
data to the initiator.
The sense data is valid for a CHECK CONDITION or RESERVATION
CONFLICT status returned on the previous command. The sense data bytes are
preserved by the tape drive until retrieved by a REQUEST SENSE command, or
until the receipt of any other command from the same initiator, though some
commands, such as INQUIRY, do not change sense data.
If the tape drive receives an unsolicited REQUEST SENSE, it returns sense data
with the appropriate values in the End of Media (EOM), Sense Key, Additional
Sense Code, and Additional Sense Code Qualifier. The positional information
provided reflects the logical position of the tape drive. The tape drive returns
information based on the non-diagnostic data in its buffer as well as the data on
tape medium. Additionally, bytes 25 through 28 contain the amount of tape to
be written in 4 KB blocks.
REQUEST SENSE does not cause the drive to flush its buffered data to tape.
Therefore, if the host requires the exact physical positioning of the tape medium,
it should precede the REQUEST SENSE command with a WRITE FILEMARKS
command with length 0 (Immed=0) specified. This forces the tape drive to flush
any currently-buffered data to tape. A subsequent REQUEST SENSE command
returns the actual physical (and logical) position of the tape drive to the
initiator.
The following figure shows the format of REQUEST SENSE DATA.
Quantum DLT 4000 Tape Drive
5-135
SCSI Commands
REQUEST SENSE Command (03h) (continued)
Bit
Byte
7
0
Valid
6
5
3
2
1
0
Error Code
1
2
4
Segment Number (0)
Filemark
EOM
ILI
Reserved
Sense Key
(MSB)
3-6
Information Bytes
(LSB)
7
Additional Sense Length
(MSB)
8 - 11
Command-Specific Information Bytes
(LSB)
12
Additional Sense Code (ASC)
13
Additional Sense Code Qualifier (ASCQ)
14
Sub-Assembly Code (0)
15
SKSV
C/D
Reserved
BPV
Bit Counter
(MSB)
16 - 17
Field Pointer
18
Internal Status Code (VU)
19 - 20
Tape Motion Hours
21 - 24
Power On Hours
(LSB)
25 - 28
Tape Remaining
Figure 5–70 REQUEST SENSE - Data Format
5-136
Quantum DLT 4000 Tape Drive
SCSI Commands
REQUEST SENSE Command (03h) (continued)
Table 5–66 REQUEST SENSE Data - Field Descriptions
Field Name
Description
Valid
When set to 1, this field indicates that the information bytes contain valid
information as defined in the ANSI SCSI-2 specification.
Error Code
A value of 70h indicates a current error – the report is associated with the most
recently received command.
A value of 71h indicates a deferred error – the report is associated with a
previous command and not as a result of the current command.
No other values are returned in this field.
Segment
Number
This value of this byte is always 0.
Filemark
This bit indicates that the current command has read a Filemark.
EOM
End of Medium. This bit indicates that an End of Medium condition (End of
Partition or Beginning of Partition) exists. The warning is also given by setting
the Sense Key to NO SENSE and the Additional Sense Qualifier to End of Partition
or Beginning of Partition.
ILI
Incorrect Length Indicator. This bit indicates that the requested logical block
length did not match the logical block length of the data on the tape medium.
Only READ or VERIFY may cause this bit to be set.
Sense Key
In most cases, Additional Sense Code and/or Qualifier information is available.
The codes and qualifiers are covered in detail in Table 5-67.
Information
Bytes
These bytes contain the differences (residue) of the requested length minus the
actual length in bytes, blocks, or Filemarks, as determined by the command.
Negative values are indicated by two’s complement notation. The bytes are valid
for all READ, WRITE, SPACE, and VERIFY tape commands for which a CHECK
CONDITION status has been generated. The information bytes are 0 for MODE
SELECT / SENSE, INQUIRY, READ BLOCK LIMITS, and TEST UNIT READY.
Additional Sense
Length
This field specifies the number of additional sense bytes to follow. If the
Allocation Length of the Command Descriptor Block is too small to transfer all
of the Additional Sense bytes, the Additional Sense Length is not adjusted to
reflect the truncation.
Quantum DLT 4000 Tape Drive
5-137
SCSI Commands
REQUEST SENSE Command (03h) (continued)
Table 5–66 REQUEST SENSE Data - Field Descriptions (continued)
Field Name
Description
Command
Specific
Information
Bytes
Command Specific Information Bytes are handled as device-specific and can be
logged by the operating system on error conditions. On tape medium errors,
such an entry usually contains the current SCSI Logical Block Address.
Additional Sense
Code
This field (and the field for Additional Sense Code Qualifier) provide additional
information about the Sense Key and cause of a CHECK CONDITION status.
Additional Sense Codes are discussed in detail later in this chapter.
Additional Sense
Code Qualifier
This field (and the field for Additional Sense Code) provides additional
information about the Sense Key and cause of a CHECK CONDITION status.
Additional Sense Code Qualifiers are discussed in detail later in this chapter.
Sub-Assembly
Code
Not used. Returned as 0.
SKSV
Sense-Key Specific Valid. When = 1, indicates that the Sense Key specific field is
as defined by the International Standard.
C/D
Command / Data. When set to 1, this field indicates that the illegal parameter is
contained in the Command Descriptor Block. A C/D set to 0 indicates that the
illegal parameter is in the Parameter List from the initiator.
BPV
Bit Pointer Valid. When set to 1, this field indicates that the Bit Pointer field is
valid and designates which bit of the byte designated by the field pointer is in
error. For a multi-bit field, it points to the most significant bit of the field.
Field Pointer
This field indicates which byte of the Command Descriptor Block or Parameter
List is in error. For a multi-byte field, the most significant byte is indicated.
Internal Status
Code
Internal Status Codes are explained in detail in Appendix A.
Tape Motion
Hours
This field reports the number of tape motion (i.e., head wear) hours. Format is
given as a hexadecimal word (2 bytes).
Power On Hours
This field reports the total number of hours that drive power has been applied
since its last power on cycle (not total power on hours over the device’s
lifetime). Format is given as a hexadecimal longword (4 bytes).
Tape Remaining
This field reports the amount of tape remaining in 4KB (4096 bytes) blocks.
5-138
Quantum DLT 4000 Tape Drive
SCSI Commands
REQUEST SENSE Command (03h) (continued)
Table 5–67 Supported Sense Keys
Sense Key
Description
0h
NO SENSE. Check the Filemark/EOM/ILI bits and the Additional Sense Code/Additional
Sense Code Qualifier bytes.
1h
RECOVERED ERROR. This can be caused by rounding of Mode Parameters on a MODE
SELECT, or may report that READ/WRITE error rates are reaching subsystem specification
limits for optimal operation. The device may still be able to continue to function
without any unrecovered errors for a long period of time, however.
2h
NOT READY. The tape medium is not ready for tape operation commands. Tape
medium might not be present in the drive or may be in the process of loading or
calibrating.
3h
MEDIUM ERROR. An unrecoverable WRITE, READ, or positioning error has occurred.
Detailed device-specific information may be available.
4h
HARDWARE ERROR. The Additional Sense Code / Additional Sense Code Qualifier fields
may present more specific information.
5h
ILLEGAL REQUEST. The Command Descriptor Block or supplied parameter data had an
unsupported or illegal operation specified. Check bytes 15, 16, and 17.
6h
UNIT ATTENTION. Unit Attentions are created after a device reset, if the medium
asynchronously becomes ready to the initiator, if another initiator changes Mode
Parameters, and/or if the firmware is updated.
7h
DATA PROTECTED. The current tape medium is write-protected. This can be because
the Write Protect switch on the cartridge is in its enabled position or if the tape
medium is not the appropriate type (DLTtape III, DLTtape IIIxt, and DLTtape IV).
8h
BLANK CHECK. An End of Data or LongGap has been encountered.
Bh
COMMAND ABORTED. This key is generated when a command has been aborted by
the tape drive for some reason. Check the Additional Sense Code / Additional Sense
Code Qualifier bytes.
Dh
VOLUME OVERFLOW. This key indicates that the physical end of tape medium has
been reached during writing. The initiator ignored the End of Medium condition and
continued to write to tape.
Eh
MISCOMPARE. A compare error has occurred during READ by the self-tests invoked
during execution of a SEND DIAGNOSTIC command.
Quantum DLT 4000 Tape Drive
5-139
SCSI Commands
REQUEST SENSE Command (03h) (continued)
Table 5–68 Supported ASC / ASCQ in Hex
Sense Key
00
NO SENSE
5D
5D
ASCQ
00
01
02
03
04
05
00
FF
01
RECOVERED ERROR
00
0A
0A
37
3B
44
44
47
48
51
53
5B
80
80
17
00
80
00
08
C1
C2
00
00
00
01
02
02
03
Clean Requested (Non-Vendor Unique)
Error Log Overflow
Error Log Generated
Rounded Parameter
Repositioning Error
EEROM Copy 1 Area Bad
EEROM Copy 2 Area Bad
SCSI Parity Error
IDE Message Received
ERASE Failure
Unload Tape Failure
Log Counter at Maximum
Cleaning Requested
Soft Error Exceeds Threshold
02h
NOT READY
04
04
04
04
30
30
00
01
02
03
02
03
3A
3A
5A
00
80
01
Unit Not Ready, Cause Nonreportable
Unit Not Ready, Calibration in Process
Unit Not Ready, LOAD Command Needed
Unit Not Ready, Manual Intervention Needed
Incompatible Format
Unit Not Ready, Incompatible Media (Cleaning
Cartridge) Installed
Media Not Present
Media Not Present, VU Cartridge Missing
Operator Media Removal Request
00
04
0C
11
11
14
15
30
00
02
00
00
08
00
02
00
Medium Error
Unit Not Ready, LOAD Command Needed
WRITE Error
Unrecovered READ Error
Unrecovered READ Error, Incomplete Block Read
Recorded Entity Not Found
Position Error Detected by Read of Medium
Cannot Read Medium
03h
MEDIUM ERROR
ASC
00
Description
No Additional Sense Code
Unexpected FM Encountered
End of Medium (EOM) Encountered
SetMark Encountered
Beginning of Medium (BOM) Encountered
EOD Encountered
Tape Alert Failure Prediction Threshold Exceeded
False Exception Condition
* = Medium Changer specific command.
5-140
Quantum DLT 4000 Tape Drive
SCSI Commands
REQUEST SENSE Command (03h) (continued)
Table 5–68 Supported ASC / ASCQ in Hex (continued)
Sense Key
ASC
ASCQ
Description
MEDIUM ERROR
(cont.)
30
3B
3B
51
80
80
81
01
00
08
00
00
01
00
Unknown Format
Sequential Positioning Error
Repositioning Error
ERASE Failure
Calibration Error
Cleaning Required
Directory Read Error
04h
HARDWARE ERROR
08
08
0C
11
11
11
15
21
3B
3B
3B
40
40
40
40
40
44
44
44
44
44
44
44
44
44
44
44
47
48
51
53
53
00
01
80
80
81
82
01
01
08
0D
0E
80
81
82
83
84
00
83
84
85
86
87
88
8A
C1
C2
C3
00
00
00
00
01
LUN Communication Failure
LUN Communication Timeout Failure
Write SCSI FIFO CRC Error
Read SCSI FIFO CRC Error
Block Port Detected EDC Error
Block Port Detected Record CRC Error
Random Mechanical Positioning Error
Invalid Element Address
Repositioning Error
Media Destination Element Full*
Media Source Element Empty*
Diagnostic/POST Failure, ROM EDC Error
Diagnostic/POST Failure, RAM Failure
Diagnostic/POST Failure, Bad Drive Status
Diagnostic/POST Failure, Loader Diagnostics Failure
Diagnostic/POST Failure, POST Soft Failure
Internal Target Failure
SCSI Chip Gross Error
Unexplained Selection Interrupt
Immediate Data Transfer Timeout
Insufficient CDB Bytes
Disconnect/SDP Sequence Failed
Bus DMA Transfer Timeout
Over Temperature Condition
EEPROM Copy 1 Area Bad
EEPROM Copy 2 Area Bad
Both EEROM Copy Areas Bad
SCSI Parity Error
IDE Message Received
Erase Failure
Media Load/Eject Failure
Unload Tape Failure
* = Medium Changer specific command.
Quantum DLT 4000 Tape Drive
5-141
SCSI Commands
REQUEST SENSE Command (03h) (continued)
Table 5–68 Supported ASC / ASCQ in Hex (continued)
Sense Key
ASC
ASCQ
05h
ILLEGAL REQUEST
1A
20
20
21
24
24
24
24
24
24
24
24
24
24
24
24
25
26
26
26
30
39
3B
3B
3D
53
82
00
00
81
01
00
81
82
84
86
87
89
8B
8C
8D
8E
8F
00
00
01
02
00
00
0D
0E
00
02
00
Description
Parameter List Length Error
Illegal Opcode
Illegal Command While In Recovery Mode
Invalid Element Address (Media Changer)
Invalid CDB Field
Invalid Mode on WRITE Buffer
Media in Drive
Insufficient Resources
Invalid Offset
Invalid Size
Image Data Over Limit
Image/Personality is Bad
Not Immediate Command
Bad Drive/Server Image EDC
Invalid Personality for Code Update (CUP)
Bad Controller Image EDC
Illegal LUN
Parameter List Error, Invalid Field
Parameter List Error, Parameter Not Supported
Parameter List Error, Parameter Value Invalid
Incompatible medium (cannot read medium)
Saving Parameters Not Supported
Media Destination Element Full*
Media Source Element Empty*
Invalid Bits in ID Message
Media Removal Prevented
Not Allowed if not at BOT
06h
UNIT ATTENTION
28
29
2A
2A
3F
5B
00
00
01
02
01
01
Not Ready To Ready Transition
Reset Occurred
Mode Parameters Changed
Log Parameters Changed
Microcode has been Changed
Log Threshold Condition Met
07h
DATA PROTECTED
27
27
80
82
Hardware WRITE Protect
Data Safety WRITE Protect
08h
BLANK CHECK
00
08
05
00
01
EOD Encountered
LUN Communications Failure
LUN Communications Time-out
0Ah
0A
00
80
Error Log Overflow
Error Log Generated
* = Medium Changer specific command.
5-142
Quantum DLT 4000 Tape Drive
SCSI Commands
REQUEST SENSE Command (03h) (continued)
Table 5–68 Supported ASC / ASCQ in Hex (continued)
Sense Key
ASC
ASCQ
0Bh
COMMAND
ABORTED
2F
43
44
44
44
44
00
00
80
82
83
84
44
44
45
47
48
49
4B
4E
83
87
89
00
00
00
00
00
00
00
Description
Commands Cleared by Another Initiator
Message Error
Unexpected Selection Interrupt
Command Complete Sequence Failure
SCSI Chip, Gross Error/ Illegal – Command Status
Unexpected/Unexplained Residue Count in Transfer
Register
Disconnect Sequence Failed
Command Cleared from Queue Without Other
Select/Reselect Failure
SCSI Parity Error
IDE Message Error
Invalid Message Error
Data Phase Error
Overlapped Commands Attempted
Can not Retry Read/Write Data Transfer
0Dh VOLUME OVERFLOW (No Additional Sense Code or Sense Code Qualifier)
0Eh MISCOMPARE (No Additional Sense Code or Sense Code Qualifier)
* = Medium Changer specific command.
Filemark, End of Medium (EOM), and Incorrect Length Indicator (ILI) Bits
Filemark (byte 2, bit 7), EOM (byte 2, bit 6), and ILI (byte 2, bit 5) are names
of fields in the SCSI-2 REQUEST SENSE command. Any of these bits may be set
to a 1 even though the Additional Sense Code (ASC) / Additional Sense Code
Qualifier (ASCQ) bits have a value of 0.
For example:
?
?
?
Filemark, EOM, ILI bit may be set to 1 with No Sense key (00h) and ASC /
ASCQ = 00 00.
Filemark, EOM, ILI bit may be set to 1 with Recovered Error (01h) and ASC
/ ASCQ = 00 00.
Filemark, BOM, ILI bit may be set to 1 with Medium Error (03h) and ASC /
ASCQ = 00 00.
Quantum DLT 4000 Tape Drive
5-143
SCSI Commands
5.20
RESERVE UNIT COMMAND (16H)
The RESERVE UNIT command reserves the specified tape drive for exclusive use
by the requesting initiator or for another specified SCSI device.
Bit
Byte
7
6
0
5
4
3
2
1
0
Operation Code (16h)
1
Logical Unit Number
2-4
3rdPty
Third Party Device ID
Rsvd
Reserved
5
Unused
Reserved
Flag
Link
Figure 5–71 RESERVE UNIT Command Descriptor Block - Data Format
Table 5–69 RESERVE UNIT Command Data - Field Descriptions
Field Name
Description
3rdPty
The third party reservation option for RESERVE UNIT allows an initiator to
reserve a logical unit for another SCSI device. This option is intended for
systems that use COPY, and is implemented by the tape drive.
If set to 1, logical unit is reserved for the SCSI device whose ID appears in the
Third Party Device ID field. The tape drive ignores any attempt made by any
other initiator to release the reservation and returns a GOOD status.
If set to 0, no third party reservation is requested.
Third Party
Device ID
5-144
If 3rdPty is set to 1 (indicating that an initiator has reserved the logical unit for
another SCSI device), this field contains the ID number of that SCSI device for
which the reservation was made.
Quantum DLT 4000 Tape Drive
SCSI Commands
RESERVE UNIT Command (16h) (continued)
A reservation via the RESERVE UNIT command remains in effect until one of
the following conditions is met:
•
•
The initiator that made the reservation sends another RESERVE UNIT
command.
The tape drive is released via a RELEASE UNIT command from the same
initiator.
•
A BUS DEVICE RESET message is received from any initiator.
•
A hard reset occurs.
The occurrence of the last two conditions is indicated by the drive returning a
CHECK CONDITION status, sense key of UNIT ATTENTION on the next
command following the condition. It is not an error to issue a RESERVE UNIT
command to a drive that is currently reserved by the requesting initiator.
If another initiator has previously reserved the logical unit, the target returns a
RESERVATION CONFLICT status.
If, after honoring the reservation, any other initiator attempts to perform any
command except INQUIRY, REQUEST SENSE, or RELEASE UNIT, the
command is rejected with a RESERVATION CONFLICT status. That logical
unit ignores a RELEASE UNIT command issued by another initiator.
An initiator that holds a current reservation may modify that reservation (for
example, to switch third parties) by issuing another RESERVE UNIT command
to the tape drive.
Medium Changer Considerations for RESERVE UNIT Command
The optional Element Reservation feature defined for Medium Change devices as
described in the ANSI SCSI-2 specification is not supported. The RESERVE
command is defined the same as for the tape drive. The whole loader unit may be
reserved. This is separate from a reservation of the tape drive.
The RESERVE / RELEASE commands operate on a LUN basis. The Medium
Changer and the tape drive are generally handled as different devices. In the case
of a reserved drive LUN, a MOVE MEDIUM command issued to the Medium
Changer LUN cannot insert or remove a tape cartridge to or from a tape drive
unless the tape drive is reserved by the same initiator.
Quantum DLT 4000 Tape Drive
5-145
SCSI Commands
5.21
REWIND COMMAND (01H)
The REWIND command directs the tape drive to position the tape at the
beginning of the currently active partition (for DLTtape drives, this is BOM).
Before rewinding, the tape drive writes any write data that is in the buffer to the
tape medium and appends an End of Data marker.
Bit
Byte
7
6
0
5
4
3
2
1
0
Operation Code (01h)
1
Logical Unit Number
2-4
Reserved
Immed
Reserved
5
Unused
Reserved
Flag
Link
Figure 5–72 REWIND Command Descriptor Block - Data Format
Table 5–70 REWIND Command Data - Field Descriptions
Field Name
Description
Immed
Immediate. If this bit is set to 1, the tape drive first writes any remaining
buffered data to tape medium and adds an EOD marker. It then returns
status to the host before beginning the actual rewind operation. If this bit is
0, status will be sent after the rewind has completed.
5-146
Quantum DLT 4000 Tape Drive
SCSI Commands
5.22
SEND DIAGNOSTIC COMMAND (1DH)
The SEND DIAGNOSTIC command directs the tape drive to perform its selfdiagnostic tests.
Bit
Byte
7
6
0
5
4
3
2
1
0
Selftst
DevOfl
UnitOfl
Flag
Link
Operation Code (1Dh)
1
Logical Unit Number
2-4
PF (0)
Rsvd
Reserved
5
Unused
Reserved
Figure 5–73 SEND DIAGNOSTIC Command Descriptor Block - Data Format
Table 5–71 SEND DIAGNOSTIC Command Data - Field Descriptions
Field Name
Description
PF
Page Format. Not supported; must be 0.
Selftst
Self Test. This bit is used in conjunction with DevOfl and UnitOfl to specify the
type of testing to be done. An explanation is provided in the following
paragraphs.
DevOfl
Device Offline. This bit is used in conjunction with Selftst and UnitOfl to specify
the type of testing to be done. An explanation is provided in the following
paragraphs.
UnitOfl
Unit Offline. This bit is used in conjunction with Selftst and DevOfl to specify
the type of testing to be done. An explanation is provided in the following
paragraphs.
Quantum DLT 4000 Tape Drive
5-147
SCSI Commands
SEND DIAGNOSTIC Command (1Dh) (continued)
Two types of unit-resident diagnostic tests can be accessed:
Electronics Self-Test (Level 1 Test)
To invoke this level of diagnostic test, a major portion of the controller hardware
and software must be functioning properly. The test is based on the premise that
full power-up testing is not necessary, therefore, it is an extension of the powerup self tests that are run. The code ROM EDC is verified, two queues used by
much of the controller software are checked by dequeuing and enqueuing items.
If a loader (Medium Changer) is configured, the test attempts a software reset
on the loader. This test does not attempt a WRITE or READ to or from the tape
medium. When complete, any errors that occur are reported in the extended
Sense Data bytes. This Level 1 test has an execution time of approximately five
(5) seconds.
Specify the Electronics Self-Test by setting the Selftst bit to 1, and both the
DevOfl and UnitOfl bits to 0.
Read / Write Functionality Test (Level 2 Test)
The default version of this test does the following:
1.
Writes 500 32 KB records on track 0.
2.
Rewinds the tape.
3.
Reads the records.
4.
Positions to the beginning of track 1.
5.
Writes 500 32 KB records on track 1.
6.
Repositions to the beginning of track 1.
7.
Reads the records.
8.
Rewinds the tape.
The execution time for this Level 2 test is approximately 6 minutes, if
calibration is not required. The test is specified by setting both the Selftst bit
and the UnitOfl bit to 1 and ensuring that the DevOfl bit is 0. The test can
accept a parameter list specifying test variables (shown in the following table).
If a parameter is specified, all parameters must be filled in and the parameter list
length should be set to 12. If these requirements are not met, an ILLEGAL
REQUEST is returned. The Selftst bit in this case must be 0.
5-148
Quantum DLT 4000 Tape Drive
SCSI Commands
SEND DIAGNOSTIC Command (1Dh) (continued)
The following table illustrates the possible settings of the Selftst, DevOfl, and
UnitOfl bits and the effects of each setting on the resulting self-test:
Table 5–72 SEND DIAGNOSTIC CDB Bits Selftst, DevOfl, and UnitOfl
Bit
Byte
Selftst
DevOfl
UnitOfl
0
0
0
Illegal Combination
0
0
1
Self-Test Level 2 with User Parameters
0
1
0
Illegal Combination
0
1
1
Self-Test Level 2 with Default Parameters
1
0
0
Self-Test Level 1 with Default Parameters
1
0
1
Self-Test Level 2 with Default Parameters
1
1
0
Self-Test Level 1 with Default Parameters
1
1
1
Self-Test Level 2 with Default Parameters
7
6
5
Self - Test Effect
4
3
2
1
0
(MSB)
0-1
Pattern Number (Table 5-72)
(LSB)
(MSB)
2-3
Maximum Number of Test Passes
(LSB)
(MSB)
4-7
Block Size
(LSB)
(MSB)
8 - 11
Block Count
(LSB)
Figure 5–74 SEND DIAGNOSTIC Parameter List - Data Format
Quantum DLT 4000 Tape Drive
5-149
SCSI Commands
SEND DIAGNOSTIC Command (1Dh) (continued)
Table 5–73 SEND DIAGNOSTIC Parameter List - Field Descriptions
Field Name
Description
Pattern Number
Indicates the type of data pattern to be used during the diagnostic tests.
Pattern
Name
Data in Hex
0
Rotate
Rotate through the other 9 patterns;
change for each tape file.
1
All 0s
00 00 00 00 00
2
2F
FF FF FF FF FF
3
Alternating 1s and 0s
55 5A AA A5 55 5A AA A5
4
Marching 1
01 02 03 04 08 10 20 40 80
5
Marching 0
FE FD FB F7 EF DF BF 7F
6
MW
0E 0E 0E 0E 0E 0E 0E 0E
7
MFM
DE AD DE AD DE AD DE AD
8
IF
AA AA AA AA AA AA AA AA
9 (default) Random Data
This field specifies the number of test passes of the diagnostic to be run. If
Maximum Number of Test Passes = 0, the test will loop continuously. A
BUS RESET or a selection from the host sending an ABORT or BUS DEVICE
RESET message terminates testing. Default = 1.
Maximum Number
of Test Passes
Block Size
This field specifies the size of the blocks to be used. If this field is 0, random
block sizes are used. Default = 8400 bytes (DLTtape III media); 64 K
(DLTtape IV media).
Block Count
This field specifies how many blocks to WRITE / READ to and from starting
on track 0, then moving to track 1.
For example, if the Block Size and Block Count fields result in three (3)
tracks worth of data, the test will:
Write tracks 0, 1, 2
REWIND, READ, and VERIFY tracks 0, 1, 2
WRITE three tracks starting with 1: 1, 2, 3 and then REWIND to the
beginning of track 1 and perform the READ and VERIFY pass.
If Block Count is = 0, data is written until EOT is reached each time, so
almost four (4) complete passes over the tape would result. Default = 0.
5-150
Quantum DLT 4000 Tape Drive
SCSI Commands
SEND DIAGNOSTIC Command (1Dh) (continued)
NOTE
Because of data generation and verification, this test only streams
the tape for short periods of time. If Block Count is set very high,
the test can take many minutes or even many hours to complete.
If the specified diagnostic test passes, a GOOD status is returned. Otherwise, a
CHECK CONDITION is generated and the Sense Data contains information
about the failure.
Table 5–74 Sense Keys Used for SEND DIAGNOSTIC
Sense Key
Description
3h
Medium Error. A positioning error has occurred in which the returned position does
not match the expected position.
4h
Hardware Error. The Additional Sense Code (ASC) and any Additional Sense Code
Qualifier (ASCQ) provide more specific information.
5h
ILLEGAL REQUEST. Illegal bit settings in the SEND DIAGOSTIC command.
Eh
Miscompare. A compare error occurred during a READ operation.
Additional Sense Codes and Additional Sense Code Qualifiers that apply to
SEND DIAGNOSTIC self-test results are described in the following table.
Table 5–75 ASC / ASCQ for SEND DIAGNOSTIC
ASC
ASCQ
Description
15h
2h
A positioning error has occurred in which the returned position does
not match the expected position.
40h
80h
Level 1 ROM Test Failed.
40h
81h
Level 1 RAM Test Failed.
40h
82h
Level 1 Test Failed. Bad Drive Status.
40h
83h
Level 1 Test Failed. Loader Reset Failed.
Quantum DLT 4000 Tape Drive
5-151
SCSI Commands
5.23 SPACE COMMAND (11H)
The SPACE command provides a variety of positioning functions that are
determined by Code and Count fields in the Command Descriptor Block. Both
forward (toward End of Medium/End of Partition) and reverse (toward
Beginning of Medium/Beginning of Partition) positioning are provided.
Bit
Byte
7
6
5
0
4
3
2
1
0
Operation Code (11h)
1
Logical Unit Number
Reserved
Code
(MSB)
2-4
Count
(LSB)
5
Unused
Reserved
Flag
Link
Figure 5–75 SPACE Command Descriptor Block - Data Format
Table 5–76 SPACE Command Data - Field Descriptions
Field Name
Description
Code
The code can be one of the following:
Space Code
Space by:
000b
Blocks
001b
Filemarks
010b
Sequential Filemarks
011b
End of Data
For 2.6 GB and 6.0 GB format, the tape drive supports count values 0, 1, and 2
only. For 10.0 GB and newer formats, compressed or noncompressed, the count
value can be from 0 to 7FFFFFh.
5-152
Quantum DLT 4000 Tape Drive
SCSI Commands
SPACE Command (11h) (continued)
Table 5–76 SPACE Command Data - Field Descriptions (continued)
Field Name
Description
Count
When spacing over blocks or marks, the Count field is interpreted as follows:
A positive value N causes forward motion over N blocks or marks. The tape is
logically positioned after the Nth block or mark on the EOM or EOP side.
A value of 0 causes no change in logical position.
A negative value -N (two’s complement notation) causes reverse movement over
N blocks or marks. The tape is logically positioned on the BOM or BOP side of the
Nth block or mark.
When spacing to EOD, the Count field is ignored. Forward movement occurs until
the drive encounters EOD. The position is such that a subsequent WRITE command
would append data after the last object that has been written to tape before EOD.
When executing SPACE, the tape drive implements the following hierarchy:
Highest
BOM/P or EOM/P
EOD
Filemarks
Lowest
Blocks
A SPACE command in the form “SPACE N blocks” will halt with GOOD status
after the Nth block, or with CHECK CONDITION status on any occurrence of
Filemark, EOD, BOM/P, or EOM/P. A command “SPACE N Filemarks” will halt
on the Nth Filemark or on any occurrence of EOD, BOM/P, or EOM/P.
Depending on the size of blocks, read ahead data in the buffer allows some
spacing requests to be satisfied without actual tape movement.
NOTE
Note that when spacing by sequential filemarks, the DLT 4000 tape
drive handles up to 14 sequential filemarks and still reports back a
CHECK CONDITION. After the fourteenth sequential filemark (not
reached under normal operating conditions), if EOD is encountered,
the drive sends back a status good message. Status is only reported
properly on the DLT 4000 tape drive if the number of sequential
filemarks is less than or equal to 14.
Quantum DLT 4000 Tape Drive
5-153
SCSI Commands
5.23 TEST UNIT READY COMMAND (00H)
The TEST UNIT READY command checks the tape drive to ensure that the unit
is ready for commands involving tape movement. If the drive has a tape loaded,
the command returns a GOOD status. Otherwise, CHECK CONDITION is
reported.
Due to power cycle, code update, and tape loaded conditions, it is possible to get
multiple check conditions on a TEST UNIT READY command.
Bit
Byte
7
6
5
0
1
3
2
1
0
Flag
Link
Operation Code (00h)
Logical Unit Number
Reserved
2-4
5
4
Reserved
Unused
Reserved
Figure 5–76 TEST UNIT READY Command Descriptor Block - Data Format
Medium Changer Considerations
When directed at the Media Changer (Media Loader) LUN, this command
returns CHECK CONDITION, Sense Key, or NOT READY if the MODE
SELECT key is in the SERVICE mode and there is no 24 V signal (lack of 24 V
signal usually indicates the loader assembly has been moved out of its sleeve far
enough to trip the 24 V interlock). The media changer or loader is referenced as
“4500” or “4700”.
5-154
Quantum DLT 4000 Tape Drive
SCSI Commands
5.25 VERIFY COMMAND (13H)
The VERIFY command directs the tape drive to verify one or more blocks
beginning with the next block on the tape. Both CRC and EDCs are validated.
Bit
Byte
7
6
0
5
4
3
2
1
0
Immed
BC
Fixed
Operation Code (13h)
1
Logical Unit Number
Reserved
(MSB)
2-4
Verification Length
(LSB)
5
Unused
Reserved
Flag
Link
Figure 5–77 VERIFY Command Descriptor Block - Data Format
Quantum DLT 4000 Tape Drive
5-155
SCSI Commands
VERIFY Command (13h) (continued)
Table 5–77 VERIFY Command Data - Field Descriptions
Field Name
Description
Immed
Immediate. When set to 1, the VERIFY command completes before
any tape medium movement is done (that is, when the processing
has been initiated.
BC
Byte Check. When set to 0, the tape drive performs an internal
CRC/ECC check of data. No data is transferred to the initiator.
When set to 1, the command is rejected.
Fixed
This bit specifies whether fixed-length or variable-length blocks are to
be verified.
When set to 0, variable-block mode is requested. A single block is
transferred with the Verification Length specifying the maximum
number of bytes the initiator has allocated for verification.
When the Fixed bit is set to 1, the Verification Length specifies the
number of blocks to be verified. This is valid only if the logical unit is
currently operating in Fixed Block mode.
Verification Length
5-156
This field specifies the amount of data to verify, in blocks or bytes as
indicated by the Fixed bit.
Quantum DLT 4000 Tape Drive
SCSI Commands
5.26 WRITE COMMAND (0AH)
The WRITE command transfers one or more blocks from the host to the current
logical position. When in the Buffered Mode (the DLT tape drive default mode),
the tape drive reports GOOD status on WRITE commands as soon as this data
block has been transferred to the data buffer. Any check conditions will be
experienced as deferred errors. Refer to the MODE SELECT command
subsection for more information on Buffered Mode.
Bit
Byte
7
6
0
5
4
3
2
1
0
Operation Code (0Ah)
1
Logical Unit Number
Reserved
Fixed
(MSB)
2-4
Transfer Length
(LSB)
5
Unused
Reserved
Flag
Link
Figure 5–78 WRITE Command Descriptor Block - Data Format
Quantum DLT 4000 Tape Drive
5-157
SCSI Commands
WRITE Command (0Ah) (continued)
Table 5–78 WRITE Command Data - Field Descriptions
Field Name
Description
Fixed
The fixed bit specifies both the meaning of the Transfer Length field and
whether fixed-length or variable-length blocks are to be transferred.
When the Fixed bit is 0, Variable-length block mode is selected. A single block
is transferred from the initiator and is written to the logical unit beginning at
the current logical tape position. Upon successful termination, the tape is
logically positioned after this block (on the EOM/P side). The Transfer Length
specifies the number of bytes that the drive handshakes out from the initiator
as one block.
When the Fixed bit is 1, the Transfer Length field specifies the number of blocks
to be transferred to the host beginning at the current tape position. This form
of WRITE is valid only if the logical unit is currently operating in the Fixed Block
mode – when it has been instructed to use fixed-length blocks with MODE
SELECT. The current block length is the block length defined in the MODE
SELECT command. Upon termination, the tape is logically positioned after
these blocks.
Transfer Length
This field contains the length of the data transfer in bytes or blocks depending
on whether Fixed or Variable block mode is selected.
When the Transfer Length is 0, no data is transferred and the current position
on the logical unit is not changed.
Exception Conditions
If End of Tape (EOT) is detected while writing, the tape drive finishes writing
any buffered data. The command terminates with CHECK CONDITION status.
Within the sense data, the EOM bit is set, the Sense Key is set to NO SENSE,
and the Additional Sense code and Additional Sense Code Qualifier fields are set
to EOM/P detected. The drive attempts to complete any subsequent writes,
returning a CHECK CONDITION status in each case.
If the tape drive encounters the physical End of Medium (EOM) when
attempting WRITE, a CHECK CONDITION status is returned. Within the sense
data, the EOM and Valid bits are set, and the Sense Key field is set to Volume
Overflow. The Information fields contain the residue count and the Additional
Sense code and Additional Sense Code Qualifier fields are set to EOM/P
Detected. The tape is physically positioned at EOM/P.
5-158
Quantum DLT 4000 Tape Drive
SCSI Commands
5.27 WRITE BUFFER COMMAND (3BH)
The WRITE BUFFER command is used with READ BUFFER as a diagnostic
function for testing the device data buffer, DMA engine, SCSI bus interface
hardware, and SCSI bus integrity. It is also used for downloading and updating
DLT microcode (firmware).
Bit
Byte
7
6
0
5
4
3
2
1
0
Operation Code (3Bh)
1
Logical Unit Number
2
Reserved
Mode
Buffer ID (00h)
(MSB)
3-5
Buffer Offset (000000h)
(LSB)
(MSB)
6-8
Parameter List / Data Length
(LSB)
5
Unused
Reserved
Flag
Link
Figure 5–79 WRITE BUFFER Command Descriptor Block - Data Format
Quantum DLT 4000 Tape Drive
5-159
SCSI Commands
WRITE BUFFER Command (3Bh) (continued)
Table 5–79 WRITE BUFFER Command Data - Field Descriptions
Field Name
Description
Mode
The tape drive supports the following values within the field. If any other value is
set, the drive terminates the command with CHECK CONDITION status and an
ILLEGAL REQUEST sense key set.
Mode
Description
000b
010b
100b
101b
WRITE combined header and data (Section 5.27.1)
WRITE data (Section 5.27.2)
Download Microcode (Section 5.27.3)
Download Microcode and Save (Section 5.27.4)
Buffer ID
For all of the modes described for the Mode field, only a Buffer ID of 0 is supported.
If the Buffer ID field is a value other than 0, the command is rejected. The target
detects and rejects commands that would overrun the buffer.
Buffer Offset
See Sections 5.26.1 through 5.26.4 for the appropriate settings.
5.27.1 Write Combined Header and Data Mode (000b)
The data to be transferred is preceded by a 4-byte header consisting entirely of
reserved bytes. This header is discarded (not stored within the buffer). The buffer
offset field must be 0 for this mode.
5.27.2 Write Data Mode (010b)
Similar to Header and Data Mode, except there is no header in the data passed
to the target. Any potential buffer overruns are detected and the command is
rejected. The buffer offset field must be 0 for this mode.
CAUTION
During the actual reprogramming of the FLASH EEPROM, if any type
of powerfail occurs, or if the reprogramming fails before
completion, the tape drive subsystem becomes unusable and the
tape drive must be replaced.
5-160
Quantum DLT 4000 Tape Drive
SCSI Commands
WRITE BUFFER Command (3Bh) (continued)
5.27.3 Download Microcode Mode (100b)
Using buffer offsets, the host can download the firmware image into the target’s
buffer in pieces. These commands do not cause the new image to become active.
A Download and Save Mode WRITE BUFFER command must be issued for the
image to become active.
The tape drive must be empty of tape medium to allow downloading of an image.
This is a safeguard against accidentally starting a firmware update. If a tape
cartridge is loaded when all or part of a firmware image has been downloaded,
another WRITE BUFFER with Download Microcode mode will be rejected. The
firmware image must be downloaded in integral multiples of 4K bytes.
Any error on a WRITE BUFFER command causes any downloaded image data to
be discarded and the download must be restarted from the beginning.
CAUTION
During the actual reprogramming of the FLASH EEPROM, if any type
of powerfail occurs, or if the reprogramming fails before
completion, the tape drive subsystem becomes unusable and the
tape drive must be replaced.
5.27.4 Download Microcode and Save Mode (101b)
This mode is used to download and save the entire image at once, or to
download the image and save it, or to cause a save operation after the image
data has been downloaded using the Download Microcode mode (without the
Save). This mode of the WRITE BUFFER command causes the image data to be
verified and the Flash EEPROM firmware area to be updated. During the
reprogramming of the Flash EEPROM, the WRITE PROTECT and Drive Activity
LED’s on the drive’s front panel blinks. Also, when it is updating the EEPROM,
it disconnects from the SCSI bus and will not respond until the update is
complete.
When the Save operation is successfully completed, the firmware restarts itself,
causing the Power On Self Test (POST) to be run, and two UNIT ATTENTION
conditions are generated: POWER UP RESET and OPERATING CODE HAS
CHANGED.
Quantum DLT 4000 Tape Drive
5-161
SCSI Commands
5.28 WRITE FILEMARKS COMMAND (10H)
The WRITE FILEMARKS command directs the tape drive to write the specified
number of Filemarks beginning at the current logical position on tape. If the
Immediate bit is not set, any data or Filemarks in the WRITE cache buffer are
written to tape.
Bit
Byte
7
6
0
5
4
3
2
1
0
WSMk
(0)
Immed
Operation Code (10h)
1
Logical Unit Number
Reserved
(MSB)
2-4
Number of Filemarks
(LSB)
5
Unused
Reserved
Flag
Figure 5–80 WRITE FILEMARKS Command Descriptor Block - Data Format
5-162
Quantum DLT 4000 Tape Drive
Link
SCSI Commands
WRITE FILEMARKS Command (10h) (continued)
Table 5–80 WRITE FILEMARKS Command Data - Field Descriptions
Field Name
Description
WSmk
Write Setmark. Must be 0. This tape drive does not support Setmarks.
Immed
Immediate. When this bit is set to 1, the tape drive returns status as soon as
the Command Descriptor Block (CDB) has been validated, unless the
Filemark count is 0, or greater than 1 (since either condition causes the
WRITE buffer to be flushed to tape medium).
When set to 0, this bit indicates the status will not be returned until the
operation is complete.
Number of
Filemarks
This field contains the number of consecutive Filemarks to be written to
tape medium. A value of 0 is not considered to be an error; GOOD status is
returned.
The WRITE FILEMARKS command may be used to force the tape drive to write
any buffered WRITE data to the tape medium. If the tape drive is in buffered
mode, and WRITE FILEMARKS is received, the requested filemarks are
appended to the data and the WRITE buffer contents are flushed to tape
medium. A value of 0 in the Number of Filemarks field indicates that no
filemarks are to be written to the tape medium, but still flushes any WRITE data
to the tape medium.
If End of Tape (EOT) is detected while writing filemarks, the tape drive finishes
writing any buffered data and terminates with CHECK CONDITION status.
Within the Sense data, the End of Medium (EOM) bit is set, the Sense Key field
is set to NO SENSE and the Additional Sense Code and Additional Sense Code
Qualifier fields are set to EOM/P DETECTED. The tape drive attempts to
complete any subsequent WRITE FILEMARKS, returning a CHECK
CONDITION status in each case. If the tape drive encounters the physical EOM
when attempting a WRITE FILEMARKS, it returns CHECK CONDITION
status.
Quantum DLT 4000 Tape Drive
5-163
SCSI Commands
5-164
Quantum DLT 4000 Tape Drive
Appendix A
DEFINITION OF VENDOR UNIQUE SENSE DATA
INFORMATION
This appendix lists the internal status codes with their descriptions.
The internal status code is located at byte offset 18 of the REQUEST SENSE
data and may be available for certain types of failures.
NOTE
Byte 18 of the REQUEST SENSE data has two formats: a byte code
and a bit flags format. The bit flags format is used when there is no
internal status code to report and can be quickly distinguished by
checking to see if bit 7 of byte 18 is set to 1.
Table A–1 Internal Status Codes
Decimal
Hexadecimal
Description
0
0
No Meaning
1
1
Reed-Solomon Error Correction Code Recovery
2
2
READ or WRITE Block Retry (Soft Retry)
3
3
REPOSITION Command Aborted
4
4
Controller Has Stopped Reading
5
5
No Control or Data Buffers Available
6
6
Target Delivered in Read Ahead
7
7
Logical EOT Encountered, 2 Filemarks
8
8
Command Connection Dropped
Quantum DLT 4000 Tape Drive
A-1
Appendix A: Definition of Vendor Unique Sense Data Information
Table A–1 Internal Status Codes (continued)
A-2
Decimal
Hexadecimal
Description
9
9
10
0A
Missing Data Block – READ only
11
0B
Gap Within Object (Missing Block in Record)
12
0C
Record on Tape Larger Than Requested
13
0D
Compare Error
14
0E
Successive Blocks Missing Across Objects
15
0F
Drive State Not Valid for Command
16
10
Drive Error
17
11
Drive Communication Timeout Error
18
12
Drive Unloaded
19
13
Unable to WRITE – No CRC
20
14
Block to Append To Not Found
21
15
Data Synchronization Error (READ after WRITE Not
Happening)
22
16
Missing Block(s) in Current Entity
23
17
Drive Hardware WRITE Protected
24
18
Reposition-Target Not Found
25
19
Log Gap Encountered (Blank Tape or No Data Encountered)
26
1A
End of Data or Filler Block Encountered
27
1B
Filemark Encountered
28
1C
EDC Error Found by GPSP3 – FECC RAM Bad
29
1D
Beginning of Medium Encountered
30
1E
EDC Error
Cleared from Queue
Quantum DLT 4000 Tape Drive
Appendix A: Definition of Vendor Unique Sense Data Information
Table A–1 Internal Status Codes (continued)
Decimal
Hexadecimal
Description
31
1F
Hard WRITE Error – GPSP3 Underrun
32
20
Hard WRITE Error – READ Sync Timeout
33
21
Hard WRITE Error – Overshoot Append
34
22
Hard WRITE Error – CRC Error
35
23
EDC Error Found by GPSP3 – FECC RAM OK
36
24
Timeout on Command to Medium Changer
37
25
Medium Changer UART Error (Overrun)
38
26
Medium Changer Response Length Error
39
27
Medium Changer Detected Error
40
28
Invalid Source Slot
41
29
Invalid Destination Slot
42
2A
Source Slot Empty
43
2B
Destination Slot Full
44
2C
Medium Changer Motion Error
45
2D
Medium Changer/Drive Interface Error
46
2E
Medium Changer/Slot Interface Error
47
2F
Medium Changer Mechanical Error
48
30
Medium Changer Hardware Error
49
31
Medium Changer Controller Error
50
32
Unrecognized Medium Changer Subcommand
51
33
Medium Changer Fatal Error
52
34
Medium Changer is in Manual Mode
53
35
68020 Detected Communication Error with Servo Area
54
36
68020 Detected Drive Command Timeout
Quantum DLT 4000 Tape Drive
A-3
Appendix A: Definition of Vendor Unique Sense Data Information
Table A–1 Internal Status Codes (continued)
Decimal
Hexadecimal
55
37
Calibration Failure
56
38
Bad Tape Format
Bit 7
Bit 6
Bit 5
Description
Bit 4
Bit 3
Bit 2
Bit 1
Figure A-1 Internal Status Bits
Table A–2 Internal Status Bit Flags
Bit No.
0
1-2
Description
If set to 1, Cleaning Light is Illuminated, otherwise Light is off.
Tape Directory Status Bits:
Bit 2
3-6
7
A-4
Bit 1
0
0
Good Status
0
1
Unknown Status
1
0
Partial Directory (will be rebuilt when tape is
undergoing READ/WRITE)
1
1
No Directory (will be rebuilt when tape is
undergoing READ/WRITE)
Reserved
If set to 1, the Internal Status Byte (Byte 18) is in Bit Flags format; otherwise
Byte 18 contains a status code.
Quantum DLT 4000 Tape Drive
Bit 0
Appendix B
EEPROM-RESIDENT BUGCHECK AND EVENT LOGS
This appendix provides an explanation of the event logs (information packets) stored in semipermanent, non-volatile memory of the tape drive. These packets can be retrieved via the SCSI LOG
SENSE command with Page Code 07h.
B.1 EEPROM PACKETS (LAST N EVENTS)
The tape drive keeps certain event logs in semi-permanent, non-volatile memory
(EEPROM, in this case) located on the tape drive’s controller PCB. There is
storage enough within EEPROM for a total of 14 of these logs, or packets, each
packet consisting of 98 bytes (96 data bytes plus two control bytes) of
information. Packets may be written for different reasons and several packet
types exist.
The information in the event logs does not indicate that a tape drive or tape
medium has failed but is useful in isolating problems that may be occurring.
The logs are maintained in a circular buffer: a new entry overwrites the oldest
existing entry. At any point in time, the most recent 14 logs are kept.
The EEPROM information packets can be retrieved via the SCSI-2’s LOG
SENSE command with Page Code 07 (Last n Error Events Page).
The packet type field defines the content as well as the format of the data
portion of the packet. These packet types are detailed in this Appendix. Note
that the byte offsets in the structure layout diagrams are reference relative to the
beginning of the 98-byte EEPROM log envelope.
B.2 BUGCHECK PACKETS
Bugchecks are the result of some software-detected errors. For example, a
hardware failure or an internal system consistency failure may cause a bugcheck.
These events cause bugcheck packets to be written to EEPROM.
Quantum DLT 4000 Tape System
B-1
Appendix B: EEPROM-Resident Bugcheck and Event Logs
The most important information within the packet is the error code. The more
common bugcheck codes are listed in Table B—1. A full listing of all possible
codes is not provided: they are typically associated with firmware or product
development and are not expected once the product is released. Analysis of the
other information saved within an EEPROM bugcheck packet requires the indepth firmware knowledge to interpret and/or attempt to determine the actual
cause.
Table B–1 Bugcheck Packet Error Codes (Bytes 9 - 10)
Error
Code
Meaning and Possible Cause
E204h
Unexpected Timer 2 Interrupt – Possible Tape Drive Controller PCB fault
EE01h
Spurious Non-Maskable Interrupt – Possible Tape Drive Controller PCB fault
EE02h
Spurious 8524 Timer Interrupt – Possible Tape Drive Controller PCB fault
EE03h
Spurious Level 5 Interrupt (GPSP) – Possible Tape Drive Controller PCB fault
EE04h
Spurious Drive Comm Interrupt – Possible Tape Drive Controller PCB fault
EE05h
Spurious Loader Comm Interrupt – Possible Tape Drive Controller PCB fault
EE06h
Spurious Diag Comm Interrupt – Possible Tape Drive Controller PCB fault
EE08h
Watch Dog Expiration – SCSI bus may have lost termination, or Tape Drive
Controller PCB is constantly receiving non-tape commands.
EE09h
Spurious Power Fail Signal Received – Possible Power Supply fault.
EE0Dh
Spurious Level 6 Interrupt (GPSP) – Possible Tape Drive Controller PCB fault
F202h
Loader Time-Out – Possible Media Loader fault
B.2.1 POST Failure Packets
POST failure packets are stored whenever the Power On Self Test logic detects a
failure of any kind. Each failure is encoded as a 4-byte vector. In some cases,
multiple vectors may be stored.
If logging of POST failures occurs, contact a service representative.
B-2
Quantum DLT 4000 Tape System
Appendix B: EEPROM-Resident Bugcheck and Event Logs
B.2.2 Event Log Packets
Event log packets are non-fatal and can occur to log information about
significant events. Refer to Table B-2 for a listing of the existing error codes that
are found within event log packets.
Table B–2 Event Log Error Codes (Bytes 9 – 10)
Error
Code
[
Meaning and Possible Cause
0xA400
Hard READ Error Log - Possible Media, Cleaning Required.
0xA401
Hard WRITE Error Log - Possible Media, Cleaning Required.
0xA402
Drive Error Log – Possible Tape Drive Controller PCB or Leader.
0xA403
Loader Error Log – Possible Loader Robotics.
[
0xA404
Calibration Log1 Error Entry – Possible Cleaning Required, Media.
0xA405
Calibration Log2 Error Entry – 2nd Part of Error Code 0xA404 Calibration
Information.
0xA406
EDC Error Detected by SCSI Port Code – Possible Media, Tape Drive Controller
PCB.
[
0xA407
Directory Read Fail *
0xA408
Directory Write Fail *
0xA409
Unload Information Statistics
0xA40B
Media Quality Log – Possible Media.
0xA40C
Spurious Eject
0x40D
Directory Write on Unload Retries Failed * - Possible Cleaning Required.
0x40E
Directory Write after Read Retries Failed * - Possible Cleaning Required.
0x40F
Directory Read Retries Failure * - Possible Cleaning Required, Media.
Note: These logs are informational only.
[ = These error codes can be individual or can be multiple media error code packet.
* Directory Read and Write Fail recoverable events are discussed below.
Quantum DLT 4000 Tape System
B-3
Appendix B: EEPROM-Resident Bugcheck and Event Logs
Directory Failure Event Log Packets
Directory failure event logs are written when a directory read or directory write
request fails for any reason. Figure B-1 shows the data format and Table B-3
provides the description of important fields within the packet. Note that the byte
count begins at Byte 13, the location of the 1st event log byte within the event
log packet.
Bit
Byte
7
6
5
4
3
13
Saved Max Overwrites
14
Saved Max Rereads
15
Saved Max Rewrites
16
Dir Called Mode
17 - 18
Tape Format (when called)
19 - 20
New Tape Format
21
Flags
22
Primary Status
23
Secondary Status
24
Reserved
25
Missing Block Count
26
Total Expected LBNs
27 - 28
Servo EOT Address
29 - 32
Unique Media ID
33 - 36
CR-MSG Buffer Address
2
Figure B–1 Directory Failure Event Package – Data Format
B-4
Quantum DLT 4000 Tape System
1
0
Appendix B: EEPROM-Resident Bugcheck and Event Logs
Table B–3 Directory Failure Event Package – Field Descriptions
Field
Description
Saved Overwrites / Rereads /
Rewrites
These fields serve as temporary counters and have no use in
interpreting the directory failure packets.
Directory Called Mode
A code that specifies the original reason for the directory call.
A value of 1 indicates a directory READ (on LOAD).
A value of 2 indicates a directory WRITE (on UNLOAD).
A value of 3 indicates a directory WRITE (on WRITE from BOT).
Tape Format Called / New
These fields contain the TMSCP values for the tape format both prior
to and after the directory operation.
Flags
A bit-mapped field that provides additional status information.
Bit Mask Meaning
0x01h
READ on LOAD operation complete
0x02h
Inhibit further WRITE operations unless WRITE from BOT
0x04h
LBN 0 was found intact
0x08h
Directory WRITE failed
0x10h
Tape format mismatch
0x20h
Event log generated
0x40h
Tape format unknown
0x80h
Reserved
Quantum DLT 4000 Tape System
B-5
Appendix B: EEPROM-Resident Bugcheck and Event Logs
B-6
Quantum DLT 4000 Tape System
Appendix C
UPDATING THE FIRMWARE
This appendix explains how to update the tape drive’s PCBA-resident firmware.
C.1
OVERVIEW
Using the tape drive’s front panel and a tape with the updated firmware image,
you can update the tape drive’s PCBA-resident firmware.
CAUTION
Version 2 of the DLT 4000 tape drive requires firmware code release
V130 or higher. The drive will not function properly if a lower
version of firmware code is installed.
If a powerfail occurs during the firmware update process (when the
new image is actually being programmed into the FLASH EEPROMs),
the tape drive’s PCBA will be rendered unusable. When performing
a firmware update, take all possible precautions to prevent power
failure to the tape drive.
C.2
CREATING A FIRMWARE UPDATE TAPE
To update the tape drive’s PCBA firmware, you need a tape cartridge with a copy
of the new firmware image. The firmware image must be byte-written without
compression onto the tape using the appropriate block size as defined in Table C1. The image must be “copied” onto the tape instead of using the backup utility.
Quantum DLT 4000 Tape Drive
C-1
Appendix C: Updating the Firmware
Table C-1 Block Size Used for Firmware Update Tape
Tape Format
Density
Upgrade Tape Block
DLTtape III
2.6 GB 6.0
GB 10.0 GB
4 Kbytes Multiple 4
Kbytes Multiple 4
Kbytes Multiple
DLTtape IIIxt
15.0 GB
4 Kbytes Only
DLTtape IV
20.0 GB
4 Kbytes Only
On UN*X systems, use the FTP utility to transfer the binary firmware image. Be
sure to specify “type image” before using the “get” or “put” commands, otherwise
extra characters may be added to the file, causing the image file to be invalid.
The image file should be exactly 1286 * 512 bytes in size.
When making the update tape, copy the image file to the tape media using a
block size as defined in Table C-1, that is dd, ltf, and so on. The tape must be
uncompressed.
C.3
FIRMWARE UPDATE PROCEDURE
This section describes the procedure to update the firmware of the tape drive’s
PCBA. The update requires a cartridge that holds the update firmware image.
Firmware updates from a host are also supported (see the section on the SCSI
command WRITE BUFFER in Chapter 5).
CAUTION
If a powerfail occurs during the firmware update process (when the
new image is actually being programmed into the FLASH EEPROMs),
the tape drive’s PCBA will be rendered unusable. When performing
a firmware update, take all possible precautions to prevent power
failure to the tape drive.
C-2
Quantum DLT 4000 Tape Drive
Appendix C: Updating the Firmware
Make sure you have a DLTtape that bears the firmware image and personality of
the required revision level copied to it.
1.
Put the tape drive into the firmware update mode. To do this:
a) Remove any cartridge in the target tape drive and close the handle
(down position).
b) Press the UNLOAD button on the drive front panel and hold the button
until the WRITE PROTECT indicator begins blinking (approximately six
seconds). This indicates that the tape drive has recognized your request
for firmware update mode and is waiting for the sequence to complete.
NOTE
If the WRITE PROTECT indicator does not blink, check that:
1. The Power-On Self Test passed.
2. The drive is unloaded.
3. The drive handle is in its down position.
c) Release the UNLOAD button, then press the UNLOAD button again
within four (4) seconds. The second press should take less than one (1)
second.
d) The TAPE IN USE and the WRITE PROTECT indicators will blink. This
indicates that the tape drive recognizes that the firmware update mode
has been selected.
If you are unsuccessful in selecting the firmware update mode (if, for example,
pressing the UNLOAD button the second time requires longer than one [1]
second), the WRITE PROTECT indicator will stop blinking within several
seconds. Try the procedure again. If the drive and controller PCBA are not
communicating properly, you cannot select the firmware update function.
Once the firmware update mode has been successfully selected, insert the
cartridge with updated firmware image into the drive. The drive then
•
Automatically reads the cartridge. The tape will move for a few minutes
performing calibration and directory processing before any data is read.
•
Examines the data
•
Verifies that the data is a valid firmware image for the tape drive.
Quantum DLT 4000 Tape Drive
C-3
Appendix C: Updating the Firmware
At this point, the firmware update mode is automatically cleared. One of the
following conditions will occur:
•
If the firmware image is valid and the drive code is up-to-date, the drive code
does not go through an update.
•
If the firmware image is valid and the drive code is NOT up-to-date, the code
in the drive is updated. This will take 2 - 3 minutes
While the drive code is being updated, the WRITE PROTECT and TAPE IN USE
indicators flash alternately.
When the drive code update is complete, the drive resets, and runs its Power-On
Self Test (POST). The process waits until the tape is reloaded at the beginning
of tape (BOT).
If the firmware image is valid, the tape drive’s PCBA controller’s FLASH
EEPROM is updated with the new firmware image. The WRITE PROTECT and
TAPE IN USE indicators flash again during the controller firmware update.
C.4
INTERPRETING THE RESULTS OF A FIRMWARE UPDATE
Following a firmware update procedure, two possible results can occur:
•
The firmware update cartridge is unloaded. This signals a successful update
The tape drive rewinds the cartridge, the door is unlocked, and the green
OPERATE HANDLE indicator illuminates.
•
The firmware update cartridge is NOT unloaded. This signals an
unsuccessful update.
The tape drive subsystem may still be usable. Failure may be a result of:
•
Power failure
•
Bad firmware image on the tape
•
Non-functioning FLASH EEPROMS.
Table C-2 provides troubleshooting information.
C-4
Quantum DLT 4000 Tape Drive
Appendix C: Updating the Firmware
Table C-2 Results of Firmware Update
If...
Then...
The image is valid
1. The FLASH EEPROM containing the current firmware is
erased.
2. The new image is programmed into FLASH EEPROM
(approximately 2 minutes). Then:
The tape drive resets
The tape drive runs POST
The tape drive unloads the tape cartridge and the cartridge can
be removed. This indicates a successful firmware update.
1. The tape is NOT a
valid firmware update
tape
2. The tape does not
contain a valid firmware
image
The tape contains a
valid image but there is
a failure when
attempting to
reprogram FLASH
EEPROM
No firmware update is attempted. The WRITE PROTECT and
TAPE IN USE indicators do not blink. The drive resets and the
tape remains loaded to signal that the firmware update was
unsuccessful.
The controller PCBA is probably unusable and should be
replaced. The tape drive performs a reset and reruns POST. The
front panel LEDs are in a blinking state. POST will fail if FLASH
EEPROM does not contain a valid firmware image.
Quantum DLT 4000 Tape Drive
C-5
Appendix C: Updating the Firmware
C-6
Quantum DLT 4000 Tape Drive
Appendix D
THE TAPE CARTRIDGE
This appendix covers:
•
Tape Cartridge Handling Guidelines (subsection D.1)
•
Tape Cartridge Inspection Procedure (subsection D.2)
•
Tape Cartridge Write-Protect Switch (subsection D.3)
•
Loading a Tape Cartridge (subsection D.4)
•
Unloading a Tape Cartridge (subsection D.5)
•
Using a Cleaning Tape Cartridge (subsection D.6)
D.1 TAPE CARTRIDGE HANDLING GUIDELINES
The tape drive can use one of the following types of DLTtape cartridge:
•
DLTtape III, 1100 feet/cartridge (gray brown plastic)
•
DLTtape IIIxt, 1800 feet/cartridge (white plastic)
•
DLTtape IV, 1800 feet/cartridge (black plastic)
Ensure that your tape backup solution performs reliably by following both the
general handling guidelines described in this subsection.
HANDLING GUIDELINES
•
Always keep each tape cartridge in its protective plastic case when
it is not in the tape drive.
•
When carrying tape cartridges in their cases, always orient the cases
so that the grooves in the cases interlock. This prevents the cases
from slipping apart and falling.
•
Never stack the tape cartridges in a stack of more than five.
Quantum DLT 4000 Tape Drive
D-1
Appendix D: The Tape Cartridge
•
D-2
Always observe the proper environmental conditions for the
storage of tape cartridges. Refer to the cartridge reference card
supplied with each cartridge. The ambient operating environment
for the tape cartridge is:
Temperature
10°C to 40°C (50°F to 104°F)
Relative Humidity
20% to 80% (non-condensing)
•
If storage and/or transportation of a tape cartridge have exposed it
to conditions outside the ambient values above, you should
“condition” the tape cartridge to its operating environment for a
24-hour period.
•
When placing tape cartridges in archival storage, make sure you
stand each tape cartridge vertically.
•
Do not place cartridges on or near devices that may produce
magnetic fields such as computer monitors, motors, or video
equipment. Such exposure can alter or erase data on the tape.
Note that magnetic fields are not generally a problem since their
strength decreases as inverse of the distance from the source
cubed. Unless very near (within a few inches) a magnet or an
electric motor there is no problem. The earth exerts a magnetic
field everywhere of less than about 0.5 Oersteds. The field from a
tape that is read by a recording head is about 100 Oer. To disturb
the information on the tape would require a field larger than this
and to erase the recorded information a field larger than the
coercivity of the tape is required which would be about 2000 Oer.
field strength.
•
Never apply adhesive labels or POST-IT notes on the top, side, or
bottom of your DLTtape cartridge. Only use the user slide- in type
label provided with each cartridge and slide it over the label slot on
the cartridge.
•
Do not carry cartridges loosely in a box or any other container.
Allowing cartridges to hit together exposes them to unnecessary
physical shock.
•
Do not touch or allow direct contact with tape or tape leader. Dust
or natural skin oils can contaminate the tape and impact tape
performance.
Quantum DLT 4000 Tape Drive
Appendix D: The Tape Cartridge
•
Do not expose the tape cartridge to moisture or direct sunlight.
•
Do not insert any cartridge that has been dropped into the
DLTtape drive without at least a thorough visual inspection as
described in this paper. A dropped cartridge may have dislodged,
loosened, or damaged internal components.
•
Avoid unnecessary opening of the cartridge door; this may expose
the tape to contamination or physical damage.
•
Do not attempt to remove a tape cartridge from the tape drive
unless the Operate Handle LED lights steadily and the drive’s beeper
has sounded its tone. Overriding the drive handle will cause
damage to both the media and the tape drive.
•
Do not use graphite pencils, water-soluble felt pens, or other
debris-producing writing instruments on your labels. Never erase a
label – replace it.
•
Make sure you place the unused cartridge labels in the protective
box so that you do not inadvertently pick them up along with the
cartridge during subsequent usage. A static electricity charge on a
cartridge may cause a label to cling to the cartridge. A label that is
accidentally inserted into the drive along with a cartridge can
prevent the hub reel and drive gear from meshing.
•
Maintain clean operating, working, and storage environments.
•
Follow all tape cartridge handling instructions that accompany your
cartridges or tape drive.
Quantum DLT 4000 Tape Drive
D-3
Appendix D: The Tape Cartridge
D.2 TAPE CARTRIDGE INSPECTION PROCEDURE
Ensure that your tape backup solution performs reliably by following the Visual
Mechanical Inspection (VMI) procedures described in this subsection. These steps
will help you identify any potential tape cartridge problems, and will prevent
accidental loss of data or damage to your DLTtape system.
You should do a VMI:
•
As a general practice whenever you change or load a new tape cartridge
•
If a tape cartridge is dropped or subject to some hard physical shock
•
If the DLTtape drive becomes inoperable after loading a tape cartridge
•
If you receive a shipment of tape cartridges that show any sign of shipping
damage.
Follow these steps to visually inspect a DLTtape cartridge:
1.
Remove the tape cartridge from its protective plastic case.
2.
Look at the tape cartridge to check for any obvious cracks or other physical
damage. Look for broken or missing parts.
3.
Gently shake the tape cartridge. Listen for any rattling or sounds of any
loose pieces inside the cartridge. If you hear anything loose inside, do not
use the cartridge.
4.
Hold the tape cartridge so that the end of the cartridge that is inserted into
the DLTtape drive is facing you, as shown in Figure D-1. You will see that
there is a small opening on the left-hand side of the tape cartridge.
Reel Lock Opening
Figure D-1 Location of One of the Two Reel Lock Tabs on the DLTtape Cartridge
Inside and near the center of this opening, you should see a small plastic tab. This
is one of the reel locks. The reel locks can break if the cartridge is dropped. This
may be the cause of any rattling sound you hear when you gently shake the tape
cartridge. If this reel lock tab is not visible do not use the cartridge.
D-4
Quantum DLT 4000 Tape Drive
Appendix D: The Tape Cartridge
5.
Look at the bottom of the tape cartridge, holding it as shown in Figure D-2.
Spring-Loaded Hub
Reel Lock Opening
Figure D-2 Location of Reel Lock Opening and Spring-Loaded Hub on Bottom of
DLTtape Cartridge
Check the opening indicated in Figure D-2 and ensure that the small plastic tab is
partially visible. This is the second reel lock. The reel locks can break if the
cartridge is dropped. This may be the cause of any rattling sound you hear when
you gently shake the tape cartridge. If this reel lock tab is not visible do not use
the cartridge.
Also located on the bottom of the tape cartridge is the spring-loaded hub. Verify
that the hub is centered within the circular opening in the tape cartridge. Gently
press the hub and make sure that it springs back into place. Make sure that it
ends up centered within its circular opening.
Quantum DLT 4000 Tape Drive
D-5
Appendix D: The Tape Cartridge
6.
Ensure that the tape leader within the tape cartridge is in the correct
position. To do this, you must open the tape cartridge door. Refer to Figure
D-3.
Leader
Loop
Figure D-3 Opening the Door on a DLTtape Cartridge Showing Tape Leader Loop in its
Correct Position
Open the door by holding the DLTtape cartridge as shown in Figure D-3.
On the right side corner of the tape cartridge there is a small tab in a cut-out
portion of the cartridge. Using your thumb, gently lift up on the tab and swing the
door open (Figure D-3).
Inside the door, you will see the tape and cartridge leader loop. The loop should
stick up about an eighth of an inch when viewed from the edge; the loop must be
a closed loop. If the loop is torn, bent, pulled in, or not sticking up about an eighth
of an inch, do not use the tape cartridge.
D-6
Quantum DLT 4000 Tape Drive
Appendix D: The Tape Cartridge
7.
Figure D-4 shows three different tape cartridge loop problems. No tape
cartridge that exhibits the problems shown in the examples in Figure D-4
should be used in a DLT tape system.
Example 1: “Swallowed” Tape Cartridge Leader
Example 2: Torn or Broken Leader Loop
Example 3: Tape is Loosely Wound
Figure D-4 Three Examples of Tape Cartridges with Damage Visible during Visual
Inspection
Quantum DLT 4000 Tape Drive
D-7
Appendix D: The Tape Cartridge
8.
Finally, check for proper operation of the tape cartridge’s write-protect
switch (Figure D-5). This sliding switch, located on the end of the tape
cartridge used for the tape label, should snap smartly back and forth,
and the orange tab should be visible when the tape cartridge is set to
provide write protection (data on the tape cannot be written over).
DISABLE
WRITE-PROTECTION
ENABLE
WRITE-PROTECTION
Figure D-5 Write-Protect Switch on Tape Cartridge
By following general handling procedures, conducting careful visual inspections of
tape cartridges on a regular, ongoing basis, and making sure that tape cartridges
are stored within their environmental limits, you will greatly reduce any chance
that you will experience problems with your tape cartridges or cause damage to
your DLT tape system. Respect your media as much as you do your data.
D.3 TAPE CARTRIDGE WRITE-PROTECT SWITCH
Each tape cartridge has a write-protect switch that can be used to prevent
accidental erasure of data. Before inserting the tape cartridge into the tape drive,
position the write-protect switch on the front of the cartridge (Figure D-5):
•
Move the write-protect switch to the left to enable write protection (existing
data on the tape cannot be overwritten, nor can additional data be appended
to the media).
When the write-protect switch is moved to the left, a small orange rectangle
is visible. This indicates that data cannot be written to the tape.
D-8
Quantum DLT 4000 Tape Drive
Appendix D: The Tape Cartridge
•
Move the write-protect switch to the right to disable write protection
(existing data on the tape can be overwritten, and/or additional data can be
appended to the media unless the cartridge is write-protected via software).
When write-protect is disabled, no orange rectangle is visible.
When a tape cartridge is loaded in the drive and the tape cartridge’s write-protect
switch is moved to its write-protected position (to the left as you face the label/
switch side of the tape cartridge), the drive turns on its write-protect indicator
immediately. If the drive is currently writing to the tape, the write-protect feature
does not take effect until after the current WRITE operation completes.
Table D-1 Write-Protect Switch Positions
Write-Protect Switch
Position
Orange
Indicator
Result
Before Loading the Cartridge
Enabled
(Slide switch to left)
Visible
Data cannot be written to the tape.
Existing data on the tape cannot be overwritten.
Additional data cannot be appended to the media.
Disabled
(Slide switch to right)
Not
visible
Unless the cartridge is write-protected via software:
Data can be written to the tape.
Existing data on the tape can be overwritten.
Additional data can be appended to the media.
After Loading the Cartridge and During Operation
If the write-protect switch
is moved from its right
(disabled) position to its
left (enabled) position.
Visible
If the drive is currently writing to tape, the writeprotect feature does not take effect until AFTER the
current WRITE operation completes.
If the write-protect switch
is moved from its left
(enabled) to its right
(disabled) position.
Not
visible
The tape becomes write-enabled AFTER a variable
amount of seconds.
Quantum DLT 4000 Tape Drive
D-9
Appendix D: The Tape Cartridge
D.4 LOADING A TAPE CARTRIDGE
Complete this subsection to load a tape cartridge into the front panel (Chapter 2,
Figure 2-10) of the tape drive. Because this subsection of the manual refers to
some of the front panel LEDs and controls, it may be useful to review information
in chapter 2.5 that describe them.
1.
Only when the green Operate Handle LED is steadily lit and when the
audible beep sounds, lift the tape drive’s cartridge Insert/Release handle.
If the green Operate Handle LED is blinking, close the handle and wait for
the LED to light steadily, then lift the handle and insert the cartridge.
2.
Insert the cartridge. Push the cartridge fully into the tape drive.
CAUTION
To prevent failures and/or damage to the handle, assist the handle
to its closed position. Do not flip it down or otherwise treat it
roughly.
3.
Push the handle to its closed (down) position.
The green Operate Handle LED extinguishes and the amber Tape in Use
LED blinks to show that the tape is loading. When the tape reaches the
BOT marker, the amber LED lights steadily. The tape is now ready for use.
D-10
Quantum DLT 4000 Tape Drive
Appendix D: The Tape Cartridge
D.5 UNLOADING A TAPE CARTRIDGE
Complete this subsection to unload a tape cartridge. Because this subsection of
the manual refers to some of the front panel LEDs and controls (Chapter 2,
Figure 2-10) of the tape drive. Because this subsection of the manual refers to
some of the front panel LEDs and controls, it may be useful to review information
in chapter 2.5 that describe them.
CAUTION
Remove the tape cartridge from the tape drive BEFORE turning off
host power. Failure to remove a tape cartridge may result in
cartridge and/or tape drive damage.
When you remove a tape cartridge from the drive, return the
cartridge to its plastic case to protect the cartridge from damage.
Close the Insert/Release handle.
1.
Press the Unload button (or issue an appropriate system software
command). The amber Tape in Use LED blinks as the tape rewinds.
CAUTION
Do NOT rush removal of the tape cartridge: premature removal can
cause tape leader failure. Wait until the Operate Handle LED lights in
a steady green. Delay removing the tape cartridge for one or two
seconds to ensure that the tape leader of the cartridge is in a safe
position for cartridge removal.
2.
When the green Operate Handle LED lights steadily and you hear the
audible beep signal, lift the tape drive cartridge Insert/Release handle to its
open position to eject the cartridge.
3.
Remove the cartridge.
4.
Push the Insert/Release handle to its closed position.
Quantum DLT 4000 Tape Drive
D-11
Appendix D: The Tape Cartridge
D.6 USING A CLEANING TAPE CARTRIDGE
This subsection contains information on how and when to use a cleaning tape
cartridge. Because this subsection of the manual refers to some of the front panel
LEDs and controls (Chapter 2, Figure 2-10) of the tape drive. Because this
subsection of the manual refers to some of the front panel LEDs and controls, it
may be useful to review information in chapter 2.5 that describe them.
A cleaning cartridge has a life expectancy of approximately 20 uses.
Use Table D-2 to determine when to use a cleaning tape cartridge.
Table D–2 When to Use a Cleaning Tape Cartridge
If:
It means:
And you should:
The Use Cleaning Tape
LED is lit.
The drive head needs
cleaning or the tape
is bad.
Use the cleaning cartridge. Follow the
instructions in this chapter for loading a
cartridge into the tape drive. When
cleaning completes, the Use Cleaning Tape
LED turns off, Operate Handle lights, and
the drive’s beeper sounds a tone to alert
you that the cartridge can be removed
from the tape drive.
A data tape cartridge
causes Use Cleaning
Tape LED to light even
after a cleaning tape
has been used.
The data cartridge
may be damaged.
Back up the data from this cartridge onto
another cartridge. Discard the damaged
cartridge: use of a damaged cartridge may
cause unnecessary use of the cleaning
cartridge.
The Use Cleaning Tape
LED remains lit after
you have used a
cleaning cartridge to
clean the drive head.
Your cleaning tape
cartridge may be
exhausted.
Try another cleaning tape cartridge.
The Use Cleaning
Cartridge LED remains
lit after you have loaded
the cleaning cartridge.
The drive is still
looking for a good
piece of cleaning
tape to perform the
cleaning function.
Cleaning of the drive
has not taken place;
the cartridge has
expired.
Replace the cleaning tape cartridge.
D-12
Quantum DLT 4000 Tape Drive
Index
A
ASC/ASCQ codes,
REQUEST SENSE, 5-147
SEND DIAGNOSTIC, 5-159
ABORT message, 4-5
Acoustic noise emissions, 1-9
Altitude specification, 1-6
ATTENTION condition, 3-24
loader (rackmount), 2-14
power cord (rackmount), 2-11
SCSI (rackmount), 2-11
tabletop, 2-15
Controls
description, 2-17
front panel, 2-17
functionality, 2-20
D
B
Beeper, 2-17, 2-21
Bugcheck packets, B-1
BUS DEVICE RESET message, 4-5
BUS FREE, 3-10
BUS PARITY ERRORS, 3-11
Bus termination, 2-6, 2-8, 2-16, 2-26,
2-27
C
Data cache, 5-12
DATA-phase command components,
5-8
Density
LED functionality, 2-19
selecting, 2-21
Density codes,
MODE SELECT, 5-69
MODE SENSE, 5-101
Description
product, 1-1
DISCONNECT message, 4-6
DLTtape recording media
specifications, 1-9
Cables
connecting, 2-10
SCSI bus cable, 2-11
Capacity, 1-4
E
Cartridge insert/release handle, 2-17
Cleaning tape cartridge
EEPROM
using, D-12
Event log error codes, B-3
COMMAND COMPLETE message, 4-5
Packets (last n error events), B-1
Command descriptor block, 5-4
Resident bugcheck packets, B-1
Commands
Vendor Unique Page Parameters,
SCSI, 3-1, 5-13
5-86
Configuration, 2-3
Electromagnetic emissions, 1-7
Connectors
Quantum DLT4000 Tape Drive
Index-1
Index
EMI and safety certifications, 1-8
Environmental specifications, 1-5
ERASE command, 5-15
ESD protection, 2-3
SCSI ID, tabletop, 2-8
TERMPWR rackmount, 2-6
TERMPWR tabletop, 2-8
L
F
Firmware update,
creating a tape, C-1
interpreting results, C-4
procedure, C-2
Front panel
Cartridge insert/release handle, 2-17
controls, 2-20
LEDs, 2-18
G
Guidelines
for installation, 2-2
for tape cartridge handling, D-1
Last n error events page, B-1
LEDs
description, 2-17
functionality, 2-18
density functionality, 2-19
LINKED COMMAND COMPLETE,
4-9
LINKED COMMAND COMPLETE
with flag message, 4-9
Loading a cartridge, D-10
LOAD UNLOAD command, 5-27
LOCATE command, 5-31
LOG SELECT command, 5-33
LOG SENSE command, 5-41
M
H
Humidity specification, 1-5
I
IDENTIFY message, 4-7
INITIATOR DETECTED ERROR
message, 4-8
INQUIRY command, 5-17
Installation
connections, 2-10
rackmount, 2-8
setup, 2-3
Interface type, 1-4
Media type, 2-20, 5-98, 5-99, 5-101
MESSAGE PARITY ERROR, 4-9
MESSAGE REJECT, 4-9
MODE SELECT command, 5-63
MODE SENSE command, 5-95
N
Non-operating shock, 1-6
Non-operating vibration, 1-6
NO OPERATION message, 4-10
O
Operation codes, 5-1
J
Jumper
Disable/enable parity, 2-7, 2-8
SCSI ID, rackmount, 2-4
Index-2
Quantum DLT4000 Tape Drive
Index
P
RESTORE POINTERS message, 4-10
REWIND command, 5-153
Parity checking
rackmount, 2-7
tabletop, 2-8
Performance data, 1-4
Physical specifications, 1-3
Pin assignments
power, 2-14
SCSI differential, 2-13
SCSI single-ended, 2-12
POST
description, 2-24
tape drive states following, 2-24
ready activity, 2-24
Power connections
rackmount, 2-11
tabletop, 2-15
Power-on self test
See POST
Power requirements, 1-7
PREVENT/ALLOW MEDIUM
REMOVAL command, 5-119
Product description, 1-1
R
READ command, 5-121
READ BLOCK LIMITS command,
5-125
READ BUFFER command, 5-127
READ POSITION command, 5-131
RECEIVE DIAGNOSTICS RESULTS
command, 5-135
Recording media, 1-10
Reliability (projected), 1-8
RELEASE UNIT command, 5-137
REPORT LUNS command, 5-139
REQUEST SENSE
command, 5-141
Supported ASC/ASCQ codes, 5-147
Supported Sense Keys, 5-146
RESERVE UNIT command, 5-151
S
Safety requirements, 2-1
SAVE DATA POINTER message, 4-10
SCSI
ANSI implemented commands, 3-1
ARBITRATION, 3-12
Attention, 3-24
BUS FREE, 3-10
Bus conditions, 3-24
bus phases, 3-10
bus signal definitions, 3-6
bus timing values, 3-8
information transfer, 3-17
message format, 4-1
overview, 3-1
pointers, 5-3
queued unit attentions, 3-26
RESELECTION, 3-15
reset, 3-25
SELECTION, 3-13
signal sources, 3-5
signal values, 3-4
supported commands, 5-1
supported messages, 4-5
SCSI bus
terminating, 2-6, 2-16
SCSI cable, 2-11, 2-16
SCSI commands
ERASE (19h), 5-15
INQUIRY (12h), 5-17
LOAD UNLOAD (1Bh), 5-27
LOCATE (2Bh), 5-31
LOG SELECT (4Ch), 5-33
LOG SENSE (4Dh), 5-41
MODE SELECT (15h/55h), 5-63
MODE SENSE (1Ah/5Ah), 5-95
PREVENT/ALLOW MEDIUM
REMOVAL (1Eh), 5-119
READ (08h), 5-121
Quantum DLT4000 Tape Drive
Index-3
Index
READ BLOCK LIMITS (05h), 5-125
READ BUFFER (3Ch), 5-127
READ POSITION (34h), 5-131
RECEIVE DIAGNOSTIC RESULTS
(1Ch), 5-135
RELEASE UNIT (17h), 5-137
REPORT LUNS (A0h), 5-139
REQUEST SENSE (03h), 5-141
RESERVE UNIT (16h), 5-151
REWIND (01h), 5-153
SEND DIAGNOSTIC (1Dh), 5-155
SPACE (11h), 5-161
TEST UNIT READY (00h), 5-163
VERIFY (13h), 5-165
WRITE (0Ah), 5-167
WRITE BUFFER (3Bh), 5-169
WRITE FILEMARKS (10h), 5-173
SCSI ID
rackmount, 2-4
tabletop, 2-8
SEND DIAGNOSTIC
command, 5-155
Supported ASC/ASCQ codes, 5-159
Supported Sense Keys, 5-159
Sense keys
REQUEST SENSE, 5-146
SEND DIAGNOSTIC, 5-159
Setup, 2-3
Shock requirements
non-operating, 1-6
operating, 1-6
SPACE command, 5-161
Specifications
acoustic noise emissions, 1-9
electromagnetic emissions, 1-7
EMI and safety certifications, 1-8
environmental, 1-5
interface type, 1-4
non-operating shock, 1-6
non-operating vibration, 1-6
performance data, 1-4
physical, 1-3
power, 1-7
Index-4
recording media, 1-10
reliability (projected), 1-8
shock, 1-6
storage capacity, 1-4
tape drive recording type, 1-9
vibration, 1-6
Status/error reporting, 5-7
Storage capacity, 1-4
SYNCHRONOUS DATA TRANSFER
REQUEST message, 4-10
T
Tape cartridge
guidelines for care, D-1
handling, D-1
inspecting, D-4
labeling, D-2, D-3
loading, D-10
storage, D-2
unloading, D-11
using cleaning tape cartridge, D-12
write-protect switch, D-8
Tape drive recording type, 1-9
Temperature specifications, 1-5
TERMPWR,
rackmount, 2-6
tabletop, 2-8
TEST UNIT READY command, 5-163
Transfer rate, 1-4
Troubleshooting, 2-25
U
Unit attention condition, 5-11
Unloading a cartridge, D-11
Updating firmware, C-1
Quantum DLT4000 Tape Drive
Index
V
Vendor unique page parameters for
EEPROM, 5-86
Vendor unique sense data
request sense status codes, A-1
VERIFY command, 5-165
Vibration requirements
non-operating, 1-6
operating, 1-6
W
WRITE BUFFER command, 5-169
WRITE command, 5-167
WRITE FILEMARKS command, 5-173
Quantum DLT4000 Tape Drive
Index-5
Index
Index-6
Quantum DLT4000 Tape Drive
*81-60043-04 A01*
81-60043-04 A01
501 Sycamore Drive
Milpitas, CA 95035
(408) 894-4000
www.quantum.com
April 4, 2001
81-60043-04