Product manual

ManualsBrandsQuantum ManualsHome building and DecorDLT 8000

DLT

8000 Tape System

Product Manual

April 2, 2001

81-60118-04

Summary of content (408 pages)

PAGE 1
DLTTM 8000 Tape System Product Manual April 2, 2001 81-60118-04
PAGE 2
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.
PAGE 3
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.
PAGE 4
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.
PAGE 5
USER MANUAL STATEMENTS FOR CLASS B EQUIPMENT (continued)
PAGE 6
PAGE 7
Table of Contents Page REVISION HISTORY ......................................................................................................................................xxv ABOUT THIS MANUAL................................................................................................................................xxix CHAPTER 1: GENERAL DESCRIPTION AND SPECIFICATIONS 1.1 GENERAL DESCRIPTION..............................................................................................................
PAGE 8
Table of Contents CHAPTER 2: CONFIGURING, INSTALLING AND OPERATING THE TAPE SYSTEM 2.1 Safety, Handling, and Electrostatic Discharge (ESD) Protection...................................................2-1 2.1.1 Safety Precautions.......................................................................................................................2-1 2.1.2 Handling........................................................................................................................................2-1 2.
PAGE 9
Table of Contents CHAPTER 3: SCSI DESCRIPTION 3.1 SCSI Overview ......................................................................................................................................3-1 3.2 SCSI Commands...................................................................................................................................3-3 3.3 Signal States.......................................................................................................................................
PAGE 10
Table of Contents CHAPTER 4: SCSI MESSAGES 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)..
PAGE 11
Table of Contents 5.1.7 Data Cache and Tape Write Interaction ......................................................................... 5-12 5.2 SCSI Command Descriptions in this Manual ......................................................................... 5-13 5.3 ERASE Command (19h)............................................................................................................ 5-15 5.4 INQUIRY Command (12h).............................................................................
PAGE 12
Table of Contents 5.9.3 DISCONNECT / RECONNECT Page (02h) ........................................................................ 5-84 5.9.4 CONTROL MODE Page (0Ah)........................................................................................... 5-86 5.9.5 DATA COMPRESSION Page (0Fh).................................................................................... 5-88 5.9.6 DEVICE CONFIGURATION Page (10h) ............................................................................
PAGE 13
Table of Contents 5.17 READ POSITION Command (34h).........................................................................................5-173 5.17.1 Standard READ POSITION Data......................................................................................5-174 5.17.2 Total Current Logical Position ........................................................................................5-176 5.18 RECEIVE DIAGNOSTIC RESULTS Command (1Ch)...........................................................
PAGE 14
Table of Contents Appendix F: Timeout Specifications for DLT 8000 Tape System SCSI Commands...................F-1 Appendix G: DLT 7000 Emulation Feature..........................................................................................G-1 Index xii ..................................................................................................................................
PAGE 15
Table of Contents FIGURES Figure 2–1 Location of SCSI ID Connector Block..................................................................................2-4 Figure 2–2 Jumper Installed on Pin Pair 3 / 4 Enables Termination Power (TERM PWR) ..............2-6 Figure 2–3 Jumper Installed on Pin Pair 1 / 2 Disables Parity Checking...........................................2-7 Figure 2–4 Locations and Dimensions for Mounting Holes...............................................................
PAGE 16
Table of Contents Figure 5–13 LOAD UNLOAD Command Descriptor Block — Data Format...................................... 5-34 Figure 5–14 LOCATE Command Descriptor Block — Data Format................................................... 5-37 Figure 5–15 LOG SELECT Command Descriptor Block — Data Format ........................................... 5-39 Figure 5–16 Log Page Header Format ...................................................................................................
PAGE 17
Table of Contents Figure 5–42 Disconnect / Reconnect Page — Data Format.............................................................. 5-84 Figure 5–43 Control Mode Page Format Descriptor — Data Format.............................................. 5-86 Figure 5–44 Data Compression Page Format Descriptor — Data Format....................................... 5-88 Figure 5–45 Device Configuration Page — Data Format ...................................................................
PAGE 18
Table of Contents Figure 5–70 PREVENT / ALLOW MEDIUM REMOVAL Command Descriptor Block — Data Format................................................................................................................................5-161 Figure 5–71 READ Command Descriptor Block — Data Format.....................................................5-163 Figure 5–72 READ BLOCK LIMITS Command Descriptor Block — Data Format...........................5-167 Figure 5–73 READ BLOCK LIMITS Data — Data Format...............
PAGE 19
Table of Contents Figure 5–99 SPACE Command Descriptor Block — Data Format ...................................................5-223 Figure 5–100 TEST UNIT READY Command Descriptor Block — Data Format.............................5-225 Figure 5–101 VERIFY Command Descriptor Block — Data Format ................................................5-227 Figure 5–102 WRITE Command Descriptor Block — Data Format.................................................
PAGE 20
Table of Contents TABLES Table 1−1 Storage Capacity .......................................................................................................................1-2 Table 1−2 Performance and Timing Specifications ...............................................................................1-3 Table 1−3 Physical Dimensions ..................................................................................................................1-5 Table 1−4 Temperature and Humidity Specifications........
PAGE 21
Table of Contents Table 2–11 Indicator Activity During POST............................................................................................ 2-39 Table 2–12 Possible Tape System States Following Initialization ...................................................... 2-39 Table 2–13 Tape System Operating Modes / Indicator Activity ......................................................... 2-41 Table 2–14 Tape in Use Indicator Modes.....................................................................
PAGE 22
Table of Contents Table 5–11 Identifier Descriptor — Field Descriptions ....................................................................... 5-27 Table 5–12 Firmware Build Information Page — Field Descriptions................................................ 5-28 Table 5–13 Command Support Data Page — Field Descriptions...................................................... 5-31 Table 5–13 LOAD UNLOAD Command Descriptor Block — Field Descriptions..............................
PAGE 23
Table of Contents Table 5–36 Mode Parameter Header — Field Descriptions ............................................................... 5-78 Table 5–37 Mode Parameter Block Descriptor — Field Descriptions............................................... 5-80 Table 5–38 MODE SELECT Page Descriptor — Field Descriptions..................................................... 5-81 Table 5–39 READ/WRITE Error Recovery Page — Field Descriptions ................................................
PAGE 24
Table of Contents Table 5–64 When Do Conflicts Between Existing Reservations and New Reservations Exist? ..5-146 Table 5–65 PERSISTENT RESERVATION OUT Command — Field Descriptions..............................5-149 Table 5–66 PERSISTENT RESERVATION OUT Command’s Service Action Descriptions...............5-152 Table 5–67 Persistent Reservation Type Codes and Their Meanings..............................................5-156 Table 5–68 PERSISTENT RESERVATION OUT Parameter List – Field Descriptions............
PAGE 25
Table of Contents Table 5–92 SEND DIAGNOSTIC Command Data — Field Descriptions..........................................5-217 Table 5–93 SEND DIAGNOSTIC CDB Bits Selftst, DevOfl, and UnitOfl ...........................................5-219 Table 5–94 SEND DIAGNOSTIC Parameter List — Field Descriptions.............................................5-220 Table 5–95 Sense Keys Used for SEND DIAGNOSTIC..........................................................................
PAGE 26
Table of Contents xxiv Quantum DLT 8000 Tape System
PAGE 27
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 81-60118-01 Date of Release 81-60118-01 Nov. 6, 1998 2nd issue as preliminary manual. Changes to all chapters. Addition of information about NTF Testing in Chapters 2 and 5 and a new appendix, Appendix E. 81-60118-01 Dec. 4, 1998 3rd issue as preliminary manual.
PAGE 28
Revision History xxvi 81-60118-01 January 15, 1999 (continued) (continued) Chapter 2: Part number added for LVD connector in Figure 2-9. Change to wording of first NOTE on page 2-31 (change from “unless” to “when”). Statement about yellow indicator illuminating only after calibration added. Descriptions of “Use Cleaning Cartridge” indicator corrected. Chapter 5: List of supported parameter codes updated in Section 5.8.8, Device Status Page. Options for “Speed” field included (Table 5-37).
PAGE 29
Revision History 81-60118-02 May 7, 1999 Release as Version 02 of the Product Manual. Cover, Legal Notice Page, Table of Contents, Revision History Updated to reflect change to Version 02 and new release date. Chapter 1 Changed name of NTF Test to BHC Test (Basic Health Check). Corrected dimensions in table for Physical Dimensions. Changed Section 1.3.6 from “Operating Environment” to “Temperature and Humidity” and reorganized revision 01’s Tables 1-4 and 1-5 into a new Table 1-4. Changed Section 1.3.
PAGE 30
Revision History Manual Number - Revision Level 81-60118-02 Date of Release May 7, 1999 Summary of Changes (Updates for Version 02 continued) Updated illustrations of tabletop rear panel in Figure 2-7, 2-8, and 2-10. Changed name of NTF Test to BHC Test (Section 2.8). Chapter 5 Changed all references from NTF Test to BHC Test. Appendix A Modified Table A-2 to illustrate bit assignments more clearly. Appendix E Changed all references from NTF Test to BHC Test.
PAGE 31
Revision History Manual Number - Revision Level 81-60118-03 Date of Release November 9, 1999 Summary of Changes 1st Release as Preliminary version of Rev 03. Chapter 1: Dropped BHC from features list on page 1-1. Restated compressed transfer rate as “up to 12 MB/second,” added definition for uncorrected READ error. Modified references to variable speed recording (now called Dual Speed). Added new tape speed specs, made corrections to vibration, shock, and drop specification parameters (G for g).
PAGE 32
Revision History Manual Number - Revision Level 81-60118-03 Date of Release November 9, 1999 (continued) 81-60118-03 February 11, 2000 81-60118-03 June 29, 2000 81-60118-03 July 13, 2000 81-60118-03 September 25, 2000 Summary of Changes Incorporated information in Appendix B into REQUEST SENSE section of Chapter 5; deleted Appendix B and re-numbered Appendices C – F as B – E. Appendix C: Added note that BHC is provided only for trained service provider.
PAGE 33
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 this Quantum DLTtape system into a host system or subsystem.
PAGE 34
About This Manual Chapter 3 SCSI Description This chapter provides a detailed description of the logical interfaces of the tape system. It describes the product’s compliance with the ANSI SCSI-2 specification. The system’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 system.
PAGE 35
About This Manual Appendix F Timeout Specifications for DLT 8000 System SCSI Controls Appendix F provides the timeout specifications for the SCSI commands supported by the DLT 8000 tape system. Appendix G DLT 7000 Emulation Feature Appendix G explains how to use the DLT 7000 emulation feature on a DLT 8000 tape drive.
PAGE 36
About This Manual xxxii Quantum DLT 8000 Tape System
PAGE 37
Chapter 1 GENERAL DESCRIPTION AND SPECIFICATIONS This chapter provides a description and gives specifications for the Quantum DLT™ 8000 Tape System. 1.1 GENERAL DESCRIPTION The Quantum DLT 8000 tape system is a high-performance, high-capacity, streaming cartridge tape product designed for efficient data back up for midrange and high-end computing systems.
PAGE 38
General Description and Specifications 1.3 SPECIFICATIONS This section of provides the performance, physical, environmental, and electrical specifications for the tape system. Specifications for the DLTtape tape media cartridges are included. 1.3.1 Drive Capacity Table 1−1 provides the ranges of capacity (native and compressed) for the tape system, depending on which DLTtape cartridge is used.
PAGE 39
General Description and Specifications 1.3.3 Performance and Timing Specifications Table 1−2 provides performance and timing specifications for the tape system. Table 1−2 Performance and Timing Specifications Item Specification Transfer Rates User Native = 6.0 MB/second Compressed = Up to 12.
PAGE 40
General Description and Specifications Table 1−2 Performance and Timing Specifications (continued) Item Specification READ/WRITE Tape Speed 168 inches/second Linear Search Tape Speed 175 inches/second Rewind Tape Speed 175 inches/second Average Rewind Time 60 seconds Maximum Rewind Time 120 seconds Access Time From BOT (32KB blocks) in seconds Save Set Access Times (25 Mb Save Set) in seconds LOAD Time (Previously Written Tape) 1-4 Minimum 2 6 Average 69 70 Maximum 136 134 Average 130 s
PAGE 41
General Description and Specifications 1.3.4 Reliability (Projected) Mean time between failures (MTBF) for the tape system is projected to be 250,000 hours at 100% duty cycle, not including heads; 300,000 hours at 20% duty cycle, not including heads. Life of recording heads is 30,000 hours, minimum; 50,000 hours, average. Media durability is projected to be 1,000,000 passes of the tape medium across the read/write heads (15,000 uses).
PAGE 42
General Description and Specifications 1.3.6 Temperature and Humidity Table 1−4 provides the temperature and humidity specifications for the tape system. Table 1−4 Temperature and Humidity Specifications Description Integratible Version Tabletop Version Operating Ranges Temperature Range 50°F to 104°F (10°C to 40°C) 50°F to 104°F (10°C to 40°C) Temperature Gradient 18°F (10°C ) per hour (across the range) 18°F (10°C ) per hour (across the range) Dry Bulb Temp.
PAGE 43
General Description and Specifications 1.3.7 Operating Air Velocity Both versions of the tape system require an air flow velocity of 125 linear feet per minute measured directly in front of the bezel. 1.3.8 Vibration, Shock, and Drop Specifications Table 1−5 provides the vibration and shock specifications for operating tape systems, and for non-operating tape systems (both packaged and unpackaged). Table 1-6 provides the drop specifications for the tape system.
PAGE 44
General Description and Specifications Table 1−5 Vibration and Shock Specifications (continued) Non-Operating (Unpackaged) Vibration Specifications Vibration Type: Sine Sweep Frequency Range 5 – 500 – 5 Hz Upward and downward sweep Acceleration Level 1G 5 – 500 – 5 Hz Application X, Y, and Z axes Sweep rate: 1 octave per minute 0.010 inch DA Between 5 – 31 Hz (crossover) Vibration Type: Random Frequency Range 10 – 500 Hz Acceleration Level 2g PSD Envelope 0.
PAGE 45
General Description and Specifications Table 1−6 Drop Specifications Non-Operating (Packaged) Drop Specifications Test Type: Drop Shock Drop Height: 30 inches for items < 20.9 lbs. (9.48 kg) 23 inches for items between 21lbs (9.52 kg) and 40.9 lbs. (18.55 kg) Application 1.3.9 10 drops total; 1 each side, 3 edges, 1 corner Altitude The following table provide the tape system’s altitude specifications, both operating and non-operating.
PAGE 46
General Description and Specifications 1.3.10 Acoustic Emissions The following tables provide the tape system’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−8 Acoustic Noise Emissions, Nominal Noise Power Emission Level (LNPEc) Mode Idle Streaming Integratible Version Tabletop Version Not applicable 5.4 Bel 5.9 Bel 5.
PAGE 47
General Description and Specifications 1.3.12 Power Requirements Table 1−10 provides the applicable power requirements for both versions of the tape system. Note that the tabletop version requires ac power. Table 1−10 Power Requirements Description Integratible Version Tabletop Version Electrical Rating (Auto Ranging) Not applicable 100 to 240 VAC Power Requirements 28 W, steady state 56 W, maximum +5 V (±5%) bus * 2.8 A, steady state; 4.35 A, maximum Not Applicable +12 V (±5%) bus * 1.
PAGE 48
General Description and Specifications 1.3.13 Current Requirements Table 1-11 presents the current requirements for the tape system in a variety of operating conditions. These numbers may vary with workload. Table 1−11 Current Requirements Drive Operating in WRITE Mode Start/Stop 5 Volt 12 Volt Typical 2.2 1.2 Maximum (Includes Ripple) 3.9 3.6 Typical 2.1 1.2 Maximum (Includes Ripple) 3.3 4.
PAGE 49
General Description and Specifications 1.3.14 Tape System Recording Type The tape system uses 2,7 RLL code with DLTTM 2000, DLTTM 2000XT, DLTTM 4000, DLTTM 7000, or DLT 8000 format. 1.3.15 DLTtape Recording Media Specifications Table 1−12 provides specifications for tape media. Table 1-12 provides operating and storage environment limits for the tape cartridges Table 1−12 DLTtape Media Specifications DLTtape Media Type Specifications DLTtape III Width: 0.
PAGE 50
General Description and Specifications Table 1−12 DLTtape Media Specifications (continued) DLTtape Media Type Specifications DLTtape IV Width: 0.5 inch Length: 1800 feet Cartridge Dimensions: 4.1 in x 4.1 in x 1.0 in Shelf Life: 30 years min.
PAGE 51
General Description and Specifications 1.3.16 Electromagnetic Interference (EMI) Susceptibility This section presents tables that provide the specifications for conducted emissions, radiated emissions, magnetic radiated susceptibility, radiated susceptibility, conducted susceptibility, and ESD failure limits. Regulations and certifications for the tape system include: For electromagnetic emissions: • • CSA 108.
PAGE 52
General Description and Specifications Table 1−15 Radiated Emissions NOTE Table 1-15 shows the Class B equipment limits for radiated interference field strength in the frequency range from 30 MHz to 30 GHz at a test distance of 3 and 10 meters.
PAGE 53
General Description and Specifications Table 1−18 Conducted Susceptibility NOTE The transient voltage is the actual peak voltage above the normal ac voltage from the power source. Fast Transient (Bursts) for Power and Data Cables 2 kV S/W recoverable errors No hardware failures High Energy Transient Voltage for Power Cables * 1.2 kV No errors 2.
PAGE 54
General Description and Specifications 1-18 Quantum DLT 8000 Tape System
PAGE 55
Chapter 2 CONFIGURING, INSTALLING, AND OPERATING THE TAPE SYSTEM This chapter contains information needed for the integration of the tape system into a system or subsystem. This includes safety and handling instructions, configuration jumper settings, connector pin assignments, installation instructions, power and signal cabling descriptions, and operating instructions. 2.
PAGE 56
Configuring, Installing, and Operating the Tape System • Always handle the system carefully and gently. A drop of 1/4 inch onto a bench or desktop may damage a system. • Do not bump, jar, or drop the system. Use care when transporting the system. • Never place the tape system so that it rests on its front bezel. Always gently place the system flat, PCB side down, on an appropriate ESD-protected work surface to avoid the system being accidentally knocked over.
PAGE 57
Configuring, Installing, and Operating the Tape Drive 2.2 Configuring and Installing an Integral Tape System This section provides information for configuring and installing a tape system that is integrated into a host system, expansion cabinet, or other chassis. For information for configuring and installing a tabletop tape system, see Section 2.3.
PAGE 58
Configuring, Installing, and Operating the Tape System 2.2.1 Setting the SCSI ID Select the appropriate SCSI ID (IDs 0 through 15 are available) for the tape system by installing jumper blocks on the pin pairs of the connector block located on the tape system’s PCBA (Figure 2-1). Refer to Table 2-1 for the allowable SCSI IDs. Front Bezel SCSI ID Connector Block A jumper must always be placed across Pin Pair 9 / 10 if any SCSI ID other than the default (5) is selected.
PAGE 59
Configuring, Installing, and Operating the Tape Drive Table 2–1 SCSI ID Jumper Settings NOTES The default setting (no jumpers installed) for the tape system is SCSI ID 5. A jumper must always be placed on pin pair 9 / 10 (SCSI ID Present) for the host to recognize any SCSI ID selections made on this connector, otherwise, the SCSI ID remains SCSI ID 5. Note that the SCSI ID of the host adapter is typically SCSI ID 7.
PAGE 60
Configuring, Installing, and Operating the Tape System 2.2.2 Setting TERM PWR A SCSI bus must be terminated at each end of the bus. At least one device on the bus must supply terminator power (TERM PWR). To configure the DLT 8000 tape drive to supply TERM PWR, install a jumper block on pin pair 3 / 4 (Figure 2-2). Side View of Tape System Front Bezel Jumper on Pin Pair 3 / 4 enables termination power (TERM PWR).
PAGE 61
Configuring, Installing, and Operating the Tape Drive 2.2.3 Setting Parity Checking Parity checking is the default setting for DLT 8000 tape systems. If the system to which you are configuring the tape system does not generate parity, disable parity checking on the tape system by installing a jumper block on pin pair 1 / 2 on the connector as shown in Figure 2-3. Note that this is the same connector as the one used to select the setting for TERM PWR (Section 2.2.2).
PAGE 62
Configuring, Installing, and Operating the Tape System 2.2.4 Installing the Tape System Installing the tape system requires securing the tape system in its bay or chassis and connecting SCSI bus and power cables. 2.2.4.1 Securing the Tape System in Bay or Chassis Using four (4) screws, secure the tape system in its bay or chassis. Figure 2-4 is a dimensional drawing that shows the locations of the mounting holes at the bottom and sides of the tape system.
PAGE 63
Configuring, Installing, and Operating the Tape Drive Figure 2–4 Locations and Dimensions for Mounting Holes Quantum DLT 8000 Tape System 2-9
PAGE 64
Configuring, Installing, and Operating the Tape System 2.2.4.2 Connecting SCSI Bus and Power Cables Carefully connect the appropriate SCSI and power cables to their matching connectors. Figure 2-5 shows the location of the SCSI and power connectors on the rear of the tape system. Tables 2-2 through 2-4 provide SCSI pin signal names/locations for the SCSI connectors. Table 2-5 provides power connector signal names/locations.
PAGE 65
Configuring, Installing, and Operating the Tape Drive Table 2–2 68-Pin Single-Ended Configuration SCSI Connector Signal Names Signal Name Pin Number Pin Number Signal Name Signal Return Signal Return Signal Return Signal Return Signal Return Signal Return Signal Return Signal Return Signal Return Signal Return Signal Return Signal Return Signal Return Signal Return Signal Return 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
PAGE 66
Configuring, Installing, and Operating the Tape System Table 2–3 68-Pin Wide LVD Version SCSI Connector Signal Names Signal Name +DB(12) +DB(13) +DB(14) +DB(15) +DB(P1) +DB(0) +DB(1) +DB(2) +DB(3) +DB(4) +DB(5) +DB(6) +DB(7) +DB(P) GROUND DIFFSENS TERMPWR TERMPWR RESERVED GROUND +ATN GROUND +BSY +ACK +RST +MSG +SEL +C/D +REQ +I/O +DB(8) +DB(9) +DB(10) +DB(11) 2-12 Pin Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 Pin Number 35 36 37 38 39 40 41 42 43
PAGE 67
Configuring, Installing, and Operating the Tape Drive Table 2–4 68-Pin Differential Version SCSI Connector Signal Names Signal Name Pin Number Pin Number Signal Name +DB(12) +DB(13) +DB(14) +DB(15) +DB(P1) Ground +DB(0) +DB(1) +DB(2) +DB(3) +DB(4) +DB(5) +DB(6) +DB(7) +DB(P) DIFFSENS TERMPWR TERMPWR Reserved +ATN Ground +BSY +ACK +RST +MSG +SEL +C/D +REQ +I/O Ground +DB(8) +DB(9) +DB(10) +DB(11) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 3
PAGE 68
Configuring, Installing, and Operating the Tape System Table 2–5 Power Connector Signal Names Pin Signal 1 +12 VDC 2 Ground (+12 V return) 3 Ground (+5 V return) 4 +5 VDC 2.2.4.3 The Loader Connector Located on the side of the integratible tape system (Figure 2-6), the loader connector provides signals used when the tape system is part of a loader configuration.
PAGE 69
Configuring, Installing, and Operating the Tape Drive 2.3 Configuring and Installing a Tabletop Tape System This section provides instructions for configuring and installing the tabletop version of the tape system. The tabletop version is enclosed in a top cover and the enclosure includes a separate power supply. The power switch and the SCSI ID selection switch are located on the unit’s rear panel. SCSI cables and the unit’s ac power cable are connected at the rear panel.
PAGE 70
Configuring, Installing, and Operating the Tape System Figure 2–7 Physical Dimensions of DLT 8000 Tabletop System 2-16 Quantum DLT 8000 Tape System
PAGE 71
Configuring, Installing, and Operating the Tape Drive 2.3.1 Selecting SCSI ID Select the appropriate SCSI ID for the tabletop version of the tape system by incrementing or decrementing the number displayed on the SCSI ID selection switch on the tabletop tape system’s rear panel (Figure 2-8). Press either the small switch above the indicator to increment the number, or the small switch below the indicator to decrement the number. Note that the default SCSI ID of the system is SCSI ID 3.
PAGE 72
Configuring, Installing, and Operating the Tape System 2.3.2 Connecting the SCSI Bus Cables Figure 2-9 shows the locations of the two SCSI bus connectors on the rear panel of the tabletop tape system. The SCSI bus cable leading from the host adapter can be connected to either of the connectors. If the tape unit is the last device on the bus, then a terminator should be installed on the open connector.
PAGE 73
Configuring, Installing, and Operating the Tape Drive 2.3.3 Installing the AC Power Cord WARNING Do not attempt to modify or use an external 100 - 115 VAC power cord for 220 240 VAC input power. Modifying the power cord in any way can cause personal injury and severe equipment damage. An ac power cord is supplied with each tabletop tape unit. Carefully inspect the power cord and ensure that the cord is the appropriate cord for your country or region based on the criteria below.
PAGE 74
Configuring, Installing, and Operating the Tape System 115 V 220 / 240 V Figure 2–10 AC Power Cord Plug Ends 2-20 Quantum DLT 8000 Tape System
PAGE 75
Configuring, Installing, and Operating the Tape Drive Figure 2-11 shows the location of the ac power cord connector on the tabletop tape system’s rear panel.
PAGE 76
Configuring, Installing, and Operating the Tape System 2.
PAGE 77
Configuring, Installing, and Operating the Tape Drive 2.4.1 Care and Handling of Tape Cartridges Although designed and manufactured to withstand much handling and use, tape cartridges should be handled properly. • Do not carry cartridges loosely in a box or other container that exposes them to unnecessary physical shock. • Store each cartridge vertically in its protective case until needed. • Do not drop or bump the cartridge; this may dislodge and/or damage internal components.
PAGE 78
Configuring, Installing, and Operating the Tape System • 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 has exposed it to conditions outside the ambient values above, you should “condition” the tape cartridge to its operating environment for a 24-hour period. • Place labels only in the front slide slot of the cartridge.
PAGE 79
Configuring, Installing, and Operating the Tape Drive 2.4.2 Tape Cartridge Write-Protect Switch Tape Cartridge (Label End) Write-Protect Switch pushed to the right (Write Protect disabled position) Orange Rectangle Visible Write-Protect Switch pushed to the left (Write Protect enabled position) Figure 2-12 Write-Protect Switch on Tape Cartridge Each tape cartridge has a write-protect switch that can be used to prevent accidental erasure of data.
PAGE 80
Configuring, Installing, and Operating the Tape System When a tape cartridge is loaded in the system 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 system turns on its Write Protect indicator immediately. If the system is currently writing to the tape, the write-protect feature does not take effect until after the current WRITE operation completes.
PAGE 81
Configuring, Installing, and Operating the Tape Drive 2.4.3 Checking a Tape Cartridge Before you insert any tape cartridge, you should inspect it to ensure that it is not damaged. Refer to Appendix E for a detailed visual mechanical inspection procedure and other DLTtape cartridge-related information. • Open the tape cartridge door and check the position of the tape leader. • Close the tape cartridge door and shake the cartridge, listening for a rattle sound.
PAGE 82
Configuring, Installing, and Operating the Tape System 2.4.4 Loading a Cartridge NOTE Because this section of the manual includes descriptions of the states of indicators on the tape system, it may be useful to review sections of this chapter that describe tape system indicators, their states, and meanings of states. Follow these steps to load a tape cartridge into the front panel of the tape system. Figure 2-13 illustrates the tape system’s front panel.
PAGE 83
Configuring, Installing, and Operating the Tape Drive 1. When the green Operate Handle indicator is steadily illuminated, lift the tape system’s cartridge Insert/Release handle. NOTE If the green Operate Handle indicator is blinking, close the handle and wait for the indicator to illuminate steadily, then lift the handle and insert the cartridge. Do not attempt to load a cartridge when the green Operate Handle indicator is blinking; damage to the system may result. 2. Insert the cartridge.
PAGE 84
Configuring, Installing, and Operating the Tape System 2.4.5 Unloading a Cartridge NOTE Because this section of the manual includes descriptions of the states of indicators on the tape system, it may be useful to review sections of this chapter that describe tape system indicators, their states, and meanings of states. Follow the steps below the first CAUTION notice to unload a tape cartridge. CAUTION Always remove the tape cartridge from the tape system BEFORE turning off host power.
PAGE 85
Configuring, Installing, and Operating the Tape Drive 3. Remove the cartridge. 4. Push the Insert/Release handle to its closed position. 2.4.6 How and When to Use a Cleaning Tape Cartridge NOTE Because this section of the manual includes descriptions of the states of indicators on the tape system, it may be useful to review sections of this chapter that describe tape system indicators, their states, and meanings of states. Use Table 2-9 to determine when to use a cleaning tape cartridge.
PAGE 86
Configuring, Installing, and Operating the Tape System Table 2–9 When to Use a Cleaning Cartridge (continued) If It means And you should…. The Use Cleaning Tape indicator continues to be illuminated steadily after you have used a cleaning cartridge to clean the recording head Your cleaning tape cartridge may be exhausted. Try another cleaning tape cartridge.
PAGE 87
Configuring, Installing, and Operating the Tape Drive 2.5 Operating the Tape System – Controls and Indicators Operating the tape system requires use of a tape cartridge and the controls and indicators on the front panel, or bezel, of the tape system. All controls and indicators are located on the tape system’s front panel or bezel (Figure 2-13). Use these controls and indicators to operate the tape system and monitor the tape system’s activities.
PAGE 88
Configuring, Installing, and Operating the Tape System 2.5.1 Unload Button Use the Unload Button to unload the tape cartridge. When a user pushes the Unload Button, the tape system waits until any active writing of data to tape is completed, then begins its unload sequence. The tape system rewinds the tape medium back into the cartridge and writes the current or updated tape directory to the tape.
PAGE 89
Configuring, Installing, and Operating the Tape Drive 2.5.3 Selecting Density CAUTION If the tape is not positioned at End of Data (EOD), a WRITE to the tape will deny access to previously recorded data beyond the current tape position. To prevent this, position the tape to EOD, then perform the WRITE. This condition is termed an “appended WRITE.” NOTES TM 1. Default capacity of a DLTtape (compression ON). 2. Default capacity of a DLTtape IIIXT cartridge is 15.0 GB, native (compression OFF), or 30.
PAGE 90
Configuring, Installing, and Operating the Tape System To select density on the tape system, Load the tape cartridge into the tape system. The yellow Tape in Use indicator blinks while the tape loads and calibrates. After calibration is complete, the Tape In Use indicator remains steadily illuminated. The appropriate tape density indicator along the left edge of the system’s front panel illuminates to indicate the tape’s prerecorded density (if any).
PAGE 91
Configuring, Installing, and Operating the Tape Drive Table 2–10 Indicator Light Activity During Density Selection If… Then… The Density Select Button is not used The illuminated indicators show data density when the tape is being read from and written to. The indicators illuminate steadily; Density Override remains extinguished.
PAGE 92
Configuring, Installing, and Operating the Tape System 2.6 Power On Self Test (POST) and Indicator Activity During POST When power is applied to the tape system, it performs power-on self testing (POST). The sequence of events that may be observed is: Table 2–11 Indicator Activity During POST Stage What Can be Observed 1 Indicators on the right-hand side of the front panel illuminate in sequence from top to bottom. All indicators remain illuminated for a few seconds.
PAGE 93
Configuring, Installing, and Operating the Tape Drive Table 2–12 Possible Tape System States Following Initialization (continued) State Indicator Display and Activity A tape cartridge is present, but the handle is up (not recommended) The yellow Tape In Use indicator extinguishes. The green Operate Handle indicator 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 system.
PAGE 94
Configuring, Installing, and Operating the Tape System 2.7 Tape System Operating Modes and Indicator Activity Table 2-13 describes the various operating conditions of a tape system and what observations can be made of the various indicators for each mode. A detailed description of the modes for the Tape in Use indicator is provided.
PAGE 95
Configuring, Installing, and Operating the Tape Drive illuminate steadily Quantum DLT 8000 Tape System 2-41
PAGE 96
Configuring, Installing, and Operating the Tape System Table 2–13 Tape System Operating Modes / Indicator Activity (continued) Front Panel Indicator All four right-hand or all six left-hand indicators 10.0 / 15.0 20.0 35.0 40.0 Compress Density Override 2-42 Color of Indicator --- Yellow Yellow Yellow Yellow Yellow Yellow State Operating Mode On POST is beginning Blinking An error has occurred. See Section 2.9 for troubleshooting. On Tape is recorded in 10.0 / 15.
PAGE 97
Configuring, Installing, and Operating the Tape Drive (automatic) Tape in Use Indicator and Modes Whenever the yellow Tape in Use indicator is illuminated steadily, the tape system and cartridge are ready to use. When the system is calibrating, reading, writing, or rewinding the tape, the Tape in Use indicator blinks. Table 2-14 explains each of the modes of the Tape in Use Indicator. Table 2–14 Tape in Use Indicator Modes If the yellow Tape in Use Indicator is… It means….
PAGE 98
Configuring, Installing, and Operating the Tape System 2.8 Using the DLT 8000 Tape System’s Basic Health Check (BHC) Test Feature NOTE The BHC feature is provided for use only by a trained service provider. The BHC test uses the tape system’s firmware to check the various EEROM-based information packets for log entries of events that have occurred in the previous 120 hours of operation. Based on that information, the system can report on its “health.” The test is pass/fail only.
PAGE 99
Configuring, Installing, and Operating the Tape Drive 2.9 Troubleshooting Use Table 2-15 for troubleshooting tips in the event that your tape system fails its power-on self test or if it signals a problem via its front panel indicators. Table 2–15 Troubleshooting Chart If… Then… You Should… System does not recognize the tape system System may not be configured to recognize the SCSI ID.
PAGE 100
Configuring, Installing, and Operating the Tape System Table 2–15 Troubleshooting Chart (continued) If… Then… You Should… System does not recognize the tape system (continued) 1. SCSI bus may be too long. 1. 2. Too many devices on the bus. Limit bus length to ANSI SCSI standard for the SCSI interface being used. 2. Limit the number of devices on the bus (including the SCSI adapter) to match the limits of the interface being used.
PAGE 101
Configuring, Installing, and Operating the Tape Drive Table 2–15 Troubleshooting Chart (continued) If… Then… You Should… Indicators along right-hand side of front panel are blinking and the Operate Handle Light is illuminated steadily The tape leader may be dropped. Open the handle and look inside the tape system. If the tape leader is missing contact your service representative. Also, check the tape cartridges for damage.
PAGE 102
PAGE 103
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 16 devices (wide SCSI). ANSI defines three primary objectives of SCSI-2: 1.
PAGE 104
SCSI Description 3.2 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. Table 3–1 Implemented ANSI SCSI-2 Commands 3-2 Command Code Class Description ERASE 19h Mandatory Causes part of the entire tape medium to be erased, beginning at the current position on the logical unit.
PAGE 105
SCSI Description Table 3–1 Implemented ANSI SCSI-2 Command (continued) Command Code Class Description MODE SELECT (6) 15h Optional Provides a means for the initiator to specify device parameters. MODE SENSE (6)/(10) 1Ah/ 5Ah Optional Provides a means for a drive to report parameters to the initiator. PREVENT ALLOW MEDIUM REMOVAL 1Eh Optional Requests that the target enables or disables the removal of the medium in the logical unit.
PAGE 106
SCSI Description Table 3–1 Implemented ANSI SCSI-2 Command (continued) 3-4 Command Code Class Description 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 Mandatory Requests the drive to write the data transferred from the initiator to the medium.
PAGE 107
SCSI Description 3.3 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.
PAGE 108
SCSI Description connector. Chapter 2, Configuring, Installing, and Operating the Tape System has full instructions for setting the SCSI ID.
PAGE 109
SCSI Description 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 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.
PAGE 110
SCSI Description Table 3–3 SCSI-2 Bus Signal Definitions (continued) Signal Definition 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. Table 3–4 SCSI Bus Timing Values Timing Description Value Description Arbitration Delay 2.
PAGE 111
SCSI Description Table 3–4 SCSI Bus Timing Values (continued) Timing Description Value Description 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.
PAGE 112
SCSI Description Table 3–4 SCSI Bus Timing Values (continued) Timing Description Value Transfer Period 2 2 3-10 Description 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, fast synchronous. Set during an SDTR message.
PAGE 113
SCSI Description 3.5 SCSI Bus Phases The SCSI architecture includes eight distinct phases: BUS FREE phase ARBITRATION phase SELECTION phase RESELECTION phase COMMAND phase DATA phases (In/Out) STATUS phase 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.
PAGE 114
SCSI Description 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.
PAGE 115
SCSI Description 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.
PAGE 116
SCSI Description 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.
PAGE 117
SCSI Description 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.
PAGE 118
SCSI Description 4. 3-16 Sets the DATA BUS to the logical OR of its SCSI ID bit and the initiator’s SCSI ID bit.
PAGE 119
SCSI Description 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. 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.
PAGE 120
SCSI Description 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. The initiator asserts the RST signal. 2. The initiator follows these steps: a) Continues asserting the SEL and ATN signals and releases the DATA BUS.
PAGE 121
SCSI Description NOTES (continued) 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.
PAGE 122
SCSI Description Information Transfer Direction True I/O Signal: from drive to initiator False I/O Signal: from initiator to drive Table 3–5 Information Transfer Phases MSG Signal 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.
PAGE 123
SCSI Description 3.5.5.1 Asynchronous Data Transfer Drive to Initiator Transfer Procedure 1. The drive drives the DB (0-15, P, & P1) 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 (0-15, P, & P1) 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 (0-15, P, & P1) signals. 7.
PAGE 124
SCSI Description 3.5.5.2 Synchronous Data Transfer 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.
PAGE 125
SCSI Description 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 (0-15, P, & P1) signals to their desired values. The DB (0-15, P, & P1) 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.
PAGE 126
SCSI Description • 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.
PAGE 127
SCSI Description 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 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.).
PAGE 128
SCSI Description 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.
PAGE 129
SCSI Description Table 3–6 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.
PAGE 130
SCSI Description • 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.
PAGE 131
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 disk 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.
PAGE 132
Messages The DLT 8000 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).
PAGE 133
Messages Table 4–2 Supported Messages Message Message Code ABORT 06h Out BUS DEVICE RESET 0Ch Out COMMAND COMPLETE 00h In DISCONNECT 04h In Out EXTENDED MESSAGE (SDTR and wide Data Transfer Request) * 01h In Out 80h – FFh In Out IGNORE WIDE RESIDUE 23h In INITIATOR DETECTED ERROR 05h 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
PAGE 134
Messages Bit 7 6 5 4 3 2 1 0 Byte 0 Extended Message (01h) 1 Extended Message Length 2 Extended Message Code 3 to n-1 Extended Message Arguments 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.
PAGE 135
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.
PAGE 136
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.
PAGE 137
Messages 4.2.5 IDENTIFY Message (80h - FFh) The IDENTIFY message is sent by either the initiator or the drive to establish or reestablish 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.
PAGE 138
Messages 4.2.6 IGNORE WIDE RESIDUE Message (23h) The IGNORE WIDE RESIDUE message is sent by the target to the initiator to indicate that the number of valid bytes sent during the last REQ/ACK handshake and REQB/ACKB handshake of a DATA IN phase is less than the negotiated transfer width. The Ignore field indicates the number of invalid data bytes transferred. This message is sent immediately following that DATA IN phase and prior to any other messages.
PAGE 139
Messages 4.2.7 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 drive-related.
PAGE 140
Messages 4.2.8 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.
PAGE 141
Messages 4.2.12 NO OPERATION (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.
PAGE 142
Messages 4.2.15 SYNCHRONOUS DATA TRANSFER REQUEST Message (01h) 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. 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.
PAGE 143
Messages 4.2.16 WIDE DATA TRANSFER REQUEST Message (03h) The following figure illustrates the message formats.
PAGE 144
Messages The DLT 8000 tape drive implements both wide data transfer option and synchronous data transfer option. It negotiates the wide data transfer agreement prior to negotiating the synchronous data transfer agreement. If a synchronous data transfer agreement is in effect, then after accepting a WIDE DATA TRANSFER REQUEST message, it resets the synchronous agreement to asynchronous mode. The transfer width is two the transfer width exponent bytes wide.
PAGE 145
Chapter 5 SCSI COMMANDS This chapter describes the SCSI protocol features implemented in the DLT 8000 tape system. 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 SCSI COMMANDS The Quantum DLT 8000 tape system supports the SCSI commands listed in Table 5–1.
PAGE 146
SCSI Commands Table 5–1 Supported SCSI Commands (continued) Command REPORT LUNS REQUEST SENSE RESERVE UNIT (6) RESERVE UNIT (10) REWIND SEND DIAGNOSTIC SPACE TEST UNIT READY VERIFY WRITE WRITE BUFFER WRITE FILEMARKS Operation Code A0h 03h 16h 56h 01h 1Dh 11h 00h 13h 0Ah 3Bh 10h Subsection 5.22 5.23 5.24 5.25 5.26 5.27 5.28 5.29 5.30 5.31 5.32 5.33 NOTES 5-2 1. Relative Addressing is not supported by the tape drive. Therefore, in all I/O commands, the RelAdr bit must be 0. 2.
PAGE 147
SCSI Commands 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.
PAGE 148
SCSI Commands 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.
PAGE 149
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.
PAGE 150
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.
PAGE 151
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). Messagelevel 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.
PAGE 152
SCSI Commands 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. 5.1.
PAGE 153
SCSI Commands Table 5–5 DATA-Phase Command Contents Command ERASE INQUIRY Length in CDB Data Out (To Drive) Data In (To Initiator) 0 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) / (10) Parameter List MODE SENSE (6) / (10) Allocation --- Mode Parameter Header (4) Block Descriptor (8) Page(s) PERSISTENT RESERVATION IN Allocation -
PAGE 154
SCSI Commands Table 5–5 DATA-Phase Command Contents (continued) Length in CDB Data Out (To Drive) REPORT LUNS Allocation --- Supported LUNS List REQUEST SENSE Allocation --- Sense Data (18) 0 (Extent List Option not supported) --- --- 0 --- --- Parameter List Diagnostic Page --- SPACE 0 --- --- TEST UNIT READY 0 --- --- VERIFY Transfer Data --- WRITE Transfer Data --- Parameter List Microcode Image Data --- --- --- --- Command RESERVE UNIT REWIND SEND DIAGNOSTIC W
PAGE 155
SCSI Commands 5.1.6 Behavior at Power-On and SCSI Bus Reset The following apply to the DLT 8000 tape drive’s behavior at power-on and/or SCSI bus reset: • When the Quantum DLT 8000 system is powered up, all device SCSI lines are set to high impedance. • The design of the DLT 8000 tape drive does not allow it to generate any spurious signals on the SCSI bus at power-on.
PAGE 156
SCSI Commands 5.1.7 Data Cache and Tape Write Interaction The Quantum DLT 8000 system tape 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.
PAGE 157
SCSI Commands 5.2. SCSI COMMAND DESCRIPTIONS IN THIS MANUAL 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.
PAGE 158
SCSI Commands 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 below: Bit 7 6 5 4 3 2 1 0 Byte (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 is bit 0 of byte 8.
PAGE 159
SCSI Commands 5.3 ERASE Command (19h) The ERASE command causes data on the tape medium to be erased. NOTE ERASE command MUST be issued while at BOT.
PAGE 160
SCSI Commands ERASE Command (19h) (continued) Table 5–6 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. NOTE The ERASE command results in no operation for the tape drive unless the Long bit is set to 1.
PAGE 161
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 applicable interfacing protocol. The drive does not need to access its storage medium to respond to the inquiry.
PAGE 162
SCSI Commands INQUIRY Command (12h) (continued) Table 5–7 INQUIRY Command Descriptor Block — Field Descriptions Field Description CmdDt Command Support Data. If CmdDt = 0 and EVPD (see below) = 0, the drive returns the Standard Inquiry Data. If CmdDt = 1 with EVPD = 0, the drive returns the Command Data specified by Page Code/Operation. Information about Command Support Data is provided in Figure 5-12 and Table 5-13. EVPD Enable Vital Product Data.
PAGE 163
SCSI Commands INQUIRY Command (12h) (continued) Bit 7 6 5 4 3 2 1 0 Byte 0 1 2 3 Peripheral Qualifier Peripheral Device Type RMB Device Type Modifier ISO Version AENC TrmIOP ECMA Version ANSI Version Reserved Response Data Format 4 Additional Length = 33h 5 Reserved 6 Rsv’d MChngr 7 RelAdr Wbus32 Reserved Wbus16 Sync Linked 8 - 15 Vendor Identification (QUANTUM ) 16 - 31 Product Identification (DLT8000 ) 32 - 35 Product Revision Level (hhss) 36 - 55 Vendor Uniqu
PAGE 164
SCSI Commands INQUIRY Command (12h) (continued) Table 5–8 contains field descriptions for the data returned by the drive. Table 5–8 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.
PAGE 165
SCSI Commands INQUIRY Command (12h) (continued) Table 5–8 Standard Inquiry Data Page — Field Descriptions (continued) Field Name Value Description Product Revision Level This field contains 4 bytes of ASCII data that provides the drive’s firmware 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.
PAGE 166
SCSI Commands INQUIRY Command (12h) (continued) 5.4.2 Vendor Unique Inquiry Data The following information can be used to precisely identify the revision of subsystem components.
PAGE 167
SCSI Commands INQUIRY Command (12h) (continued) Table 5–9 Vendor Unique Inquiry Data Page — Field Descriptions Field Name Description Product Family This field indicates the data density of each of the DLT tape drives as follows: Released Firmware Product Family Bit Drive Density 0 Not Specified 3 10.0 / 20.0 GB 5 20.0 / 40.0 GB 6 15.0 / 30.0 GB 7 35.0 / 70.0 GB 8 40.0 / 80.0 GB This flag differentiates between released and test versions of firmware.
PAGE 168
SCSI Commands 5.4.3 Supported Vital Product Data Pages and Command Support Data 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.
PAGE 169
SCSI Commands INQUIRY Command (12h) (continued) The Unit Serial Number Page (80h) Bit 7 6 5 4 3 2 1 0 Byte 0 Peripheral Qualifier 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–10 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 typically starting with “CX” indicating the site of
PAGE 170
SCSI Commands INQUIRY Command (12h) (continued) The Device Identification Page (83h) Bit 7 6 5 4 3 2 1 0 Byte 0 Peripheral Qualifier Peripheral Device Type 1 Page Code (83h) 2 Reserved 3 Page Length (n-3) 4-n Identification Descriptors Figure 5–9 Device Identification Page — Data Format There are three different Device Identification Descriptors returned, in numerical order of the Identifier Type.
PAGE 171
SCSI Commands INQUIRY Command (12h) (continued) Table 5–11 Identifier Descriptor — Field Descriptions Field Name Description Code Set The value in this field indicates the type of data to be found in the Identifier field. Code Meaning 1 2 Binary data ASCII data Association The value in this field indicates whether the Identifier is associated with the logical unit (LUN) or the port. The default for this field = 0, designating associating with the LUN.
PAGE 172
SCSI Commands INQUIRY Command (12h) (continued) The Firmware Build Information Page (VU) (C0h) Bit 7 6 5 4 3 2 1 0 Byte 0 Peripheral Qualifier 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–11 Firmware Build Information Page — Data Format Table 5–12 Firmware Build Information Page — Field Descriptions Field Name Descrip
PAGE 173
SCSI Commands INQUIRY Command (12h) (continued) The Subsystem Components Revision Page (C1h) This page contains information used by Quantum Corporation about firmware, drive controller, and other DLT 8000 tape drive components. It is reserved for use by Quantum Corporation and should not be used for other purposes.
PAGE 174
SCSI Commands INQUIRY Command (12h) (continued) Command Support Data An application client can request command support data by setting the CmdDt bit of the INQUIRY command to 1, and specifying the SCSI operation code of the Command Descriptor Block (CDB) for which it wants information. Format of the command support data and definitions of the fields follow.
PAGE 175
SCSI Commands INQUIRY Command (12h) (continued) Table 5–13 Command Support Data Page — Field Descriptions Field Description Support The value of the Support field describes the type of support that the tape drive provides for Command Support Data. Value Description 000b Data about the requested SCSI operation code is not currently available. In this case, all data after Byte 1 is undefined. 001b The device does not support the SCSI operation code requested.
PAGE 176
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.
PAGE 177
SCSI Commands LOAD UNLOAD Command (1Bh) (continued) Bit 7 6 5 4 3 2 1 0 Byte 0 1 Operation Code (1Bh) Logical Unit Number Reserved 2 Reserved 3 Reserved 4 5 Reserved Unused EOT Reserved Immed Re-Ten Load Flag Link Figure 5–13 LOAD UNLOAD Command Descriptor Block — Data Format Quantum DLT 8000 Tape System 5-33
PAGE 178
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.
PAGE 179
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.
PAGE 180
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.
PAGE 181
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.
PAGE 182
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.
PAGE 183
SCSI Commands LOG SELECT Command (4Ch) (continued) 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.
PAGE 184
SCSI Commands LOG SELECT Command (4Ch) (continued) 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.
PAGE 185
SCSI Commands LOG SELECT Command (4Ch) (continued) LOG PARAMETERS Bit 7 6 5 4 3 2 1 0 Byte (MSB) 0 -1 Parameter Code (LSB) 2 DU DS TSD 3 ETC TMC Rsv’d LP Parameter Length (MSB) 4-7 Parameter Value (LSB) Figure 5–17 Log Parameters Format Table 5–18 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 01h 02h 03h 04h 05h 06h 8000h Errors corrected with
PAGE 186
SCSI Commands LOG SELECT Command (4Ch) (continued) Table 5–18 Log Parameters Field Descriptions (continued) Field Name Description NOTE Byte 2 of the Log Parameter Block is referred to as the Parameter Control Byte; it is made up of six control bits plus one bit that is reserved. 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.
PAGE 187
SCSI Commands LOG SELECT Command (4Ch) (continued) Table 5–18 Log Parameters Field Descriptions (continued) Field Name Description 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.
PAGE 188
SCSI Commands LOG SELECT Command (4Ch) (continued) 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: • 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 ascend
PAGE 189
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.
PAGE 190
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.
PAGE 191
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.
PAGE 192
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.
PAGE 193
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.
PAGE 194
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.
PAGE 195
SCSI Commands LOG SENSE Command (4Dh) (continued) LOG PARAMETERS Bit 7 6 5 4 3 2 1 0 Byte (MSB) 0 -1 Parameter Code (LSB) 2 DU DS TSD 3 ETC TMC Rsv’d LP Parameter Length (MSB) 4 - 11 Parameter Value (LSB) Figure 5–21 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: Parame
PAGE 196
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 NOTE: Byte 2 of the Log Parameter Block is referred to as the Parameter Control Byte; it is made up of six control bits plus one bit that is reserved. DU Disable Update. This field with a value 0 indicates that the target will update all log parameter values.
PAGE 197
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 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.
PAGE 198
SCSI Commands LOG SENSE Command (4Dh) (continued) 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 48).
PAGE 199
SCSI Commands LOG SENSE Command (4Dh) (continued) LOG PARAMETERS Bit 7 6 5 4 3 2 1 0 Byte (MSB) 0 -1 Parameter Code (LSB) 2 DU DS TSD ETC 3 TMC Rsv’d LP Parameter Length (MSB) 4-n Hex ASCII String for Event n (LSB) Figure 5–23 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, where 0 is the oldest even
PAGE 200
SCSI Commands LOG SENSE Command (4Dh) (continued) 5.8.5 TapeAlert Page (2Eh) This page returns results of the tape drive’s on-going self diagnosis, so that the tape drive’s behavior can be monitored and high reliability ensured.
PAGE 201
SCSI Commands LOG SENSE Command (4Dh) (continued) TAPE ALERT LOG PARAMETERS Bit 7 6 5 4 3 2 1 0 Byte 5n –1 to 5n (MSB) 5n + 1 Parameter Code ( n) (LSB) DU DS TSD ETC TMC Rsv’d 5n + 2 Parameter Length (1) 5n + 3 Value of TapeAlert Flag (Flag is set when Bit 0 = 1; Bits 1 – 7 are Reserved) LP Figure 5–25 Log Parameters Format for TapeAlert Page Table 5–25 Log Parameter Field Descriptions for TapeAlert Page Field Name Description Parameter Code This field contains the Flag code.
PAGE 202
SCSI Commands LOG SENSE Command (4Dh) (continued) Table 5–26 Tape Alert Flags, Severity Levels, and Meanings Flag Severity Level * Meaning 1 Read Warning Warning Problems reading data. There is no loss of data, but the tape drive’s performance is reduced. 2 Write Warning Warning Problems writing data. There is no loss of data, but the capacity of the tape is reduced.
PAGE 203
SCSI Commands LOG SENSE Command (4Dh) (continued) Table 5–26 Tape Alert Flags, Severity Levels, and Meanings (continued) Flag Severity Level * Meaning 22 Expired Cleaning Media Critical The cleaning cartridge that was used has expired. Wait for all tape drive operations to complete, then use a valid cleaning cartridge for cleaning. 31 Hardware B Critical The tape drive may have a hardware fault. Contact a service representative.
PAGE 204
SCSI Commands LOG SENSE Command (4Dh) (continued) 5.8.6 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.
PAGE 205
SCSI Commands LOG SENSE Command (4Dh) (continued) LOG PARAMETERS FOR PARAMETER CODES 00h AND 01h Bit 7 6 5 4 3 2 1 0 Byte (MSB) 0 -1 Parameter Code (LSB) 2 DU DS TSD ETC 3 TMC Rsv’d LP 02h (MSB) 4-n Compression Ratio x 100 (LSB) Figure 5–27 Log Parameters Format for READ / WRITE COMPRESSION RATIO LOG SENSE Page (Parameter Codes 00h and 01h) Table 5–28 Log Parameters for READ / WRITE COMPRESSION RATIO LOG SENSE Page Field Descriptions (Parameter Codes 00h and 01h) Field Name Descript
PAGE 206
SCSI Commands LOG SENSE Command (4Dh) (continued) LOG PARAMETERS FOR PARAMETER CODES 02h THROUGH 09h Bit 7 6 5 4 3 2 1 0 Byte (MSB) 0 -1 Parameter Code (LSB) 2 DU DS TSD 3 ETC TMC Rsv’d LP 04h (MSB) 4-7 Counter Value (LSB) Figure 5–28 Log Parameters Format for READ / WRITE COMPRESSION RATIO LOG SENSE Page (Parameter Codes 02h through 09h) Table 5–29 Log Parameters for READ / WRITE COMPRESSION RATIO LOG SENSE Page Field Descriptions (Parameter Codes 02h through 09h) Field Name Descr
PAGE 207
SCSI Commands LOG SENSE Command (4Dh) (continued) Table 5–29 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.
PAGE 208
SCSI Commands LOG SENSE Command (4Dh) (continued) 5.8.7 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).
PAGE 209
SCSI Commands LOG SENSE Command (4Dh) (continued) DEVICE WELLNESS LOG SENSE PAGE PARAMETERS (0000h - 000Fh) Bit 7 6 5 4 3 2 1 0 Rsv’d LP Byte 0 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–30 Log Parameters Format for DEVICE WELLNESS LOG SENSE Page Quantum DLT 8000 Tape System 5-65
PAGE 210
SCSI Commands LOG SENSE Command (4Dh) (continued) Table 5–31 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.
PAGE 211
SCSI Commands LOG SENSE Command (4Dh) (continued) 5.8.8 Device Status Page (3Eh) The Device Status Page describes the current status of the tape drive. Figures 5-31 and 5-32 and Table 5-32 describe the following header log parameter formats for the log sense device status page. Code 0000h 0001h 0002h 0003h 0004h 0005h Provides Device type. Device cleaning-related status Number of “loads” over the lifetime of the tape drive. Specifies the number of cleaning sessions per cartridge.
PAGE 212
SCSI Commands LOG SENSE Command (4Dh) (continued) DEVICE STATUS LOG SENSE PAGE PARAMETERS Bit 7 6 5 4 3 2 1 0 Rsv’d LP Byte 0-1 2 Parameter Code DU 3 DS TSD ETC TMC Parameter Length (04h) (MSB) 4-7 Parameter Value (LSB) Figure 5–32 Log Parameters Format for DEVICE STATUS LOG SENSE Page 5-68 Quantum DLT 8000 Tape System
PAGE 213
SCSI Commands LOG SENSE Command (4Dh) (continued) Table 5–33 Log Parameters for DEVICE STATUS LOG SENSE Page Field Descriptions Field Name Description Parameter Codes 0000h through 0005h are supported. Parameter Value Code Description 0000h Specifies device type. For sequential-type devices such as tape drives, the value is always 00010000h. Specifies device cleaning-related status. See Figure 5-30. Specifies the number of “loads” over the lifetime of the tape drive.
PAGE 214
SCSI Commands LOG SENSE Command (4Dh) (continued) Table 5–34 Log Parameters for DEVICE WELLNESS LOG SENSE Parameter 0001h (Cleaning Related) Field Descriptions Field Name Description ClnR Set to 1 if a cleaning required condition exists. When the condition clears, this status is also cleared. ClnQ Set to 1 if a cleaning request condition exists. When the condition clears, this status is also cleared. ClnEx Set to 1 if the cleaning tape has expired.
PAGE 215
SCSI Commands 5.9 MODE SELECT Command (6) / (10) (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.
PAGE 216
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) MODE SELECT (6) Command Descriptor Block — Data Format Bit 7 6 5 4 3 2 1 0 Byte 0 Operation Code (15h) 1 Logical Unit Number PF 2-3 Reserved SP (0) Reserved 4 Parameter List Length 5 Unused Reserved Flag Link MODE SELECT (10) Command Descriptor Block — Data Format Bit 7 6 5 4 3 2 1 0 Byte 0 Operation Code (55h) 1 Logical Unit Number PF Reserved 2-6 Reserved 7-8 Parameter List Length 9 Unused
PAGE 217
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–35 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.
PAGE 218
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Bit 7 6 5 4 3 2 1 0 Byte 0-7 Mode Parameter Header 8 - 15 Mode Parameter Block Descriptor (Optional) 8-n or 16 - n Page(s) (Optional) Figure 5–36 MODE SELECT (10) Mode Parameter List — Data Format Table 5–36 MODE SELECT (6) or (10) Mode Parameter List — Field Descriptions Field Name Description Mode Parameter Header Contains information about the remainder of the Parameter List and is always present (see Figure 5-37 an
PAGE 219
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) 5.9.1.1 Mode Parameter Header The figures and tables that follow provide an illustration and description of the fields that make up the MODE SELECT (6) or (10) command’s Mode Parameter header.
PAGE 220
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–37 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.
PAGE 221
SCSI Commands MODE SELECT Command (6) / (10) (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.
PAGE 222
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–38 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 Description 00h Use default density 19h 62500 bpi, 64 track pairs, serial cartridge tape – 10.0 GB (DLTtape III) / 15.0 GB (DLTtape IIIXT) 1Ah 81633 bpi, 64 track pairs, serial cartridge tape – 20.
PAGE 223
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–38 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).
PAGE 224
SCSI Commands MODE SELECT Command (6) / (10) (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.
PAGE 225
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–40 READ/WRITE 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.
PAGE 226
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) 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.
PAGE 227
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–41 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.
PAGE 228
SCSI Commands MODE SELECT Command (6) / (10) (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.
PAGE 229
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–42 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.
PAGE 230
SCSI Commands MODE SELECT Command (6) / (10) (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.
PAGE 231
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–43 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.
PAGE 232
SCSI Commands MODE SELECT Command (6) / (10) (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.
PAGE 233
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–44 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.
PAGE 234
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–44 Device Configuration Page — Field Descriptions (continued) Field Name Description 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.
PAGE 235
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) 5.9.7 MEDIUM PARTITION PAGE (11h) The drive supports the Medium Partition Parameters Page, which is used to specify the medium partitions.
PAGE 236
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–45 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.
PAGE 237
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) 5.9.8 TAPEALERT PAGE (1Ch) The drive supports the TapeAlert Page, which is, used to set/change the supported TapeAlert configuration options (use the MODE SENSE command to read the settings of the TapeAlert page).
PAGE 238
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–46 TapeAlert Page Format 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.
PAGE 239
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–46 TapeAlert Page Format Descriptor — Field Descriptions (continued) Field Name Description MRIE Method for Reporting Informational Exceptions. The tape drive uses the contents of this field to report information about exception conditions. Three methods are available: Value Method 00h No reporting of Informational Exception Conditions. The device server does not report information exception conditions.
PAGE 240
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) 5.9.9 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.
PAGE 241
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–47 EEPROM Vendor Unique Page Parameters Default Length (Bytes) Name Value Rep.
PAGE 242
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–47 EEPROM Vendor Unique Page Parameters (continued) Default Length (Bytes) ASCII Decimal 1 1 1 - 7 = LUN to report media loader device on. 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). Name Value Rep. LOADERLUN REWINDONRESET Usage 1 = Rewind the tape medium to BOT on reset.
PAGE 243
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–47 EEPROM Vendor Unique Page Parameters (continued) Default Length (Bytes) ASCII Binary 0 1 To make variable READ command handled as if the SILI bit is set if set. ASCII Decimal 0 1 0,1 = Do not cache filemarks unless IMMED bit is set (if set) Name Value Rep. FORCEREADSILI CACHETMS Usage 2 = Cache if not two in a row unless IMMED bit is 1. 3 = Always cache filemarks.
PAGE 244
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) Table 5–47 EEPROM Vendor Unique Page Parameters (continued) ASCII Decimal Default 2 Length (Bytes) 1 SCSIRESELRETRIES ASCII Decimal 10 1 SCSIRDYEARLY ASCII Binary 0 1 REPORTRCVRDERR ASCII Binary 0 1 NORDYUAONUNLD ASCII Binary 0 1 HOSTCOMPSETTING ASCII Decimal 0 1 REDUNDANCYMODE ASCII Decimal 0 1 REPBUSYINPROG ASCII Binary 0 1 Name SCSIBUSDMATIMER Value Rep.
PAGE 245
SCSI Commands Table 5–47 EEPROM Vendor Unique Page Parameters (continued) Default Length (Bytes) ASCII Decimal 0 1 ENAGRANULARITY ASCII Binary 1 1 ENASCSIFILTER ENAREQACKACTNEG ASCII Binary ASCII Binary 1 1 1 1 SETEOMATBOM ASCII Binary 0 1 SETEOMATEW ASCII Binary 0 1 REPUAONSEQUNLD ASCII Binary 0 1 DISDEFERCLNRPT ASCII Binary 0 1 ENASCSIUNLONPMR ASCII Binary 0 1 MAXBURSTSIZE ASCII Binary 0080h 2 SPEEDSETTING ASCII Decimal 3 1 TAMRIEDEFAULT ASCII Binary 3 1 Name
PAGE 246
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) As an example of an EEPROM vendor unique page, the figure below shows a page that will modify the VENDORID parameter to “XXXYY.
PAGE 247
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) An example follows that illustrates an EEPROM vendor unique page that modifies the FORCEDENSITY parameter to 4.
PAGE 248
SCSI Commands MODE SELECT Command (6) / (10) (15h) / (55h) (continued) 5.9.10 Changeable Parameters within MODE SELECT The table below 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.
PAGE 249
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 below. An illustration of the command descriptor block for the 10-byte MODE SENSE (5Ah) follows on the next page.
PAGE 250
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Bit 7 6 5 4 3 2 1 0 Byte 0 1 Operation Code (5Ah) Logical Unit Number 2 Rsv’d DBD PC Reserved Page Code 3 Reserved 4 Reserved 5 Reserved 6 Reserved (MSB) 7-8 Allocation Length (LSB) 9 Unused Reserved Flag Link Figure 5–52 MODE SENSE (10) Command Descriptor Block — Data Format 5-106 Quantum DLT 8000 Tape System
PAGE 251
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Table 5–49 MODE SENSE Control 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. PC Page Control. The Page Control field indicates the type of page parameter values to be returned to the host.
PAGE 252
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 below.
PAGE 253
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Bit 7 6 5 4 3 2 1 0 Byte (MSB) 0-1 Mode Sense Data Length (LSB) 2 3 Media Type WP Buffered Mode Speed 4 Reserved 5 Reserved (MSB) 6-7 Block Descriptor Length (08h) (LSB) Figure 5–54 MODE SENSE (10) Data Header — Data Format Quantum DLT 8000 Tape System 5-109
PAGE 254
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Table 5–50 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 follows that is available to be transferred during the DATA IN phase. Note that the Mode Sense Data Length does not include itself.
PAGE 255
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) 5.10.2 MODE SENSE Block Descriptor The illustration below describes the MODE SENSE block descriptor that follows the MODE SENSE header. Bit 7 6 5 4 3 2 1 0 Byte 0 Density Code (MSB) 1-3 Number of Blocks (000000h) (LSB) 4 Reserved (MSB) 5-7 Block Length (LSB) Figure 5–55 MODE SENSE Block Descriptor — Data Format Descriptions of the MODE SENSE blocks are provided in the table on the following page.
PAGE 256
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Table 5–51 MODE SENSE 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 19h 1Ah 1Bh 41h Description Use default density 62500 bpi, 64 track pairs, serial cartridge tape – 10.0 GB (DLTtape III) / 15.0 GB (DLTtape IIIXT) 81633 bpi, 64 track pairs, serial cartridge tape – 20.
PAGE 257
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Table 5–50 MODE SENSE Block Descriptor — Field Descriptions (continued) Field Name Description Number of Blocks 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. Block Length This field specifies the length (in bytes) of each logical block transferred over the SCSI bus.
PAGE 258
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) 5.10.3 MODE SENSE Mode Pages The illustration below depicts the variable length page descriptor. Bit 7 6 PS 0 5 4 3 2 1 0 Byte 0 Page Code 1 Additional Page Length 2 Page Defined or Vendor-Unique Parameter Bytes Figure 5–56 MODE SENSE Page Descriptor — Data Format Descriptions of the MODE SENSE page descriptor fields are provided in the table below. Detailed descriptions of each of the MODE SENSE Pages follow.
PAGE 259
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Page codes and pages that are supported are: 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 1Ch TapeAlert Page BOTH 5.
PAGE 260
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 below.
PAGE 261
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Table 5–53 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.
PAGE 262
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) 5.10.3.2 DISCONNECT / RECONNECT Page (02h) The tape drive supports the DISCONNECT / RECONNECT Page. The format for the page is illustrated below.
PAGE 263
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Table 5–54 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.
PAGE 264
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.
PAGE 265
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Table 5–55 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.
PAGE 266
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.
PAGE 267
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Table 5–56 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.
PAGE 268
SCSI Commands 5.10.3.5 Device Configuration Page (10h) The tape drive supports the Device Configuration Page. The format for the page is illustrated below.
PAGE 269
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Table 5–57 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.
PAGE 270
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Table 5–57 Device Configuration Page — Field Descriptions (continued) Field Name Description 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.
PAGE 271
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 below.
PAGE 272
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Table 5–58 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.
PAGE 273
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) 5.10.3.7 TAPEALERT PAGE (1Ch) The TapeAlert configuration settings can be read via the MODE SENSE command’s TapeAlert Page.
PAGE 274
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Table 5–59 TapeAlert Page Format 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.
PAGE 275
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) Table 5–59 TapeAlert Page Format Descriptor — Field Descriptions (continued) Field Name Description Test Not Supported. LogErr Error Log. Not Supported MRIE Method for Reporting Informational Exceptions. The tape drive uses the contents of this field to report information about exception conditions. Three methods are available: Value Method 00h No reporting of Informational Exception Conditions.
PAGE 276
SCSI Commands MODE SENSE (6) / (10) Command (1Ah / 5Ah) (continued) 5.10.3.8 EEPROM Vendor Unique page (3Eh) The tape drive supports the EEPROM vendor unique page (3Eh). All the EEPROM parameters settable via the MODE SELECT’s 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.
PAGE 277
SCSI Commands 5.11 PERSISTENT RESERVATION IN Command (5Eh) The PERSISTENT RESERVATION IN command is a 10-byte command used to obtain information about persistent reservations and reservations that are active within a device server. It is used in conjunction with the PERSISTENT RESERVATION OUT command. Note that reservations are not persistent across power cycles. The figure below illustrates the format of the PERSISTENT RESERVATION IN command; the table that follows explains the data fields of the command.
PAGE 278
SCSI Commands PERSISTENT RESERVATION IN Command (5Eh) (continued) Table 5–60 PERSISTENT RESERVATION IN Command — Field Descriptions Data Field Description Service Action Service actions that require information about persistent reservation and registrations may require enabling of nonvolatile memory within the logical unit.
PAGE 279
SCSI Commands PERSISTENT RESERVATION IN Command (5Eh) (continued) The figure and table below illustrate and describe the data fields of Read Key data parameters.
PAGE 280
SCSI Commands PERSISTENT RESERVATION IN Command (5Eh) (continued) Table 5–61 Read Keys Parameters — Field Descriptions Data Field Description Generation The value in this field is a 32-bit counter in the device server that is incremented each time a PERSISTENT RESERVATION OUT command requests a Register, Clear, Pre-empt, or Pre-empt and Clear operation.
PAGE 281
SCSI Commands PERSISTENT RESERVATION IN Command (5Eh) (continued) The figure and table below illustrate and describe the data fields of Read Reservations data parameters.
PAGE 282
SCSI Commands PERSISTENT RESERVATION IN Command (5Eh) (continued) The figure and table below illustrate and describe the data fields of each Read Reservations descriptor’s data fields.
PAGE 283
SCSI Commands PERSISTENT RESERVATION IN Command (5Eh) (continued) Table 5–63 PERSISTENT RESERVATION IN Read Reservations Descriptor — Field Descriptions Data Field Reservation Key Scope-Specific Address Description The Reservation key field contains an 8-byte value that identifies the reservation key under which the persistent reservation is held.
PAGE 284
SCSI Commands PERSISTENT RESERVATION IN Command (5Eh) (continued) Table 5–63 PERSISTENT RESERVATION IN Read Reservations Descriptor — Field Descriptions (continued) Data Field Description Type The value of the Type field specifies the characteristics of the persistent reservation being established for all data blocks within the extent or within the logical unit.
PAGE 285
SCSI Commands PERSISTENT RESERVATION IN Command (5Eh) (continued) Table 5–64 Persistent Reservation Type Codes and Their Meanings Code 0h Name Description READ Shared READS: Shared; any application client on any initiator may execute commands that perform transfers from the target to the initiator. WRITES: Prohibited; any command from any initiator that performs a transfer from the initiator to the target results in a reservation conflict.
PAGE 286
SCSI Commands PERSISTENT RESERVATION IN Command (5Eh) (continued) Table 5-64 Persistent Reservation Type Codes and Their Meanings (continued) Code 3h Name Description Exclusive; any command from any initiator other than the initiator holding the persistent reservation that attempts a transfer from the target results in a reservation conflict.
PAGE 287
SCSI Commands PERSISTENT RESERVATION IN Command (5Eh) (continued) Table 5–64 Persistent Reservation Type Codes and Their Meanings (continued) Code 5h Name Description WRITE Exclusive, READS: Registrants Only WRITES: Shared; any application client on any initiator may execute commands that perform transfers from the target to the initiator.
PAGE 288
SCSI Commands PERSISTENT RESERVATION IN Command (5Eh) (continued) Table 5–65 When Do Conflicts Between Existing Reservations and New Reservations Exist? Persistent Reservation Already Held READ Shared LU EX WRITE Exclusive LU EX READ Exclusive LU EX Exclusive Access * LU EX Shared Access * LU EX WRITE Exclusive RO LU EX Exclusive Access RO LU EX LU N N Y Y Y Y Y Y N N Y Y Y EX N N Y O Y O Y O N N Y O Y O LU Y Y Y Y Y Y Y Y Y Y Y Y Y Y WRITE Exclusive EX Y
PAGE 289
SCSI Commands 5.12 PERSISTENT RESERVATION OUT Command (5Fh) The PERSISTENT RESERVATION OUT command is a 10-byte command used to reserve a logical unit or an extent within a logical unit for the exclusive or shared use by an initiator. Note that reservations are not persistent across power cycles. The command is used in conjunction with the PERSISTENT RESERVATION IN command; it is not used with the RESERVE and RELEASE commands. Persistent reservations conflict with reservations made via the RESERVE command.
PAGE 290
SCSI Commands PERSISTENT RESERVATION OUT Command (5Fh) (continued) Bit 7 6 5 4 3 2 1 0 Byte 0 Operation Code (5Fh) 1 Reserved 2 Service Action Scope 3-6 Type Reserved (MSB) 7–8 Parameter List Length (18h) (LSB) 9 Unused Reserved Flag Link Figure 5–68 PERSISTENT RESERVATION OUT Command Descriptor Block — Data Format 5-146 Quantum DLT 8000 Tape System
PAGE 291
SCSI Commands PERSISTENT RESERVATION OUT Command (5Fh) (continued) Table 5–66 PERSISTENT RESERVATION OUT Command — Field Descriptions Data Field Description Service Action Service actions that require information about persistent reservation and registrations may require enabling of nonvolatile memory within the logical unit.
PAGE 292
SCSI Commands PERSISTENT RESERVATION OUT Command (5Fh) (continued) Table 5–66 PERSISTENT RESERVATION OUT Command — Field Descriptions (continued) Data Field Description Scope The value in this field indicates whether a persistent reservation applies to an entire logical unit, to a part of the logical unit (defined as an extent), or to an element. The values for the Scope field are: Code Name Description 0h LU Logical Unit. Persistent reservation applies to the full logical unit.
PAGE 293
SCSI Commands PERSISTENT RESERVATION OUT Command (5Fh) (continued) Table 5–66 PERSISTENT RESERVATION OUT Command — Field Descriptions (continued) Data Field Description Type The value of the Type field specifies the characteristics of the persistent reservation being established for all data blocks within the extent or within the logical unit.
PAGE 294
SCSI Commands PERSISTENT RESERVATION OUT Command (5Fh) (continued) Table 5–67 PERSISTENT RESERVATION OUT Command’s Service Action Descriptions Code Name Description 00h Register When the command executes a Register service action, it registers a reservation key with a device server without generating a reservation.
PAGE 295
SCSI Commands PERSISTENT RESERVATION OUT Command (5Fh) (continued) Table 5–67 PERSISTENT RESERVATION OUT Command’s Service Action Descriptions (continued) Code Name Description 02h Release A PERSISTENT RESERVATION OUT command with Release service action removes a persistent reservation held by the same initiator. The fields associated with a Release service action match fields of the active persistent reservation.
PAGE 296
SCSI Commands PERSISTENT RESERVATION OUT Command (5Fh) (continued) Table 5–67 PERSISTENT RESERVATION OUT Command’s Service Action Descriptions (continued) Code Name Description 04h Preempt A PERSISTENT RESERVATION OUT command with a successful Pre-empt service action removes all persistent reservations for all initiators that have been registered with the Service action Reservation key specified in the PERSISTENT RESERVATION OUT command’s parameter list.
PAGE 297
SCSI Commands PERSISTENT RESERVATION OUT Command (5Fh) (continued) Table 5–67 PERSISTENT RESERVATION OUT Command’s Service Action Descriptions (continued) Code Name Description 05h Pre-empt & Clear A PERSISTENT RESERVATION OUT command with a Pre-empt & Clear service action removes all persistent reservations for all initiators that have been registered with the Service action Reservation key specified in the PERSISTENT RESERVATION OUT command’s parameter list.
PAGE 298
SCSI Commands PERSISTENT RESERVATION OUT Command (5Fh) (continued) Table 5–68 presents the definitions of the characters of the available “Type” values from the Type field of the PERSISTENT RESERVATION IN Read Reservations parameters. Each of the codes provides handling instructions for READ operations, for WRITE operations, and for subsequent attempts to establish persistent reservations (referred to as “Additional Reservations Allowed” in the table).
PAGE 299
SCSI Commands PERSISTENT RESERVATION OUT Command (5Fh) (continued) Table 5-68 Persistent Reservation Type Codes and Their Meanings (continued) Code 3h Name Description Exclusive Access READS: Exclusive; any command from any initiator other than the initiator holding the persistent reservation that attempts a transfer from the target results in a reservation conflict.
PAGE 300
SCSI Commands PERSISTENT RESERVATION OUT Command (5Fh) (continued) Table 5-68 Persistent Reservation Type Codes and Their Meanings (continued) Code 6h Name Description Exclusive Access, READS: Exclusive; any command from an initiator that has not previously performed a Register service action with the device server that attempts a transfer from the target results in a reservation conflict.
PAGE 301
SCSI Commands PERSISTENT RESERVATION OUT Command (5Fh) (continued) Table 5-69 PERSISTENT RESERVATION OUT Parameter List — Field Descriptions Data Field Description Reservation Key This field contains an 8-byte token that is provided by the application client to the device server to identify which initiator is the source of the PERSISTENT RESERVATION OUT command.
PAGE 302
SCSI Commands PERSISTENT RESERVATION OUT Command (5Fh) (continued) The table below illustrates which fields are set by the application client and interpreted by the device server for each Service and Scope value.
PAGE 303
SCSI Commands 5.13 PREVENT / ALLOW MEDIUM REMOVAL Command (1Eh) This command enables or disables the unloading of the tape cartridge.
PAGE 304
SCSI Commands 5.14 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 7 6 5 4 3 2 1 0 SILI Fixed Byte 0 Operation Code (08h) 1 Logical Unit Number Reserved (MSB) 2-4 Transfer Length (LSB) 5 Unused Reserved Flag Link Figure 5–71 READ Command Descriptor Block — Data Format Table 5–72 READ Command Descriptor Block — Field Descriptions Field Name Description SILI Suppress Incorrect Length Indicator.
PAGE 305
SCSI Commands READ Command (08h) (continued) Table 5–72 READ Command Descriptor Block — Field Descriptions (continued) Field Name Description 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.
PAGE 306
SCSI Commands READ Command (08h) (continued) The meaning of EOM 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.
PAGE 307
SCSI Commands 5.15 READ BLOCK LIMITS Command (05h) The READ BLOCK LIMITS command directs the tape drive to report its block length limits.
PAGE 308
SCSI Commands READ BLOCK LIMITS Command (05h) (continued) The READ BLOCK LIMITS data shown below 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.
PAGE 309
SCSI Commands 5.16 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. In addition, by using buffers 1 and 2, the READ BUFFER command allows the contents of the tape system’s local RAM/EEPROM, and DRAM to be transferred over the SCSI bus. Buffers 1 and 2 provide a diagnostic capability for the system’s firmware.
PAGE 310
SCSI Commands READ BUFFER Command (3Ch) (continued) Table 5–74 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. Buffer ID Mode Description 000b 010b 011b Combined Header and Data (see 5.16.1) Data (see 5.16.2) Descriptor (see 5.16.3) Must be 0, 1, or 2.
PAGE 311
SCSI Commands READ BUFFER Command (3Ch) (continued) 5.16.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 figure below illustrates the format of the header.
PAGE 312
SCSI Commands READ BUFFER Command (3Ch) (continued) Bit 7 6 5 4 3 2 1 0 Byte 0 Offset Boundaries (0Ch) (MSB) 1-3 Buffer Capacity (LSB) Figure 5–76 READ BUFFER Descriptor — Data Format 5-168 Quantum DLT 8000 Tape System
PAGE 313
SCSI Commands 5.17 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.
PAGE 314
SCSI Commands READ POSITION Command (34h) (continued) 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. 5.17.
PAGE 315
SCSI Commands READ POSITION Command (34h) (continued) Table 5–77 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. Since the tape drive does not support more than one partition, the value of this field will be 1 when at BOT. EOP End of Partition.
PAGE 316
SCSI Commands READ POSITION Command (34h) (continued) 5.17.
PAGE 317
SCSI Commands 5.18 RECEIVE DIAGNOSTIC RESULTS Command (1Ch) The RECEIVE DIAGNOSTIC RESULTS command fetches the results of the last SEND DIAGNOSTIC command sent to the tape drive.
PAGE 318
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.
PAGE 319
SCSI Commands 5.19 RELEASE UNIT (6) Command (17h) The RELEASE UNIT (6) command is a 6-byte command that 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.
PAGE 320
SCSI Commands RELEASE UNIT (6) Command (17h) (continued) Table 5–80 RELEASE UNIT (6) 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 thirdparty reservation option. If this bit is 0, then the third-party release option is not requested.
PAGE 321
SCSI Commands 5.20 RELEASE UNIT (10) Command (57h) The RELEASE UNIT and the RESERVE UNIT commands are used for contention resolution in multiple-initiator systems. The RELEASE (10) command is a 10-byte command used to release a previously reserved logical unit. The drive will not return an error if the initiator attempts to release a reservation that is not currently valid.
PAGE 322
SCSI Commands RELEASE UNIT (10) Command (57h) (continued) Table 5–81 RELEASE UNIT (10) Command — Field Descriptions Field Description 3rdPty Third Party Release allows an initiator to release a logical unit that was previously reserved. If the value in this field is 0, third party release is not requested.
PAGE 323
SCSI Commands 5.21 REPORT DENSITY SUPPORT Command (44h) The REPORT DENSITY SUPPORT command is a 10-byte command used to request that information about the densities supported by the logical unit be sent to the application client. Note that a reservation conflict will occur when a REPORT DENSITY SUPPORT command is received from any initiator other than the one holding a logical unit reservation.
PAGE 324
SCSI Commands REPORT DENSITY SUPPORT Command (44h) (continued) Table 5–82 REPORT DENSITY SUPPORT Command — Field Descriptions Data Field Description Media When this bit = 0, it indicates that the device server will return density support data blocks for densities supported by the logical unit for any supported media. When this bit = 1, it indicates that the device server will return density support data blocks for densities supported by the mounted medium.
PAGE 325
SCSI Commands REPORT DENSITY SUPPORT Command (44h) (continued) Table 5–83 REPORT DENSITY SUPPORT Header — Field Descriptions Data Field Description Available Density Support Length This value within this field specifies the number of bytes in the data that follows available to be transferred. Note that this length value does not include this field. The value within this field is equal to 2 more than an integer multiple of 52 (the length in bytes of a density support data block descriptor).
PAGE 326
SCSI Commands REPORT DENSITY SUPPORT Command (44h) (continued) Bit 7 6 5 4 3 2 1 0 Byte 0 Primary Density Code 1 Secondary Density Code 2 WRTOK 3-4 DUP DEFLT Reserved Reserved (MSB) 5–7 Bits Per MM (LSB) (MSB) 8–9 Media Width (LSB) (MSB) 10–11 Tracks (LSB) (MSB) 12–15 Capacity (LSB) (MSB) 16–23 Assigning Organization (LSB) (MSB) 24–31 Density Name (LSB) (MSB) 32–51 Description (LSB) Figure 5–86 Density Support Data Block Descriptor — Data Format 5-182 Quantum DLT 8000 T
PAGE 327
SCSI Commands REPORT DENSITY SUPPORT Command (44h) (continued) Table 5-84 Density Support Data Block Descriptor — Field Descriptions Data Field Description Primary Density Code This field contains the value returned by a MODE SENSE command for the density described in the remainder of the Density Support Data Block Descriptor. Allowable Density Codes for the tape system are shown in Table (To Be Supplied).
PAGE 328
SCSI Commands REPORT DENSITY SUPPORT Command (44h) (continued) Table 5-84 Density Support Data Block Descriptor — Field Descriptions (continued) Data Field Description Bit Per MM Bits per millimeter. The value in this field indicates the number of bits per millimeter per track as recorded on the tape medium. Note that the value is rounded up if the fractional value of the actual value is greater than or equal to 0.5.
PAGE 329
SCSI Commands 5.22 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.
PAGE 330
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–88 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.
PAGE 331
SCSI Commands 5.23 REQUEST SENSE Command (03h) The REQUEST SENSE command causes the tape drive to transfer detailed sense data to the initiator.
PAGE 332
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.
PAGE 333
SCSI Commands REQUEST SENSE Command (03h) (continued) Bit Byte 0 1 2 7 6 5 4 Valid Filemark EOM ILI 3 2 Error Code Segment Number (0) Reserve d 1 0 Sense Key (MSB) 3-6 Information Bytes (LSB) 7 Additional Sense Length (MSB) 8 - 11 Command-Specific Information Bytes (LSB) 12 13 14 15 16 - 17 SKSV (MSB) C/D Additional Sense Code Additional Sense Code Qualifier Sub-Assembly Code (0) Reserved BPV Bit Counter Field Pointer (LSB) 18 Internal Status Code (VU) 19 - 20 Tape Motion Hour
PAGE 334
SCSI Commands REQUEST SENSE Command (03h) (continued) Table 5–87 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.
PAGE 335
SCSI Commands REQUEST SENSE Command (03h) (continued) Table 5–87 REQUEST SENSE Data — Field Descriptions (continued) Field Name Description 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.
PAGE 336
SCSI Commands REQUEST SENSE Command (03h) (continued) Table 5–87 REQUEST SENSE Data — Field Descriptions (continued) Field Name Description 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).
PAGE 337
SCSI Commands REQUEST SENSE Command (03h) (continued) Table 5–88 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.
PAGE 338
SCSI Commands REQUEST SENSE Command (03h) (continued) The following table provides the additional sense codes (ASCs) and additional sense code qualifiers (ASCQs) that may be reported. Additional information, explanations, or suggestions for action are included in some of the descriptions.
PAGE 339
SCSI Commands REQUEST SENSE Command (03h) (continued) Table 5–89 Supported ASC / ASCQ in Hex (continued) Sense Key 02h NOT READY 03h MEDIUM ERROR ASC ASCQ Meaning 04 00 Unit Not Ready, Cause Non-reportable 04 01 Unit Not Ready, Calibration in Process 04 02 Unit Not Ready, LOAD Command Needed 04 03 Unit Not Ready, Manual Intervention Needed 30 02 Incompatible Format 30 03 Unit Not Ready, Incompatible Medium (Cleaning Cartridge) Installed 3A 00 Medium Not Present 3A 80 Medium Not
PAGE 340
SCSI Commands REQUEST SENSE Command (03h) (continued) Table 5–89 Supported ASC / ASCQ in Hex (continued) Sense Key 04h HARDWARE ERROR ASC ASCQ Meaning 08 00 LUN Communication Failure 08 01 LUN Communication Timeout Failure 0C 80 Write SCSI FIFO CRC Error 11 80 Read SCSI FIFO CRC error 11 81 Block port detected EDC error 11 82 Block port detected record CRC error 15 01 Random Mechanical Positioning Error 21 01 Invalid Element Address 3B 08 Repositioning Error 3B 0D Media Des
PAGE 341
SCSI Commands REQUEST SENSE Command (03h) (continued) Table 5–89 Supported ASC / ASCQ in Hex (continued) Sense Key 04h HARDWARE ERROR 05h ILLEGAL REQUEST ASC ASCQ Meaning (cont.
PAGE 342
SCSI Commands REQUEST SENSE Command (03h) (continued) Table 5–89 Supported ASC / ASCQ in Hex (continued) Sense Key 05h ILLEGAL REQUEST 06h UNIT ATTENTION 07h DATA PROTECTED 08h BLANK CHECK 09h VENDOR UNIQUE ASC ASCQ Meaning (cont.
PAGE 343
SCSI Commands REQUEST SENSE Command (03h) (continued) Table 5–89 Supported ASC / ASCQ in Hex (continued) Sense Key 0Bh COMMAND ABORTED ASC ASCQ Meaning 43 00 Message Error 44 80 Unexpected Selection Interrupt 44 82 Command Complete Sequence Failure 44 83 SCSI Chip, Gross Error/ Illegal – Command Status 44 84 Unexpected/Unexplained Residue Count in Transfer Register 44 87 Disconnect Sequence Failed 44 89 Internal Target Failure 45 00 Select/Reselect Failure 47 00 SCSI Parity Er
PAGE 344
SCSI Commands 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 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: 5-200 • Filemark, EOM, ILI bit may be set to 1 with No Sense key (00h) and ASC / ASCQ = 00 00.
PAGE 345
SCSI Commands 5.24 RESERVE UNIT (6) Command (16h) The RESERVE UNIT (6) command is a 6-byte command that reserves the specified tape drive for exclusive use by the requesting initiator or for another specified SCSI device.
PAGE 346
SCSI Commands RESERVE UNIT (6) Command (16h) (continued) Table 5–90 RESERVE UNIT (6) Command Data — Field Descriptions Field Name Description 3rdPty The third party reservation option for RESERVE UNIT (6) 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.
PAGE 347
SCSI Commands RESERVE UNIT (6) Command (16h) (continued) An initiator that holds a current reservation may modify that reservation (for example, to switch third parties) by issuing another RESERVE UNIT (6) command to the tape drive. Medium Changer Considerations for RESERVE UNIT (6) Command The optional Element Reservation feature defined for Medium Change devices as described in the ANSI SCSI-2 specification is not supported. The RESERVE UNIT command is defined the same as for the tape drive.
PAGE 348
SCSI Commands 5.25 RESERVE UNIT (10) Command (56h) The RESERVE UNIT and the RELEASE UNIT commands are used for contention resolution in multiple-initiator systems. The RESERVE UNIT (10) command is a 10-byte command that is used to reserve a logical unit. The RESERVE UNIT (10) Command Descriptor Block is shown in Figure 5-92, and the data fields are described in Table 5-91. If RESERVE UNIT (10) is used, then RELEASE UNIT (10) is also used.
PAGE 349
SCSI Commands RESERVE UNIT (10) Command (56h) (continued) Table 5–91 RESERVE UNIT (10) Command — Field Descriptions Field 3rd Pty LongID Description When set to 1, it indicates that the Third Party Device ID field is valid. When 0, indicates that the third party device associated with the reservation release has a number smaller than 255 and the ID value can be sent within the CDB.
PAGE 350
SCSI Commands RESERVE (10) Command (56h) (continued) Table 5–91 RESERVE UNIT (10) Command — Field Descriptions (continued) Field Extent Description If 0, requests that the entire logical unit be reserved for use only by the initiator until the request is supplanted by another valid RESERVE command from the same initiator, or until released via a RELEASE (10) command from the reserving initiator, a hard reset, or a power on cycle. If set = 1, the extent reservation option is implemented.
PAGE 351
SCSI Commands RESERVE UNIT (10) Command (56h) (continued) RelAdr is always 0: The DLT 8000 tape drive does not support relative addressing. The Reservation Type field defines the type of reservation in effect for the extent being reserved. Available types of reservations are shown below. Table 5–92 Reservation Types Reservation Type Description 00b READ shared. No write operations are permitted by any initiator to the reserved extent. Any initiator may read from the extent. 01b WRITE exclusive.
PAGE 352
SCSI Commands RESERVE UNIT (10) Command (56h) (continued) If the LongID bit = 1 and the Extent bit = 0, then the parameter list length is eight and the parameter list has the format shown below.
PAGE 353
SCSI Commands 5.26 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.
PAGE 354
SCSI Commands 5.27 SEND DIAGNOSTIC Command (1Dh) The SEND DIAGNOSTIC command directs the tape drive to perform its self-diagnostic tests. It can also be used to invoke the Basic Health Check (BHC) diagnostic test. Note that the BHC feature is provided for use only by a trained service provider.
PAGE 355
SCSI Commands SEND DIAGNOSTIC Command (1Dh) (continued) Two levels 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 power-up self tests that are run.
PAGE 356
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–95 SEND DIAGNOSTIC CDB Bits Selftst, DevOfl, and UnitOfl Selftst DevOfl UnitOfl 0 0 0 Illegal Combination 0 0 1 Self-Test Level 3 with User Parameters 0 1 0 Illegal Combination 0 1 1 Self-Test Level 2 with Default Parameters or BHC Test 1 0 0 Self-Test Level 1 with Defa
PAGE 357
SCSI Commands SEND DIAGNOSTIC Command (1Dh) (continued) Table 5–96 SEND DIAGNOSTIC Parameter List — Field Descriptions Field Name Description Pattern Number Indicates the type of data pattern to be used during the diagnostic test. Pattern Name Data in Hex 0h Rotate Rotate through the other 9 patterns; change for each tape file.
PAGE 358
SCSI Commands SEND DIAGNOSTIC Command (1Dh) (continued) Table 5–96 SEND DIAGNOSTIC Parameter List — Field Descriptions (continued) Field Name Description 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: 1. Write tracks 0, 1, 2 2. REWIND, READ, and VERIFY tracks 0, 1, 2 3.
PAGE 359
SCSI Commands SEND DIAGNOSTIC Command (1Dh) (continued) 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–97 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. Additional Sense Code for possible additional information. 4h Hardware Error.
PAGE 360
SCSI Commands 5.28 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. Note that the DLT 8000 tape system is a single partition device.
PAGE 361
SCSI Commands SPACE Command (11h) (continued) Table 5–99 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.
PAGE 362
SCSI Commands 5.29 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.
PAGE 363
SCSI Commands 5.30 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.
PAGE 364
SCSI Commands 5.31 WRITE Command (0Ah) The WRITE command transfers one or more blocks from the host to the current logical position. When in Buffered Mode (see MODE SELECT), the tape drive reports GOOD status on WRITE commands as soon as this data block has been transferred to the data buffer.
PAGE 365
SCSI Commands WRITE Command (0Ah) (continued) Table 5–101 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.
PAGE 366
SCSI Commands WRITE Command (0Ah) (continued) 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.
PAGE 367
SCSI Commands 5.32 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 DLTtape microcode (firmware).
PAGE 368
SCSI Commands WRITE BUFFER Command (3Bh) (continued) Table 5–102 WRITE BUFFER Command Data — Field Descriptions (continued) Field Name Description 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.32.1 through 5.32.4 for the appropriate settings. 5.32.
PAGE 369
SCSI Commands WRITE BUFFER Command (3Bh) (continued) 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 8K bytes.
PAGE 370
SCSI Commands 5.33 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.
PAGE 371
SCSI Commands WRITE FILEMARKS Command (10h) (continued) Table 5–103 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).
PAGE 372
PAGE 373
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.
PAGE 374
Appendix A: Definition of Vendor Unique Sense Data Information Table A–1 Internal Status Codes (continued) A-2 Decimal Hexadecimal Description 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
PAGE 375
Appendix A: Definition of Vendor Unique Sense Data Information Table A–1 Internal Status Codes (continued) Decimal 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 Hexadecimal 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 Description Invalid Destination Slot Source Slot Empty Destination Slot Full Medium Changer Motion Error Medium Changer/Drive Interface Error Medium Changer/Slot Interface Error Medium Changer Mechanical Error Medium Changer Hardware Error Medium Changer Controller Error Unrecognized Me
PAGE 376
Appendix A: Definition of Vendor Unique Sense Data Information A-4 Quantum DLT 8000 Tape System
PAGE 377
Appendix B EEPROM-RESIDENT BUGCHECK AND EVENT LOGS This appendix provides an explanation of the event logs (information packets) stored in semi-permanent, 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.
PAGE 378
Appendix B: EEPROM-Resident Bugcheck and Event Logs B.2 Bugcheck Packets Bugchecks are the result of some firmware-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. The most important information within the packet is the error code. The more common bugcheck codes are listed in Table B—1.
PAGE 379
Appendix B: EEPROM-Resident Bugcheck and Event Logs 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.2 Event Log Packets Event log packets are non-fatal and can occur to log information about significant events.
PAGE 380
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. 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.
PAGE 381
Appendix C UPDATING THE FIRMWARE This appendix explains how to update the tape system’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 If a powerfail occurs during the firmware update process (when the new image is actually being programmed into the FLASH EPROM’s), the tape drive’s PCBA will be rendered unusable.
PAGE 382
Appendix C: Updating the Firmware NOTE 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 it 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 an appropriate block size as shown in Table D-1, that is, dd, ltf, and so on. The tape must be uncompressed.
PAGE 383
Appendix C: Updating the Firmware NOTE If the WRITE PROTECTED indicator does not blink, check that: 1. POST 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 PROTECTED indicators will blink. This indicates that the tape drive recognizes that the firmware update mode has been selected.
PAGE 384
Appendix C: Updating the Firmware 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 PROTECTED and TAPE IN USE indicators flash again during the controller firmware update. C.
PAGE 385
Appendix C: Updating the Firmware Table C—2 Results of Firmware Update (continued) If... Then... 1. The tape is NOT a valid firmware update tape No firmware update is attempted. The WRITE PROTECTED and TAPE IN USE indicators do not blink. The drive resets and the tape remains loaded to signal that the firmware update was unsuccessful. 2.
PAGE 386
Appendix C: Updating the Firmware C-6 Quantum DLT 8000 Tape System
PAGE 387
Appendix D RUNNING THE BASIC HEALTH CHECK (BHC) TEST VIA THE LIBRARY PORT This appendix explains how to run the DLT 8000 tape system’s BHC test on a tape drive that is configured as a component within a library. NOTE The BHC feature is provided for use only by a trained service provider. Issue the RUN BHC TEST command (15h) to the tape drive configured within the library. For the results of the BHC test, obtain Tape Data Packet 3 by issuing a SEND TAPE DATA 3 command (13h).
PAGE 388
Appendix D: Running the Basic Health Check (BHC) Test Via the Library Port D-2 Quantum DLT 8000 Tape System
PAGE 389
Appendix E VISUAL INSPECTION PROCEDURE FOR DLTtape CARTRIDGES This appendix explains how to visually inspect a DLTtape Cartridge. Damaged cartridges must not be used. DLTtape CARTRIDGE GENERAL 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.
PAGE 390
Appendix E: Visual Inspection Procedure for DLTtape Cartridges • 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.
PAGE 391
Appendix E: Visual Inspection Procedure for DLTtape Cartridges Reel Lock Opening Figure E-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. 5.
PAGE 392
Appendix E: Visual Inspection Procedure for DLTtape Cartridges Spring-Loaded Hub Reel Lock Opening Figure E-2 Location of Reel Lock Opening and Spring-Loaded Hub on Bottom of DLTtape Cartridge Check the opening indicated in Figure E-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.
PAGE 393
Appendix E: Visual Inspection Procedure for DLTtape Cartridges 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 E-3. Leader Loop Figure E-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 E-3.
PAGE 394
Appendix E: Visual Inspection Procedure for DLTtape Cartridges 7. Figure 4 shows three different tape cartridge loop problems. No tape cartridge that exhibits the problems shown in the examples in Figure E-4 should be used in a DLT tape system.
PAGE 395
Appendix E: Visual Inspection Procedure for DLTtape Cartridges 8. Finally, check for proper operation of the tape cartridge’s Write Protect Switch (Figure E-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).
PAGE 396
Appendix E: Visual Inspection Procedure for DLTtape Cartridges E-8 Quantum DLT 8000 Tape System
PAGE 397
Appendix F TIMEOUT SPECIFICATIONS FOR DLT 8000 TAPE SYSTEM SCSI COMMANDS This appendix provides the timeout specifications for the SCSI commands supported by the DLT 8000 tape system.
PAGE 398
Appendix F: Timeout Specifications for DLT 8000 Tape System SCSI Commands F-2 Quantum DLT 8000 Tape System
PAGE 399
Appendix G DLT 7000 EMULATION FEATURE This appendix provides information about using the DLT 7000 emulation feature on a DLT 8000 tape drive. It includes information about what the feature is, compares the feature with actual DLT 7000 tape drive capability, and explains how to enable the emulation feature. DLT 7000 emulation is a feature that has been included in the DLT 8000 tape drive’s firmware.
PAGE 400
Appendix G: DLT 7000 Emulation Feature Enabling and Clearing the DLT 7000 Emulation Feature CAUTION Use Extreme Caution when enabling the DLT 7000 emulation feature: the DLT 7000 emulation mode changes the operation of the tape drive and fundamentally changes the way data and media are handled. 1. 2. G-2 • Do NOT enable/clear the DLT 7000 emulation feature with a tape cartridge loaded in the tape drive. • Do NOT enable/clear the DLT 7000 emulation feature while the drive is in operation.
PAGE 401
Appendix G: DLT 7000 Emulation Feature What You Should Know About the DLT 7000 Emulation Feature A DLT 8000 tape system running with DLT 7000 emulation enabled does not “become” a DLT 7000 system, nor does it retain all of the features of a DLT 8000 system. Here are the differences: 1. A DLT 8000 tape drive with DLT 7000 emulation enabled has the capability of writing and reading 10 GB, 15 GB, 20 GB and 35 GB formats. It will not support the 2.6 GB and 6.
PAGE 402
Appendix G: DLT 7000 Emulation Feature Verifying Product Family via the SCSI Bus You can verify a DLTtape system’s product family via the SCSI Bus. The following table describes the information returned by the SCSI command INQUIRY. The contents of the Product Family bits (byte 4, bits 4 – 7) of the INQUIRY command’s Subsystem Components Revision Page (C1h). A DLT 8000 running with DLT 7000 emulation enabled will return a Product Family code of 09h.
PAGE 403
Appendix G: DLT 7000 Emulation Feature SCSI Bus Differences The table below illustrates the SCSI bus differences between a DLT 7000 system, a DLT 8000 system, and a DLT 8000 system with DLT 7000 emulation enabled. SCSI opcodes that exist for a DLT 7000 drive will have an identical response on a DLT 8000 drive with emulation enabled. Note that SCSI opcodes that are not compatible with a “real” DLT 7000 drive are supported by a DLT 8000 drive in DLT 7000 emulation mode.
PAGE 404
Appendix G: DLT 7000 Emulation Feature DLT 7000 Drive DLT 8000 Drive DLT 8000 Drive with DLT 7000 Emulation Enabled MODE SELECT Command Density Code Field 0x00 Default 0x17 2.6 GB 0x18 6.
PAGE 405
Appendix G: DLT 7000 Emulation Feature DLT 7000 Drive Page C1h • Vendor Unique DLT 8000 Drive DLT 8000 Drive with DLT 7000 Emulation Enabled DLT 7000 Format Support DLT 8000 Format Support DLT 8000 Format Support (Product Family 0x09) READ POSITION Command • Long Format Bit Not supported Supported Supported SEND DIAGNOSTIC Command • Run Basic Health Check (BHC) Pattern Number Not supported Supported Supported Detailed Unit Attention ASCQs for Resets Not supported Supported Supported Front
PAGE 406
Appendix G: DLT 7000 Emulation Feature G-8 Quantum DLT 8000 Tape System
PAGE 407
PAGE 408
*81-60118-04 A01* 81-60118-04 A01 501 Sycamore Drive Milpitas, CA 95035 (408) 894-4000 www.quantum.