HP Q153090901 User Manual

HP Ultrium tape drives Technical reference manual

Generation 3 drives

Volume 3—the SCSI interface

Part Number: Q15 30–90901 Volume 3 Edition 6, December 2004

Legal and notice information

Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantab ility and fitness for a parti c u l ar purp ose. Hewlett -Packard shall not be liable for errors contained herein or direct,

indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this document. This document contains proprietary information which is protected by copyright. All rights reserved. No part of this document may

be photocopied, reproduced or translated to another language without the prior written consent of Hewlett-Packard.

Revision history

Version Date Changes

Edition 1 Nov. 2000 All Edition 2 Mar. 2001 Addition of Read and Write attribute commands and Drive Error Codes Edition 3 May 2002 Inclusion of the Request Block Address command and the Control mode page, together

with numerous small changes Edition 5 July 2003 Many small changes Edition 6 December 2004 Generation 3 version

This document is frequently revised and updated. To find out if there is a later version, please ask your HP OEM Representative.

Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Documents specific to HP Ultrium drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Documentation map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

General documents and standardization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1 Interface Implementation

The SCSI interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Supported messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Supported commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

SCSI features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Design approach. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Power-on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Reset strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Abort handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

LUN identification

Bus parity or CRC errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Disconnect strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Multi-initiator support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Fibre Channel operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Fibre Channel addressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Field replaceable units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

CD-ROM emulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

(parallel SCS I only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Contents

2Messages

Message Out support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Message In support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Extended Message support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3 Commands—introduction

Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Command details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Pre-execution checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Bad LUN check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Deferred Error check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Diagnostic Status check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Fixed Bit check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Flag Link check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Contents

Illegal Command check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Illegal Field/Request check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Media Access check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Media Information check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Media Write check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Parameter List check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Reservation check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Unit Attention check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Command descriptor block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4Commands

ERASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19h 38

INQUIRY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12h 39

INQUIRY data pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Vital Product Data pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Supported Vital Product Data Pages page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Unit Serial Number page 45

Device Identification page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Defined identifiers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Extended INQUIRY Data VPD page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Sequential Access Device Capabilities page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Drive Component Revision Levels pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

LOAD/UNLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Bh 50

LOCATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Bh 53

LOG SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Ch 55

LOG SENSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Dh 57

Log page format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Supported Log Pages page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Write Error Counters log page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Read Error Counters log page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Sequential Access Device log page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Temperature log page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

DTD Status log page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Very High Frequency Data (VHF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Very High Frequency Polling Delay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

DTD Primary Port Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

TapeAlert log page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Tape Usage log page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Tape Capacity log page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Data Compression log page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Performance Data log page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Device Status log page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

MODE SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15h/55h 71

Mode parameter pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Mode page representation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Mode data format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Mode block descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4Contents

Read-Write Error Recovery mode page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Disconnect-Reconnect page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

SCSI drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Control mode page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Data Compression Characteristics page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Device Configuration page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Medium Partitions mode page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Fibre Channel Logical Unit Control mode page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

SCSI LUN Control mode page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Fibre Channel Port Control mode page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

SCSI Port Control Mode page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Normal page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Sub-pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Information Exceptions mode page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Device Time mode page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

CD-ROM Emulation/Disaster Recovery mode page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

MODE SENSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Ah/5Ah 96

PERSISTENT RESERVE IN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Eh 98

PERSISTENT RESERVE OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Fh 101

Additional parameter data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

PREVENT/ALLOW MEDIUM REMOVAL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Eh 105

READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 08h 106

READ 6 READ 10

(CD-ROM mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 08h 109

(CD-ROM mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28h 110

READ ATTRIBUTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Ch 111

MAM attribute data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Attribute ID values 116

Standard device type attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Standard medium type attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Standard host type attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

READ BLOCK LIMITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .05h 120

READ BUFFER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Ch 121

READ CAPACITY

(CD-ROM mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25h 124

Read Capacity data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

READ MEDIA SERIAL NUMBER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ABh 125

READ POSITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34h 127

READ TOC

(CD-ROM mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43h 131

Read TOC data 132

RECEIVE DIAGNOSTICS RESULTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Ch 133

RELEASE UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 7h/57h 135

REPORT DENSITY SUPPORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44h 137

REPORT DEVICE IDENTIFIER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A3h 140

REPORT LUNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A0h 141

REPORT SUPPORTED OPCODES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A0h 143

REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS . . . . . . . . . . . . . . . . . . . . . A3h 145

REQUEST SENSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .03h 147

Request Sense data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Contents

Fixed format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Descriptor format 152

Sense data management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Current sense. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

UNIT ATTENTION sense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

DEFERRED ERROR sense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Sense keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Additional Sense codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Error codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

RESERVE UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16h/56h 164

REWIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .01h 166

SEEK

(CD-ROM mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Bh 167

SEND DIAGNOSTIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Dh 168

Standard self-test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

SET CAPACITY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0Bh 170

SET DEVICE IDENTIFIER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A4h 171

SPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11h 172

START/STOP

TEST UNIT READY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .00h 176

VERIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13h 177

WRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0Ah 178

WRITE ATTRIBUTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Dh 180

WRITE BUFFER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Bh 183

WRITE FILEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10h 186

(CD-ROM mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Bh 175

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191

6Contents

Rel ated documents

This is one of six volumes that document HP Ultrium drives. This volume provides background information f or dri v er and applicati on dev eloper s. T he follo w ing doc uments pr ov i de additional information:

Documents specific to HP Ultrium drives

• Hardware Integration Guide, volume 1 of the HP Ultrium Technical Reference Manual

• Software Integration Guide, volume 2 of the HP Ultrium Technical Reference Manual

• Specifications, volume 4 of the HP Ultrium Technical Re f e rence Manual

• HP Ultrium Configuration Guide, volume 5 of the HP Ultrium Technical Reference Manual

• Background to Ultrium Drives, volume 6 of the HP Ultrium Technical Reference Manual

• HP Ultrium Technology White Paper, which describes the features and benefi ts of

HP Ultrium drives

Please contact your HP supplier for copies.

Documentation map

The following will help you locate information in the 6-volume Technical Reference Manual:

Drives—general

Connectors 1 HW Integration: ch. 7 1 HW Integr ation: ch. 4 Controller architecture 6 Background: ch. 4 Front Panel LEDs 1 HW Integration: ch. 6 1 HW Integr ation: ch. 3 Mechanism and hardware 6 Background: ch. 3 Specifications 4 Specs

SCSI Drives FC Drives

Installation and configuration

SCSI Drives FC Drives

Connectors 1 HW Integration: ch. 7 1 HW Integration: ch. 4 Determining the configuration 2 SW Integratio n: ch. 2 2 SW Integration: ch. 2 External drives (SCSI only) 1 HW Integration: ch. 5n/a In Libraries 1 HW Inte gration: ch. 1 In Servers (SCSI only) 1 HW Integration: ch. 4n/a In Tape Arrays (SCSI only) 1 HW Integration: ch. 3n/a Modes of Usage (SCSI only) 1 HW Integration: ch. 8n/a

General documents and standardization

• Enhanced Small Computer Sy stem Interface (SCS I- 2), ANSI X3T9.2-1993 Rev. 10L,

available through ANSI

• See http://www.t10.org/t10_main.htm

for ANSI SCSI-3 and other specific ations

Copies of documents of other standards bodies can be obtained from:

ANSI

11 West 42nd Street New York, NY 10036-8002 USA

ISO

CP 56 CH-1211 Geneva 20 Switzerland

ECMA

114 Rue du Rhône

Tel: +41 22 849 6000

CH-1204 Geneva

Web URL: http://www.ecma.ch Tel: 800 854 7179 or 714 261 1455

Global Engineering Documents

Switzerland 2805 McGaw

Irvine, CA 92714 USA

1 Interface Imp lementation

HP Ultrium drives use SCSI-3 as the interface to connect to the host system. This chapter gives an overview of how the interface operates.

Full details of the messages are given in Chapter 2 and of commands in Chapter 3 and

Chapter 4.

The SCSI interface

The Small Computer System Interface (SCSI) is an industry standard, approved by the American National Standards Institute (ANSI). You are recommended to read the ANSI standard document in conjunction with this manual. The ANSI specification defines the interface in general while this document describes the HP Ultrium implementation.

The SCSI implementation provides a drive with a standard set of features and functions. These include the following:

• Synchronous data transfers

• Asynchronous data transfers

• Implementation of all mandatory and most optional commands of the Sequential Access

command set

• LVD (Low-Voltage differential) SCSI connectio n

• Ultra-320 wide SCSI

• Conformance to the following SCSI standards:

• SAM-2 ANSI INCITS .366:2003

• SPI-4 ANSI INCITS.362:2002

•SPC3

• SS C -2 ANSI INCITS.380:2003

Supported messages

The following messages are supported by the drives:

• ABORT

• BUS DEVICE RESET

• COMMAND COMPLETE

Interface Implementation

The SCSI interface

• DISCONNECT

• IDENTIFY

• IG NORE WIDE RESIDUE

• INITIATOR DETECTED ERROR

• MESSAGE PARI TY E RROR

• MESSAGE REJECT

• NO-OP (no operation)

• PARALLEL PROTOCOL REQUEST (PPR)

• RESTORE POINTERS

• SAVE DATA POINTER

• SYNCHRONOUS DATA TRANSFER REQUEST

• WIDE DATA TRANSFER REQUEST

For implementation details on these messages, see Chapter 2, “Messages”

Supported commands

The following commands are supported by the drives. They include all Mandatory and Extended commands and most Optional commands.

19h ERASE 03h REQUEST SENSE 12h INQUIRY 44h REPORT DENSITY SUPPORT 1Bh LOAD/UNLOAD A3h (05h) REPORT DEVICE IDENTIFIER 2Bh LOCATE A0h REPOR T LUNS 4Ch LOG SELECT A3h (0Ch) REPORT SUPPORTED OP CODES 4Dh LOG SENSE A3h (0Dh) REPORT SUPPORTED TASK MNGMNT FUNCTNS

15h/55h MODE SELECT 56h/16h RESERVE UNIT

1Ah/5Ah MODE SENSE 01h REWIND

5Eh PERSISTENT RESERVE IN 1Dh SEND DIAGNOSTIC 5Fh PERSISTENT RESERVE OUT 0Bh SET CAPACITY 1Eh PREVENT/ALLOW MEDIUM REMOVAL A4h (06h) SET DEVICE IDENTIFIER 08h READ 11h SPACE 8Ch READ ATTRIBUTE 00h TEST UNIT READY 05h READ BLOCK LIMITS 13h VERIFY 3Ch READ BUFFER 0Ah WRITE

ABh (01h) READ MEDIA SERIAL NUMBER 8Dh WRITE ATTRIBUTE

34h READ POSITION 3Bh WRITE BUFFER 1Ch RECEIVE DIAGNOSTIC RESULTS 10h WRITE FILEMARK S

57h/17h RELEASE UNIT

Interface Implementation12

The following additional commands are supported for CD-ROM mode:

08h READ 6 43h READ TOC 28h READ 10 2Bh SEEK 25h READ CAPACITY 1Bh START/STOP UNIT

For implementation details on these commands, see Chapter 3, “Commands—introduction” and

Chapter 4, “Commands”.

SCSI f eatures

Design approach

The features supported b y the dri v e are ba sed on standar ds, both off ici al and de fact o. T he dri ve is fully compliant with the current SCSI standards: SPC3, SSC2, SAM2, and the relevant transport protocol (e.g. SPI4 for the parallel SCSI drive). All mandatory commands and features are supported, as well as some that are optional. In addition, some features from older standards are still supported for backwards compatibility.

Power-on

The drive will respond to INQUIRY, TEST UNI T READY, REP OR T L UN S and RE QUEST SENSE commands within 250 ms of power on. The first command received from an initiator (other than

REQUES T SE NSE) w ill r e sult in CHECK CONDITION status, with UNIT ATTENTION sense data reported

for the power on. Once the drive has completed its self-test and set-up procedures, it will attempt to reload any tape that is already present in the drive. It may take some time to recover the tape, especially if it wa s po sitioned near EO M when power was cy cl ed . Dur ing ta pe recovery, medium access commands will result in a sense key of in process of becoming ready).

Reset strategy

The drive supports reset as follows:

• The current I/O process is aborted

• Any queued I/O processes from other initiators are removed

• All negotiated settings are cleare d

• Mode parameters are cleared to their default values

• Any reservations are cleared (but not persistent reservations)

• Any buffered writes are flushed to tape

• The logical position becomes undefined, unless Rewind-On-Reset has been configured in

which case the drive will rewind to BOM

INQUIRY and

Interface Implementation

NOT READY, with additional sense of 0401h (drive

(parallel SCSI drives only)

SCSI features

• A UNIT ATTENTION condition is set, based on the type of reset

The drive will respond to 250 ms of the re set line being r elea sed. Th e fir st command f r om any initia tor (other than

REQUEST SENSE and REPORT LUNS) will result in CHECK CONDITION status with UNIT ATTENT ION

sense data for the reset. Note that all commands will receive completed its internal reset.

The Reset button on the front panel and the ACI_R ESET_L line on the Automation Controller Interface are both connected to the Power-Up Reset interrupt on the processor. The effect is equivalent to power-cycling the drive. The contents of the tape and cartridge memory may not be consistent after the action and any data in the drive buffer will be lost.

Abort handling

If an abort condition is detected before a command phase completes, the bus is set to bus fr ee and the command is not executed.

If an abort condition is detected between the end of the command phase and the start of the status phase, the bus is set to bus free and the processing below is carried out.

If an abort condition is detected during status phase, the bus is set to bus free. If a command (other than

abort but before the drive is ready to process the command, the behavior depends on whether Disconnects are allowed.

• If disconnects are allo w ed, the dri v e w ill disconnect and w ait un til the abort pr ocessing has

completed before executing the command.

INQUIRY, TEST UNIT READY, REPORT LUNS and REQUEST SENSE within

INQUIRY,

BUSY status until the drive has

INQUIRY for standard data or REQUEST SENSE) is received after the

• If disconnects are not allow e d, a

Command Abort Processing

ERASE Long erase is aborted as quickly as possible without corrupting the tape

format. Short erase completes.

INQUIRY None LOAD/UNLOAD Load completes and logically positions the tape at BOT.

Unload is aborted leaving the logical position at BO T unless the operation is past the “point of no return” in which case the tape is eject ed.

LOCATE The logical position is set back to that at the start of the operation. LOG SELECT If data transfer is complete, the command is completed, otherwise no action

is taken

LOG SENSE None MODE SELECT If data transfer is complete, the command is completed, otherwise no action

is taken.

MODE SENSE None

Interface Implementation14

BUSY response will be returned.

Command Abort Processing

PREVENT/ALLOW MEDIUM REMOVAL

READ The logical position is set to that at the start of the operation. READ BLOCK LIMITS None READ BUFFER None READ POSITION None RECEIVE DIAGNOSTICS

RESULTS RELEASE UNIT The command completes. REQUEST SENSE Sense data is discarded. RESERVE UNI T The command completes. REWIND The command completes. SEND DIAGNOSTIC If data transfer is complete, the command is completed, otherwise no action

SPACE The logical position is set back to that at the start of the operatio n. TEST UNIT READY None WRITE The logical position is set back to that at the start of the operation. WRITE BUFFER If data transfer is complete, the command is completed, otherwise no action

The command completes.

None

is taken

is taken.

Interface Implementation

WRITE FILEMARKS The logical position is set back to that at the start of the operation VERIFY The logical position is set back to that at the start of the operation

LUN identification (parallel SCSI only)

Identify messages are used to identify the LUN being addressed by the initiator, and to identify which LUN is reselecting the initiator. The old LUN field in the CDB from the SCSI-2 standards is obsolete and should not be used (set to 0).

Bus parity or CRC errors

If the drive detects a bus parity error in a message out or command phase, it will still accept the command, which will then return error). Detection of a parity error during the data out phas e also causes the drive to r e turn

CONDITION

. Additional sense is set to 4701h (data phase CRC error detected) if the bus is in DT

mode or 4700h if not.

CHECK CONDITION. Additional sense is 4700h (SCSI parity

SCSI features

CHECK

If Information Units is enabled (parallel SCSI only), the dri ve will drop the bus on detecting a CRC error during a LQ_IU. If the CRC error occurs during the Information Units command phase or data out phase, the driv e will return 4703h (Information Unit CRC error detected).

CHECK CONDITION with a CRC error. Additional sense is set t o

On detecting an Initiator Detected error, the drive will return sense of 4800h (initator detect ed error message received). The exception is when Information Units mode is enabled (parallel SCSI only), when one of the following occurs:

• If an IDE message is received dur ing a LQ_IU, the dri ve dr ops the bus and retr ies the LQ_IU

pair.

• If the message is received dur i ng Status IU, the dri ve retries the LQ_Status pair.

• If the message is received during Data IU, the drive sends a LQ_Status with

CONDITION

and additional sense of 4800h.

Disconnect strategy

The disconnect strategy used by the drive is based on maximizing the use of the bus for large sequential data transfers from a large data buffer. The drive will disconnect whenever it believes that it will provide better bus use. This may be between command and data phases, between bursts of data or before sending status. However, the drive will guarantee that it sends the configured maximum burst size or the remaining data in the transfer in any single data phase burst if the maximum burst size has been set to a value other than zero.

The following diagram gives an overview of the drive’s disconnect strategy:

CHECK CONDITION with additional

CHECK

Interface Implementation16

CDB arrives

Yes

REQUEST SENSE from

an initiator in CA or

INQUIR Y w ith EVP D=0

Disconnect

priv granted

Yes

DisconnectSend data

Reselect

Data transfer

required?

Yes

ReselectExecu te cmd

Transfer data &

execute c md

Previous cmd

still in progress?

Yes

Interface Implementation

Send status

Cmd complete Cmd comp le te

Multi-initiator support

All drives are design to operate within a multi-initiator environment. The maximum number of concurrently connected initiators is as follows:

•

Parallel SCSI drives: up to 15 initiators

•

Fibre Channel drives: up to 32 initiators shared across both ports

Send status

Cmd complete

Send BUSY

status

SCSI features

Sense Data, Unit Attention and Deferred Errors are maintained for each initiator. Mode Parameters are common to all initiators.

The untagged queuing model implemented by the drives guarantees that all commands are executed in strict order of receipt. Certain non-media access type commands, such as

READY

, INQUIRY, REQUEST SENS E and REPORT LUNS, are implicitly allowed to queue-jump other

media access type commands, such as The parallel SCSI drive supports the full command queuing model with a queue depth of 1

(necessary for connectivity purposes). The FC drive supports the basic queuing model with a queue depth of 4. See “Standard Inquiry Data format (LUN0)” on page 40 for details of the BQue and CmdQue bits which define this support.

REWIND.

Fibre Channel operation

NOTE: This applies only to Fibr e Channel dr ives.

The following sections have information specific to Fibre Channel operation:

• “Fibre Channel Logical Unit Control mode page” on page 84

• “Fibre Channel Port Control mode page” on page 85

• “Vital Product Data pages” on page 44

TEST UNIT

Fibre Channel addressing

Before describing HP’s implementation of Fibre Channel addressing, the concepts of Names and Addresses need to be clarified.

Names

Names are 64-bit identifiers assigned permanently to the tape dr iv e during manufactur e. T hey ar e commonly referred to as World Wide Names since they must be guaranteed unique. The names are typically used for identifying the device to operating systems, since addresses are assigned dynamically. There at least eight different name formats distinguished by the Network Address Authority (NAA). Only one is used on HP Ultrium drives. This is the IEEE Registered Name (NNA=5) and has the following format:

This name is made up of three fields:

• NAA Identifier (4 bits). “5” indicates a IEEE Registered Name.

Interface Implementation18

• IEEE Company ID (24 bits). Assigned by IEEE to the company.

• Vendor Specified ID (36 bits). Assigned by the company.

Addresses

Each Fibre Channel port also has a Port Address which is assigned during loop initialization and/or Fabric Login. This is a 24-bit value in the following format:

The AL_PA is the Arbitrated Loop Physical Address. This is normally assigned dynamically during loop initialization.

If the loop is not attached to a fabric (in other words, when it is private,) the top two bytes will be zero. If the loop is attached to a fabric, the tape drive is assigned the top two bytes when it logs into the fabric.

Together, the three bytes provide a unique address on the Fibre Channel fabric that is used for frame addressing. It forms the equivalent of the Target ID or Initiator ID in SCSI.

HP’s implementation of names and addresses

The HP implementation uses three adjacent IEEE Registered Names:

• The first (last bits = 00) is used as the Port A World Wide Name.

• The second (last bits = 01) is used as the Port B Wor ld W ide Name.

• The third name (last bits = 10) is used for the Device World Wide Name.

(These are assigned during manufacture from HP’s pool of names, although only the first will actually be stored in the drive NV-RAM).

The port addresses will be assigned using the ‘standard’ AL_PA initialization mechanisms. The ‘Fibre Channel Port Control mode page’ controls this. The drive has the ability to support hard addresses as part of this scheme.

Interface Implementation

Fibre Channel operation

The values of the names can be obtained using the Device Identification Vital Product Information Page (part of the

INQUIRY command).

Implications for libraries

• Normally a standalone drive will operate using its own ‘hard’ names.

• The drive knows it is in a library or other ‘managed’ environment since one of the signal

lines on the ACI (Automation Control Interface) will be tied dow n.

In this case, the drive will not go on the FC loop until it is told to. The library can optionally download a new, soft base name (Port A/Device Name) into the drive at this point. The drive will then use this as the origin of its names. The library manufacturer would be responsible for obtaining this IEEE Registered Name. It would be a property of the library, not the drive.

• If the library wants to ‘warm swap’ drives, it can. It just ‘tur ns off’ the drive with the soft

name using the ACI and then turns on the spare drive, downloading the same name to it.

• If a drive is removed from the library, it will not have the ACI signal tied low and so will

revert to its original hard name. It should forget the soft name in this case.

• If the library controller breaks , the dri ve w ill time out the A CI interf ace in ~10 seconds. The

drive still knows it is in a library since the ACI signal is still tied low, so in this case it will use the soft name last downloaded. This will allow drive access without confusing the host.

Field replaceable units

An FRU code identifies which part of the hardware is considered to have failed. These codes turn up in sense data byte 14 and as the sense code qualifier for sense codes 4400h (internal target failure) and 40XX (diagnostic failure).

Interface Implementation20

Although there are no actual Field Replaceable Units on HP Ultrium drives, the following subassemblies can be replaced at Repair Centres:

• Drive PCA • Head Assembly

• Mechanism • Front Panel

CD-ROM emulation

The One Button Disaster Recovery (OBDR) functionality in HP Ultrium drives enables them to emulate CD-ROM devices in specific circumstances (also known as being in “Disaster Recovery” mode). The drive can then act as a boot device for PCs that support booting off CD-ROM.

A CD-ROM capable drive can be switched into CD-ROM mode by powering on with the eject button held down. The drive then alters its behavior as follows:

• The front panel lights flash a “warbling” sequence.

• CD-ROM commands are executed (as opposed to tape drive mode when they would be

rejected). Commands specific to CD-ROM mode are

CAPACITY

(

LOCATE), these are interpreted as CD-ROM commands 08h (READ 6), 1Bh (ST ART/STOP)

and 2Bh (

. In the case of SCSI commands 08h (READ), 1Bh (LOAD/UNLOAD) and 2Bh

SEEK) respectively.

READ 10, READ TOC and READ

• Writing is disabled.

• Normal

emulation and to sw itch the peripheral device type field to indicate a CD-R O M drive .

• The mode header and mode block descriptor are modified.

• A CD-Emulation mode page is added.

• Mode data changes to reflect CD-ROM medium type and block size.

• Status reporting by the media access check is altered.

• The drive’s sense data when the media is not ready for access always indicates “loading”.

If a tape is inserted while the drive is in CD-ROM mode, the drive assumes that it will contain an image of a CD offset 20 blocks into the tape. It reads the first 250 kilobytes of this image into buffer space reserved for CD-caching. It then looks for a special message (“

SPECIFICATION

message, it ejects the tape and waits in CD-ROM mode for a properly-written CD-image tape to be inserted.

The drive will remain in CD-emulation mode until one of the following occurs:

• A

mode page.

INQUIRY data is modified to add a field indicating that the drive supports CD

EL TORITO

”) at the 8th byte of the 18th record of the image. If the drive fails to find this

MODE SELECT command switc hes it back to ta pe drive mode using the CD-emulation

Interface Implementation

CD-ROM emulation

• A SCSI bu s r e set occurs following the reading o f at leas t 100 bloc ks of CD-R OM data by a

host.

• The user power-cycles the drive or resets it using the forced-eject mechanism. NOTE: If the drive exits CD-ROM mode through either of the first two of these, the tape will

remain at the last logical position when in CD-ROM mode.

Interface Implementation22

2Messages

This chapter includes all SCSI messages, both supported and unsupported. Parts of this chapter come from Section 5, Logical Characteristics, of the SCSI standards (see page 11).

The message system provides an initiator and a target on the SCSI bu s wit h a means of managing communication. The available messages are listed in this chapter.

Message Out support

Name Code Support

Abort 06h An abort condition is generated (see “Abort handling” on page 14). Bus Device Reset 0Ch A reset condition is generated (see “Reset strategy” on page 13). Extended Message 01h See “Extended Message Support” below. Identify 80h+ The Identify Out message is sent by the initiator to identify the Logical

Unit to be accessed and to set Disconnect Privilege.

Initiator Detected Error

Message Parity Error 09h The initiator has detected a parity error in a mess age. The dri v e w ill r etry

Message Reject 07h This message is sent when the initiator does not support a message sent

No Operation 08h This message has no effect and is ignored.

05h The initiator has detected an er ror in the data be ing sent in a C ommand,

Data or Status phase. The drive will send a restore data pointers message to retry the data transfer. (See “Message In support” below for details).

If the message is recei ved immediately after an Identify message or after the Command Complete message has been sent, the drive will go Bus Free.

the message. (S ee “Me ssage In support” below for details). If the message is recei ved immediately after an Identify message or after

the Command Complete message has been sent, the drive will go Bus Free.

by the drive or that the message is inappropriate. If the message being rejected is Disconnect , Synchronous Data T r ansfer R eques t or Wi de Data Transfer Request, the operation continues without those features. For all other messages, the message is treated as an Abort message.

If the message is received during a Command, Data or Status phase, immediately after an Identify message or after the Command Complete message has been sent, the driv e will go Bus Free.

Messages

Message In support

Name Code Support

Command Complete 00h This message is sent by the drive at the end of the status phase to

Disconnect 04h This message is sent by the drive to indicate that it is about to

Extended Message 01h See “Extended Message Support” below. Identify 8

Ignore Wide Residue 23h This message is sent by the drive to the h ost to indicate that a byte on

Message Reject 07h This message is sent to the initiator when th e mess age r ece iv ed b y the

indicate that a command is complete. Once the message is sent, the drive releases the bus and goes to Bus Free.

disconnect from the bus and go to Bus Free. During a Data phase, it is always pre-ceded by a Save Data Pointers message. If a Message Reject message is received in response to this message, then the disconnect is prevented.

h The Identify In message is sent to the initiator during reconnect to

indicate w hich Logical Unit is r econnecting.

a wide bus is not valid. This is supported whenever a wide transfer is active. It should be sent

at the end of the data phase. The standard acti on of the drive is to send this message between the data phase and the status phase with no disconnect.

drive is unsupported or inappropr iate.

Restore Pointers 03h This message causes the initiator to reset its data transfer poin ters to

the values they held when the last save data poi nters message was sent. It will be s ent w hen a parity error is detected on the bus or when an Initiator Detected Error message is rece ived in order to retry the data phase.

Save Data Pointers 02h This message instructs the initiator to save its current data transfer

pointers for use with a subsequent Restore pointers message . This message will always be sent before a Disconnect message duri ng data phases.

Messages24

Extended Message support

Name Code Support

Synchronous Data Transfer Request

Wide Data Transfer 03h The drive can initiate a Wide data transfer negotiation. If the message

Parallel Protocol Request

01h The drive can initiate a Synchronous data transfer negotiation. If the

message is received after selection and before the command phase, it will then go to message-in phase and respond with a valid re s ponse to complete the negotiation.

is received after selection and before the command phase, it will then go to message-in phase and respond with a valid response to complete the negotiation.

Note that SDTR negotiated parameter s w ill become asy nc hro nous after a WDTR.

04h The drive will never initiate a Parallel Protocol Request transfer

negotiation but will expect the initiator to do so. If the message is receiv ed afte r selection and before the command

phase, it will then go to message-in phase and respond with a valid response to complete the negotiation.

Sy nchronous Data T ransfer Request

7 6 5 4 3 2 1 0 0 Extended Message (01h) 1 Extended Message Length (03h) 2 SDTR (01h) 3 Transfer Period Factor 4 Req/Ack Offset

Wide Data Transfer Request

7 6 5 4 3 2 1 0 0 Extended Message (01h) 1 Extended Message Length (02h) 2 WDTR (01h) 3 Transf e r W idth Exponent

Messages

Parallel Protocol Request

7 6 5 4 3 2 1 0 0 Extended Message (01h) 1 Extended Message Length (06h) 2 Parallel Protocol Request (04h) 3 Transfer Period Factor 4 Reser v ed (0) 5 Req/Ack Offset 6 Transfer Width Exponent 7 PComp_En RTI Rd_Strm WR_Flow Hold_MCS QAS_Req DT_Req IU_Req

Fields:

Transfer Peri od Factor

Req/Ack Offset This has a maximum value of 255. Transfer Width

Exponent PComp_En Precompensation enable bit. Supported.

RTI Retain Training Information bit. Supported. Rd_Strm 0 Read streaming and read flow control enable bit. Not supported, so the

Wr_Flow 0 Write flow control enable bit. Not supported; the drive will always return

Hold_MCS 0 Hold Margin Control S ettings bit. Not supported; the dri v e w ill alw ay s r etur n

QAS_Req 0 QAS enable request bit. Not supported; the drive will always return zero. DT_Req This bit determines whether DT mode has been requested, in other words,

IU-Req Information units enabled request bit. Supported.

08h Transfer period of 6.25 ns, Paced Information Unit transfers 09h Transfer period of 12.5 ns (FAST-80). Only valid when DT transfers have

been requested

0Ch Transfer period of 50 ns (FAST-20) — LVD/SE drives only 19h Transfer period of 100 ns (FAST-10) 32h Transfer period of 200 ns (FAST-5)

For ST transfers, this can be either 0 (Narrow) or 1 (Wide). For DT transfers, it must be set to 1.

drive will always return zero.

zero.

packetized data transfers. Supported.

Status

A Status byte is sent from the drive to the host during the Status phase at the end of each command as specified in the SCSI specification, unless the command has been cleared by an

ABORT message, by a BUS DEVICE RESET message, or by a hard reset.

Messages26

The Status bytes that the drive returns are as follows:

00h GOOD: This status indicates that the drive has successfully completed the command. 02h CHECK CONDITION: Any err or , e xceptio n, or abnormal condition that causes sense data to be

set returns CHECK CONDITION. The REQUEST SENSE command should be sent following this status to determine the nature of the error.

04h CONDITION MET: This status will never be returned by an HP Ultrium tape drive. 08h BUSY: T he drive is unable to ex ecute the command at this time. Try again later. The drive tries

to avoid using this status code during normal operation. It can sometimes be used after commands have been aborted, during power-on and if there are multiple selecting initiators.

10h INTERMEDIATE: This status will never be returned by an HP Ultrium tape drive. 14h INTERMEDIATE CND: This status will never be returned by an HP Ultrium tape drive. 18h RESERVAT ION CONF LICT: Returned if the drive is reserved by another party. See the

Reservation check.

22h COMAND TERMINATED: This status will never be returned by an HP Ultrium tape drive. 28h QUEUE FULL

Status

Messages

Messages28

3 Commands—introduction

This chapter contains notes relating to the SCSI commands listed in Chapter .

Summary

The following table is a summary of the SCSI commands for sequential access devices, showing the operation code:

Opcode Command Name Opcode Command Name

00h

TEST UNIT READY

01h

REWIND

03h

REQUEST SENSE

05h

READ BLOCK LIMITS

08h

READ

08h

READ 6 (CD-ROM)

0Ah

WRITE

0Bh

SET CAPACITY

10h

WRITE FILEMARKS

11h

SPACE

12h

INQUIRY

13h

VERIFY

15h

MODE SELECT

16h

RESERVE UNIT

17h

RELEASE UNIT

19h

ERASE

1Ah

MODE SENSE

1Bh

LOAD/UNLOAD

1Bh

START/STOP UNIT (CD-ROM)

1Ch

RECEIVE DIAG RESULTS

1Dh

SEND DIAGNOSTIC

1Eh

PREVENT MEDIUM REMOVAL

25h

READ CAPACITY (CD-ROM)

28h

READ 10 (CD-ROM)

2Bh 2Bh 34h 3Bh

3Ch

43h

44h 4Ch 4Dh

55h

56h

57h 5Ah

5Eh

5Fh 8Ch 8Dh A0h

A3h (05h) A3h (0Ch) A3h (0Dh) A4h (06h) ABh (01h)

LOCATE SEEK (CD-ROM) READ POSITION WRITE BUFFER READ BUFFER READ TOC (CD-ROM) REPORT DENSITY SUPPORT LOG SELECT LOG SENSE MODE SELECT (10) RESERVE UNIT (10) RELEASE UNIT (10) MODE SENSE (10) PERSISTENT RESERVE IN PERSISTENT RESERVE OUT READ ATTRIBUTE WRITE ATTRIBUTE REPORT LUNS REPORT DEVICE IDENTIFIER REPORT SUPPORTED OPCODES REPORT SUPPORTED TASK MGMNT FNS SET DEVICE ID READ MEDIA SERIAL NUMBER

Command details

The command descriptions in Chapter 4 are listed in alphabetical order of command name. Each command is described briefly. This is followed by a list of pre-execution checks which are described below. The Command Descriptor Block (CDB) is then given, with details of the various parameter bits and fields.

Summary

Commands—introduction

Pre-executio n checks

NOTE: In compliance with the SCSI specification, the drive term inates a command with a

CHECK CONDITION status and sets the sense ke y to ILLEG AL RE QUEST when a reserved bit , byt e,

field or code is received which is not zero.

Before executing a command, the drive makes a number of checks. They fall into three categories:

• Checks on the command sent by the host. These ensur e that no reserved or f ix ed fields hav e

been set to illegal values. They check the syntax of commands, in other words the cross dependency of fields. For example, the Flag bit must not be set if the Link bit is not set.

• Checks to ensure that there are no outstanding

posted for the host that has sent the command.

• Checks on media access abilities. Th ese are performed for commands re quiring access to

the cartridge. A command is rejected if it attempts to access the cartridge when no cartridge is present or the cartridge is unloaded.

The checks are described below in alphabetical order. The usual order of executi on is Illegal Field , Fixed Bit, Flag Link, Bad LUN, Reservation, Deferred Error, Unit Attention, Media Access, Media Write, Diagnostic Status, Humidity, Parameter List.

Bad LUN check

For all commands except INQUIRY 12h, this checks that the LUN specified by the host is zero. The LUN is taken from the lowest 5 bits of the host’s

• If no

• If an

• If the LUN is unsupported, and the host command is not

• If the LUN is unsupported, and the host command is

IDENTIFY message is supplied, the LUN is taken from the host’s Command Descriptor

Block.

IDENTIFY message is supplied, the LUN in the host’s Command Descript or Bloc k is

ignored

CONDITION

sense of 2500h (logical unit not supported).

data is replaced with a sense key of (logical unit not supported). This new sense data is returned to the host. Once the command has completed successfully, the sense data is cleared.

is reported to the host with a sense ke y of ILLEGAL REQUEST, and additional

UNIT ATTENTION or DEFERRED ERROR events

IDENTIFY message.

REQUEST SENSE, CHECK

REQUEST SENSE, the original sense

ILLEGAL REQUEST, and additional sense of 2500h

Deferred Error check

A deferred error is generated when a command with immediate report fails after the report has been returned. The check looks to see if a deferred error exists for the host which sent the command, in other words, a deferred error for which

Commands—introduction30

CHECK CONDITION status has not yet been

+ 166 hidden pages