Ultrium Internal Tape Drive Models T200 and T200F and 3580 Ultrium Tape Drive SCSI Reference WB1109-02
Ultrium Internal Tape Drive Models T200 and T200F and 3580 Ultrium Tape Drive SCSI Reference WB1109-02
Note Before using this information and the product it supports, be sure to read the general information under “Appendix. Notices” on page 103. Fifth Edition (October 2001) This edition applies to the IBM® Ultrium™ Internal Tape Drive Models T200 and T200F and 3580 Ultrium Tape Drive SCSI Reference and to all subsequent releases and modifications unless otherwise indicated in new editions. This edition replaces WB1109-01.1. © Copyright International Business Machines Corporation 2001, 2000.
Contents Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Organization . . . . . . . . . . . . . . . . . . . . . . . . . . xi Related Publications . . . . . . . . . . . . . . . . . . . . . . . xi | | | Chapter 1. Introduction . . . . Supported Servers and Operating SCSI Attachment . . . . . Fibre Channel Attachment . . Supported Device Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
READ BUFFER . . . . . . . Error Log Buffer . . . . . . READ POSITION . . . . . . . RECEIVE DIAGNOSTIC RESULTS RELEASE UNIT . . . . . . . REPORT DENSITY SUPPORT . . REPORT LUNs. . . . . . . . REQUEST SENSE . . . . . . Sense Data Format . . . . . RESERVE UNIT . . . . . . . REWIND . . . . . . . . . . SEND DIAGNOSTIC . . . . . . Self-Test . . . . . . . . . SIM Data Structure . . . . . MIM Data Structure . . . . . Force Dump . . . . . . . . Write Dump To Cartridge . . . Post A Self Test Diagnostic . .
How to Send Your Comments . . . . . . . . . . . . . . . . . . . 104 Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . 105 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi Ultrium Internal Tape Drive and 3580 Ultrium Tape Drive: SCSI Reference
Tables 1. Supported Common Commands . . . . . . . . . . . . . . 2. ERASE Command. . . . . . . . . . . . . . . . . . . . 3. INQUIRY Command . . . . . . . . . . . . . . . . . . . 4. Standard Inquiry Data Valid LUN . . . . . . . . . . . . . . 5. Standard Inquiry Data Invalid LUN . . . . . . . . . . . . . . 6. Supported Vital Product Data Inquiry Page . . . . . . . . . . 7. Unit Serial Number Inquiry Page . . . . . . . . . . . . . . 8. Device Identification Inquiry Page . . . . . . . . . . . . . . 9.
| | | 54. Parameter Data for a Partition List Service Action Request . 55. Format for Medium Auxiliary Memory Attribute . . . . . . 56. Attribute Descriptions . . . . . . . . . . . . . . . 57. Device Common Attributes . . . . . . . . . . . . . 58. Device Vendor/Serial Number Attribute . . . . . . . . . 59. Medium Common Attributes . . . . . . . . . . . . . 60. Host Common Attributes . . . . . . . . . . . . . . 61. READ BLOCK LIMITS Command. . . . . . . . . . . 62. READ BLOCK LIMITS Descriptor . . . . . .
0. 111. 112. 113. 114. Abort Condition Handling . . . . Status Codes . . . . . . . . Supported Outbound Messages . Supported Inbound Messages . . Supported Extended Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 . 96 . 98 . 99 . . . . . . . . . . . . . . . . . . . . . . . .
x Ultrium Internal Tape Drive and 3580 Ultrium Tape Drive: SCSI Reference
Preface This publication contains information about how to use and program the IBM Ultrium Internal Tape Drive Models T200 and T200F and the IBM 3580 Ultrium Tape Drive. Organization The information in this book is organized as follows: v “Chapter 1. Introduction” on page 1 describes the tape drives. v “Chapter 2. Command Support” on page 5 lists the SCSI commands that are supported by the tape drives. v “Chapter 3.
v SCSI Stream Commands-2 (SSC-2), published by the American National Standards Institute and available on the web at http://www.t10.org. v SCSI Primary Commands-2 (SPC-2), published by the American National Standards Institute and available on the web at http://www.t10.org. v SCSI Primary Commands-3 (SPC-3), published by the American National Standards Institute and available on the web at http://www.t10.org.
Chapter 1. Introduction | | | The IBM Ultrium Internal Tape Drive Models T200 and T200F and the IBM 3580 Ultrium Tape Drive are high-performance, high-capacity data-storage devices that connect to and provide additional storage for supported servers. The Model T200 uses a Small Computer Systems Interface (SCSI) and the Model T200F uses a Fibre Channel interface. The 3580 Ultrium Tape Drive contains the Ultrium Tape Drive Model T200 (the SCSI drive). Figure 1 shows the IBM 3580 Ultrium Tape Drive.
Designed to perform unattended backups as well as to retrieve and archive files, the Ultrium Internal Tape Drives feature: v Native storage capacity of 100 GB per cartridge (200 GB at 2:1 compression)1 v Native sustained data transfer rate of 15 MB per second (30 MB at 2:1 compression)2 v RS-422 interface for enhanced performance in automated tape libraries. | | | The Ultrium Internal Tape Drive Model T200 uses an Ultra2 SCSI Low Voltage Differential/Single Ended (LVD/SE) interface.
Supported Servers and Operating Systems | The IBM Ultrium Internal Tape Drive Models T200 and T200F and the IBM 3580 Ultrium Tape Drive are supported by a wide variety of servers and operating systems, as well as adapters. These attachments can change throughout the products’ life cycles. To determine the latest supported attachments: v For the Ultrium Tape Drive Models T200 and T200F, visit the Web at http://www.ibm.
| Supported Device Drivers IBM maintains the latest levels of device drivers and driver documentation for the 3580 Ultrium Tape Drive on the Internet. You can access this material from your browser or through the IBM FTP site by doing the following: Note: If you do not have Internet access and you need information about device drivers, contact your IBM Marketing Representative. v Using a browser, type one of the following: – http://www.ibm.com/storage – ftp://ftp.software.ibm.
Chapter 2. Command Support Notes: 1. For this chapter, a megabyte (MB) is equal to 1 048 576 bytes. 2. Binary numbers are represented by numbers followed by b. Hexadecimal numbers are represented by 0-9 and A-F followed by h. Numbers with no suffix can be assumed to be decimal. | | | | | Table 1.
Table 1.
INQUIRY Table 3. INQUIRY Command 7 6 5 0 1 4 3 2 1 0 Operation Code (12h) Logical Unit Number (0) Reserved 2 Page Code 3 Reserved 4 Allocation Length 5 Control EVPD The INQUIRY command instructs the drive to return data about itself to the initiator. If the Enable Vital Product Data (EVPD) flag is clear and the Page Code is 0, standard Inquiry Data is returned.
Standard Inquiry Data Valid LUN Table 4.
Standard Inquiry Data Invalid LUN Table 5.
Supported Vital Product Data Page Table 6.
Device Identification Page Table 8. Device Identification Inquiry Page 7 0 6 5 4 Peripheral Qualifier (000b) 3 2 1 0 Peripheral Device Type (01h) 1 Page Code (83h) 2 Reserved 3 Page Length (n-3) 4 : Identification Descriptors n The device Identification Descriptor Page contains a series of device Identification Descriptors that uniquely identify the particular device. The format of each is given in Table 9. Table 9.
The Fibre Channel Identification descriptor is returned only on Fibre-Channelattached devices. The format is given in Table 10. Table 10.
Drive Component Revision Levels Pages Table 11. Drive Component Revision Levels Pages 7 0 6 5 4 Peripheral Qualifier (000b) 3 2 1 0 Peripheral Device Type (01h) 1 Page Code (C0h) 2 Reserved 3 Page Length (27h) 4 : Component (CCCCCCCCCCCC) 15 16 : Version (RRR.VVV) 22 23 : Date (YYYYMMDD) 30 31 : Variant (XXXXXXXXXXXX) 42 | | | The Drive Component Revision Levels Pages contain details of the revisions of each of the components of the drive.
LOAD/UNLOAD Table 12. LOAD/UNLOAD Command 7 6 5 0 1 4 3 1 0 Operation Code (1Bh) Logical Unit Number (0) Reserved 2 Reserved 3 Reserved 4 2 Reserved 5 EOT(0) Immed Reten(0) Load Control If the Load flag is set and there is a tape in the drive, it is positioned to BOM. If the Load flag is set and there is no tape in the drive, Check Condition status is returned. The Sense Key is set to Not Ready (2) and the ASC/ASCQ is set to Parameter Medium Not Present (3A00).
LOCATE The LOCATE command causes the logical position on tape to be set to the value indicated by the Block Address field. The value indicates the total number of records and marks between BOM and the desired logical position. A value of 0 causes the tape to be positioned at BOM. If the Immediate (Immed) flag is set to 1, then the drive validates the command and waits for any previous command from any server to complete, including any immediate commands that are currently being processed.
LOG SELECT Table 14. LOG SELECT Command 7 6 5 0 1 2 4 3 Logical Unit Number (0) Reserved PC 0 PCR SP(0) Reserved Reserved 4 Reserved 5 Reserved 6 Reserved 8 1 Operation Code (4Ch) 3 7 2 Parameter List Length 9 Control The LOG SELECT command causes log data on the drive to be reset to its default value or to be set to an initiator-specific value.
LOG SENSE Table 15. LOG SENSE Command 7 6 5 0 1 2 4 3 Logical Unit Number (0) Reserved PC 4 Reserved 7 8 9 0 PPC(0) SP(0) Page Code Reserved 6 1 Operation Code (4Dh) 3 5 2 Parameter Pointer (0) Allocation Length Control The LOG SENSE command causes log data to be sent to the initiator. If the Page Control (PC) field is 00b or 10b, the maximum value for each log entry is returned. If it is 01b, the current values are returned.
Log Page Format All log pages (except page 0) consist of a log page header, followed by a number of log parameters. The log page header has the format indicated in Table 16. Table 16. Log Page Header Format 7 0 6 5 4 3 Reserved 2 1 0 Page Code 1 Reserved 2 Page Length 3 The Page Code is a byte value that uniquely identifies what log page is being returned. The Page Length describes how many bytes are to follow for the entire log page. Each log parameter has the format indicated in Table 17.
Supported Log Pages The Supported Log Pages Log Page code is 00h. The parameter list contains a series of 1-byte entries for the log pages that are supported. At least those logs described in this document must be listed. Any additional logs that are supported must also be listed. The format of this page is give in Table 18. Table 18.
Write Error Counters Log The Write Error Counters log is page 02h. Parameters 0 through 2 are not supported and are returned as 0. All parameter lengths are 4 bytes long, except parameter 8000 which is 8 bytes long. The supported fields are listed in Table 19. Table 19.
Read Error Counters Log The Read Error Counters log is page 03h. Parameters 0 through 2 are not supported and are returned as 0. All parameter lengths are 4 bytes long, except parameter 8000 which is 8 bytes long. The supported fields are listed in Table 20. Table 20.
Sequential Access Device Log The Sequential Access Device Log Page is 0Ch. Table 21.
TapeAlert Log The TapeAlert log page is page 2Eh. There are 64 parameters, numbered from 1 through 64. Only parameters 1 through 18, 20 through 23, and 29 through 39 have definitions for tape drives without attached loaders. The remaining parameters are always 0. All parameters are 1 byte long. Each parameter is either 0 to indicate the corresponding condition has not occurred or 1 to indicate that the corresponding condition has occurred. All log parameters are cleared when the log is read.
Table 22. TapeAlert Log Parameters (continued) Parameter Description 38 Predictive Failure 39 Diagnostics Required Type DU LP LBIN Critical 1 0 0 Warning 1 0 0 See the TapeAlert specification for more complete descriptions of the flags. This data can be neither written nor reset. The flags are cleared by the action of reading the log. Tape Usage Log The Tape Usage Log Page Code is 30h. These are all read directly from the tape logs. Table 23.
| | | Note: For this command, a megabyte is equal to 1 048 576 bytes. As an example, a value of 17487h in Parameter 3 is equal to 95 367 megabytes, which is equal to 100 000 000 000 bytes. Data Compression Log The Data Compression Log Page Code is 32h. Parameter byte fields 0 and 1 are 2 bytes long. Parameter byte fields 2 through 9 are each 4 bytes long. The supported fields are listed in Table 25. Table 25.
MODE SELECT Table 26. Byte MODE SELECT Command 7 6 5 0 1 4 3 2 1 0 Operation Code (15h) Logical Unit Number (0) PF Reserved 2 Reserved 3 Reserved 4 Parameter List Length 5 Control SP(0) Table 27.
MODE SENSE Both the 10-byte and the 6-byte versions of the command are supported. Table 28. Byte MODE SENSE Command 7 6 5 0 1 4 3 2 1 0 Operation Code (1Ah) Logical Unit Number (0) 2 Reserved DBD PC Reserved Page Code 3 Reserved 4 Allocation Length 5 Control Table 29.
Mode Data Format Mode data returned by a MODE SENSE command or sent with a MODE SELECT command consists of a Mode Parameter Header, an optional Mode Block Descriptor, and zero or more Mode Parameter Pages. Table 30. Mode Data Format 7 6 5 4 3 2 1 0 1 0 0 : Mode Parameter Header 3 4 : Mode Block Descriptor 11 12 : Mode Parameter Pages n Mode Parameter Header Table 31.
If the Buffered Mode is 0, then the drive does not report Good status on WRITE and WRITE FILE MARKS commands until the data is written to tape. If Buffered Mode is 1, then the drive reports Good status as soon as data has been transferred into the drive’s data buffer. The default value is 1. The Speed field is not used and should be set to 0. The Block Descriptor Length is 0 if no Block Descriptor is transferred or 8 if a Block Descriptor is transferred.
Read-Write Error Recovery Page Table 34. Read-Write Error Recovery Page 7 0 6 4 PS (0) Reserved 1 2 5 3 2 1 0 DTE(0) DCR(0) Page Code (01h) Additional Page Length (0Ah) Reserved TB (0) Reserved EER(1) 3 Read Retry Count (FFh) 4 Reserved 5 Reserved 6 Reserved 7 Reserved 8 Write Retry Count (FFh) 9 Reserved 10 Reserved 11 Reserved PER The only supported field is Post Error (PER).
The Maximum Burst Size field for the SCSI parallel interface indicates (in multiples of 512 bytes) the number of bytes that the drive should attempt to send or receive between disconnects. The default is 0, which implies that the drive may send bursts of data at any size. The Maximum Burst Size field for the Fibre Channel interface indicates the sequence size that the drive should attempt to use when transferring data. Any value is allowed and ignored.
Sequential Access Device Configuration Page The Write Delay Time field indicates the time (in 100-ms increments) that the drive should wait with unwritten data in the buffer and no activity on the interface before forcing data to tape. The Change Active Partition (CAP) flag and the Active Partition field should be 0, since multiple partitions are not supported. The Change Active Format (CAF) and Active Format fields should be 0, since changing formats is not supported.
The Enable EOD Generation flag should be set, since EOD generation is always enabled. The Buffer Size at Early Warning field should be 0, as this cannot be set. The default value for the Select Data Compression Algorithm is 1 and indicates that data compression is enabled. If Select Data Compression Algorithm is 0, the drive uses Scheme 2 of the LTO-DC algorithm (passthrough mode).
Fibre Channel Port Control Page There is one copy of this page per Fibre Channel port. This page is defined for Fibre-Channel-attached devices only. Table 39.
Information Exceptions Mode Page Table 40. Information Exceptions Mode Page 0 7 6 PS (0) Reserved 5 3 3 2 1 0 Page Code (1Ch) 1 2 4 Page Length (0A) Perf (0) Reserved DExcept Reserved Test Reserved LogErr(0) MRIE (3) 4 : Interval Timer (0) 7 8 : Report Count (0) 11 The Information Exceptions mode page is used to control Exception Reporting by using the TapeAlert log page. If the DExcept flag is clear, Exception Reporting is enabled.
PERSISTENT RESERVE IN Table 41. PERSISTENT RESERVE IN Command 7 6 0 1 5 4 3 1 0 Operation Code (5Eh) Reserved Service Action 2 Reserved 3 Reserved 4 Reserved 5 Reserved | 6 Reserved | 7 : 2 Allocation Length 8 9 Control The PERSISTENT RESERVE IN command is used for reservation management to show what types of Reservations and Reservation Keys exist.
The PERSISTENT RESERVE IN parameter data for Read Keys is defined in Table 42. Table 42. PERSISTENT RESERVE IN Parameter Data for Read Keys 7 6 5 4 3 2 1 0 0 : Generation 3 4 : Additional Length 7 8 : First Reservation Key 15 16 : Additional Reservation Keys n Generation is a counter for PERSISTENT RESERVE OUT command requests. Additional Length is a count of the number of bytes in the Reservation Key list.
Reservation Descriptors are defined in Table 44. The PERSISTENT RESERVE IN Read Reservations Descriptor is defined in Table 44. Table 44. PERSISTENT RESERVE IN Read Reservations Descriptor 7 6 5 4 3 2 1 0 0 : Reservation Key 7 8 : Scope-specific address (0) 11 12 13 Reserved Scope (0h) Type 14 : Extent Length (0) 15 A Scope value of 0h indicates that the persistent reservation applies to the entire logical unit.
PERSISTENT RESERVE OUT Table 45. PERSISTENT RESERVE OUT Command 7 6 5 0 1 2 4 3 2 1 0 Operation Code (5Fh) Reserved Service Action Scope ( 0) Type 3 Reserved 4 Reserved 5 Reserved 6 Reserved 7 : Parameter List Length (18h) 8 9 Control The PERSISTENT RESERVE OUT command is used for reservation management to allow different types of Reservations and Reservation Keys to be created or removed.
The PERSISTENT RESERVE OUT parameter list is defined in Table 46. Table 46. PERSISTENT RESERVE OUT Parameter List 7 6 5 4 3 2 1 0 0 : Reservation Key 7 8 : Service Action Reservation Key 15 16 : Scope-specific Address (0) 19 20 21 Reserved APTPL (0) Reserved 22 : Obsolete (0) 23 Any value is allowed for the Reservation Key and the Service Action Reservation Key. The value for Activate Persist Through Power Loss (APTPL) is 0.
PREVENT/ALLOW MEDIUM REMOVAL Table 47. PREVENT/ALLOW MEDIUM REMOVAL Command 7 6 5 0 1 4 3 Logical Unit Number (0) 0 Reserved Reserved 3 Reserved 5 1 Operation Code (1Eh) 2 4 2 Reserved Prevent Control The PREVENT/ALLOW MEDIUM REMOVAL command is used to prevent accidental removal of the medium while it is required by an initiator. If the Prevent flag is set, then eject requests from the front panel are ignored and Unload commands give Check Condition status.
READ Table 48. READ Command 7 6 5 0 1 4 3 2 1 0 SILI Fixed Operation Code (08h) Logical Unit Number (0) Reserved 2 : Transfer Length 4 5 Control The READ command causes data to be transferred from the tape medium to the initiator. If the Fixed flag is clear and Transfer Length is not 0, then a single block of the length in Transfer Length is to be transferred. If the next block on tape is of this length or shorter, then it is transferred to the initiator.
READ ATTRIBUTE Table 49. READ ATTRIBUTE Command 7 6 5 0 4 3 2 1 0 Operation Code (8Ch) 1 Reserved (0) Service Action 2 : Reserved 3 4 Reserved 5 Volume Number (0) 6 Reserved 7 Partition Number (0) 8 : First Attribute ID 9 10 : Allocation Length | 13 | 14 Reserved | 15 Control | | Until the SCSI Primary Commands-3 (SPC-3) is published, refer to SCSI proposal T10/99-148r7 for support for the READ ATTRIBUTE command. The supported Service Action codes are listed in Table 50.
Table 51. Parameter Data for an Attribute Values Service Action Request 7 6 5 4 3 2 1 0 0 : Available Data (n-3) 3 4 : Attribute #1 x m : Attribute #y n Table 52 describes the format of the data returned for an Attribute List service action request. Table 52.
Table 54 describes the format of the data returned for a Partition List service action request. Table 54. Parameter Data for a Partition List Service Action Request 7 6 5 4 3 2 1 0 0 : Available Data (2) 1 | 2 First Partition Number (0) 3 Number of Partitions Available (1) Medium Auxiliary Memory Attribute Data | | | The Medium Auxiliary Memory Attribute data is used by both the READ ATTRIBUTE and WRITE ATTRIBUTE commands. Table 55 describes the attribute format.
Table 57 describes Device Common attributes. All Device Common attributes are read only. Table 57.
Table 59 describes the Medium Common Attributes. Table 59.
READ BLOCK LIMITS Table 61. READ BLOCK LIMITS Command 7 6 5 4 0 1 3 2 1 0 Operation Code (05h) Logical Unit Number (0) Reserved 2 Reserved 3 Reserved 4 Reserved 5 Control The READ BLOCK LIMITS command requests that the drive return the maximum and minimum block sizes that it supports. The maximum block size is set to 0xFFFFFF and the minimum block size is set to 1. The format of the data returned is shown in Table 62. Table 62.
READ BUFFER Table 63. READ BUFFER Command 7 6 5 0 1 4 3 2 1 0 Operation Code (3Ch) Logical Unit Number (0) Reserved 2 Mode Buffer ID 3 : Buffer Offset 5 6 : Allocation Length 8 9 Control The READ BUFFER command reads data from the memory on the drive and sends it to the initiator. Modes 000b, 010b and 011b are supported. If it is set to 010b, then just the data is returned. If it is set to 011b, just the descriptor is returned.
Table 65.
Error Log Buffer The error log buffer contains zero or more entries described in Table 66. Table 66. Error Log Buffer Command 7 6 5 4 3 2 1 0 0 : Time Stamp 3 4 Entry Number 5 Error Code 6 7 8 9 10 11 12 13 Fsc 1st Text Fsc 1st Data Fsc 2nd Text Fsc 2nd Data 14 : Cartridge Serial Number 21 22 : EC Level 27 28 : Hardware Level 31 Chapter 2.
READ POSITION Table 67. READ POSITION Command 7 6 5 4 0 1 3 2 1 0 Operation Code (34h) Logical Unit Number (0) Reserved 2 Reserved 3 Reserved 4 Reserved 5 Reserved 6 Reserved 7 Reserved 8 Reserved 9 Control BT(0) The READ POSITION command returns current position information to the initiator. The data returned has the format in Table 68. Table 68.
The First Block Location and the Last Block Location are both set to the number of blocks and file marks between BOM and current logical position. If the tape is at BOM, 0 is returned in these fields. The Beginning of Partition (BOP) flag is set if the Block Location fields are 0. The End of Partition flag is not supported and is set to 0. The Block Position Unknown flag is always set to 0, since the position is always known.
RELEASE UNIT Table 70. Byte RELEASE UNIT Command 7 6 5 4 0 1 3 2 1 0 Operation Code (17h) Logical Unit Number (0) 3rdPty Third Party Device ID (0) 2 Reservation Identification 3 Reserved 4 Allocation Length (0) 5 Control Element Table 71.
REPORT DENSITY SUPPORT Table 72. REPORT DENSITY SUPPORT Command 7 6 5 0 1 4 3 2 1 0 Operation Code (44h) Logical Unit Number (0) Reserved 2 Reserved 3 Reserved 4 Reserved 5 Reserved 6 Reserved 7 Media Allocation Length 8 9 Control The REPORT DENSITY SUPPORT command returns details about the tape formats supported by the drive. The data is returned as a header and a series of descriptor blocks.
The header is followed by one or more REPORT DENSITY SUPPORT descriptor blocks with the format in Table 74. Table 74.
The values reported for the Ultrium format are as follows: Table 75. Density Information for LTO Formats Field | | Ultrium 1 Primary density code 40h Secondary density code 40h Bits per mm 4880 Media width (in tenths of mm) 127 Tracks 384 Capacity (in megabytes) Assigning organization Density name Description 95367 LTO-CVE U-18 Ultrium 1/8T The Write Okay (WRTOK) flag is clear if the drive does not support writing to this format, but does support reading it.
REPORT LUNs Table 76. REPORT LUNs Command 7 6 5 4 3 0 Operation Code (A0h) 1 Reserved 2 Reserved 3 Reserved 4 Reserved 5 Reserved 2 1 0 6 : Allocation Length 9 10 Reserved 11 Control The server uses this command to retrieve information about the Logical Units that the drive supports. The allocation length is at least 16 bytes. If this is not the case, the drive returns Check Condition status, with a Sense Key of Illegal Request and an ASC/ASCQ of Invalid Field in CDB.
REQUEST SENSE Table 78. REQUEST SENSE Command 7 6 5 0 1 4 3 2 1 0 Operation Code (03h) Logical Unit Number (0) Reserved 2 Reserved 3 Reserved 4 Allocation Length 5 Control The sense data returned is described in Table 79 on page 60. Chapter 2.
Sense Data Format Table 79.
The Valid flag is set if the Information field contains valid information. The descriptions that follow serve only as an overview of sense reporting in the tape drive. This tape drive conforms to all sense field reporting, as specified in the SCSI standards. The Error Code field is set to 70h to indicate a current error that is associated with the most recently received command. It is set to 71h to indicate a deferred error that is not associated with the current command.
The Volume Label Fields Valid (VolValid) bit is set if the Volume Label being reported is valid. The Volume Label field reports the volume label if a cartridge is loaded in the drive and Volume Label Fields Valid is set. The Current Wrap reports the physical wrap of the tape. The least significant bit reflects the current physical direction. A 0 means the current direction is away from physical beginning of tape. A 1 means the current direction is towards physical beginning of tape.
RESERVE UNIT Table 80. Byte RESERVE UNIT Command 7 6 5 4 0 1 3 2 1 0 Operation Code (16h) Logical Unit Number (0) 3rdPty(0) Third Party Device ID (0) 2 Reserved 3 Reserved 4 Reserved 5 Control Reserved Table 81.
REWIND Table 82. REWIND Command 7 6 5 0 1 4 3 2 1 0 Operation Code (01h) Logical Unit Number (0) Reserved 2 Reserved 3 Reserved 4 Reserved 5 Control Immed The REWIND command causes the logical position to be set to BOM. If the Immediate (Immed) flag is set to 1, then the drive validates the command and waits for any previous command from any server to complete, including any immediate commands that are currently being processed. It also waits for any buffered data to be flushed to tape.
SEND DIAGNOSTIC Table 83.
SIM Data Structure The following data structure is used in several of the diagnostics. Its purpose is to give detailed error information about drive problems: Table 84.
Table 84.
The Service Message may be one of four values: v ’1’=Repair Impact is Unknown v ’7’=Repair will Disable Access to Device Servo v ’9’=Clean Device v ’A’=Device Cleaned The Severity Code may be one of four values: v ’0’=Service v ’1’=Moderate v ’2’=Serious v ’3’=Acute MIM Data Structure The following data structure is used in several of the diagnostics. Its purpose is to give detailed error information about media problems: Table 85.
Table 85.
The Severity Code may be one of four values: v ’0’=Service v ’1’=Moderate - Temporary Read/Write Errors v ’2’=Serious - Permanent Read/Write Errors v ’3’=Acute - CM Error The Volume ID Flag may be one of four values: v ’0’=VOLID not valid v ’1’=VOLID valid - obtained from tape (CM) v ’3’=VOLID valid - obtained from cartridge label (server data) v ’5’=VOLID valid - obtained from cartridge level (library) 70 Ultrium Internal Tape Drive and 3580 Ultrium Tape Drive: SCSI Reference
Force Dump For the Force Dump Diagnostic, the CDB values should be set as follows: v PF - 1 v SelfTest - 0 v DevOfl - Any value allowed and ignored v UnitOfl - Any value allowed and ignored v Parameter List Length - X0008 Table 86 shows the parameter data to be sent with the Force Dump diagnostic. Table 86.
Write Dump To Cartridge Table 87. Write Dump to Cartridge Send Diagnostic Parameter Data 7 6 5 4 3 0 Page Code (80h) 1 Reserved 2 2 1 0 Page Length (0004h) 3 4 Diagnostic ID (0161h) 5 6 Cartridge Required (1b) Flags (0000000b) 7 Reserved Table 88. Write Dump to Cartridge Receive Diagnostic Parameter Data 7 6 5 4 3 0 Page Code (80h) 1 Reserved 2 3 4 5 7 Reserved Flags (00000b) Diag.
Post A Self Test Diagnostic Table 89. Post A Self Test Send Diagnostic Parameter Data 7 6 5 4 3 0 Page Code (80h) 1 Reserved 2 2 1 0 Page Length (0004h) 3 4 Diagnostic ID (0100h) 5 6 Cartridge Required (bx) Flags (0000000b) 7 Reserved Table 90. Post A Self Test Receive Diagnostic Parameter Data 7 6 5 4 3 0 Page Code (80h) 1 Reserved 2 3 4 5 1 0 Page Length (0004Dh) Diagnostic ID (0100h) 6 Flags 7 Reserved 8 2 Flags (00000b) Diag.
Post B Tape Test Diagnostic Table 91. Post B Tape Test Send Diagnostic Parameter Data 7 6 5 4 3 0 Page Code (80h) 1 Reserved 2 2 1 0 Page Length (0004h) 3 4 Diagnostic ID (0101h) 5 6 Cartridge Required (1b) Flags (0000000b) 7 Reserved Table 92. Post B Tape Test Receive Diagnostic Parameter Data 7 6 5 4 3 0 Page Code (80h) 1 Reserved 2 3 4 5 7 Reserved Flags (00000b) Diag.
Post C Media Test Diagnostic Table 93. Post C Media Test Send Diagnostic Parameter Data 7 6 5 4 3 0 Page Code (80h) 1 Reserved 2 2 1 0 Page Length (0004h) 3 4 Diagnostic ID (0102h) 5 6 Cartridge Required (1b) Flags (0000000b) 7 Reserved Table 94. Post C Media Test Receive Diagnostic Parameter Data 7 6 5 4 3 0 Page Code (80h) 1 Reserved 2 3 4 5 1 0 Page Length (004Dh) Diagnostic ID (0102h) 6 Flags 7 Reserved 8 2 Flags (00000b) Diag.
Post D Head Test Diagnostic Table 95. Post D Head Test Send Diagnostic Parameter Data 7 6 5 4 3 0 Page Code (80h) 1 Reserved 2 2 1 0 Page Length (0004h) 3 4 Diagnostic ID (0103h) 5 6 Cartridge Required (1b) Flags (0000000b) 7 Reserved Table 96. Post D Head Test Receive Diagnostic Parameter Data 7 6 5 4 3 0 Page Code (80h) 1 Reserved 2 3 4 5 7 Reserved Flags (00000b) Diag.
Set Traps For the Set Traps Diagnostic, the CDB values should be set as follows: v PF - 1 v SelfTest - 0 v DevOfl - Any value allowed and ignored v UnitOfl - Any value allowed and ignored v Parameter List Length - X000A Table 97 shows the parameter data to be sent with the Set Traps diagnostic. Table 97.
Remove Traps For the Remove Traps Diagnostic, the CDB values should be set as follows: v PF - 1 v SelfTest - 0 v DevOfl - Any value allowed and ignored v UnitOfl - Any value allowed and ignored v Parameter List Length - X000A Table 98 shows the parameter data to be sent with the Remove Traps diagnostic.
Receive Diagnostics Results - Table 99 shows the diagnostic results data returned for the Remove Traps diagnostic. Table 99. Reset Drive Diagnostic Results Data 7 6 5 4 3 0 Page Code (80h) 1 Reserved 2 1 0 Page Length (n - 4) 3 4 Diagnostic ID (0191h) 5 6 Flags (0) 7 Reserved 8 2 Reserved Diagnostic Reserved Blocked Error 9 : List of Fault Symptom Codes with Trap Still Set n Chapter 2.
Reset Drive For the Reset Drive Diagnostic, the CDB values should be set as follows: v PF - 1 v SelfTest - 0 v DevOfl - 1 v UnitOfl - Any value allowed and ignored v Parameter List Length - 0008h Table 100 shows the parameter data to be sent with the Reset Drive. Table 100.
SPACE Table 101. SPACE Command 7 6 5 0 1 4 3 2 1 0 Operation Code (11h) Logical Unit Number (0) Reserved Code 2 : Count 4 5 Control The SPACE command instructs the drive to set a new logical position relative to the current logical position. How this is done depends on the value of the Code field and the Count field. The Count field is a signed value that indicates the distance to move. A negative value indicates movement towards BOM; a positive value indicates movement towards EOM.
TEST UNIT READY Table 102. TEST UNIT READY Command 7 6 5 0 1 4 3 2 1 0 Operation Code (00h) Logical Unit Number (0) Reserved 2 Reserved 3 Reserved 4 Reserved 5 Control The TEST UNIT READY command returns Good status if a cartridge is loaded and ready. VERIFY Table 103. VERIFY Command 7 6 5 0 1 4 3 2 1 0 Operation Code (13h) Logical Unit Number (0) Reserved Immed(0) BCmp(0) Fixed 2 : Verification Length 4 5 Control The VERIFY command is supported by all drives.
WRITE Table 104. WRITE Command 7 6 5 0 1 4 3 2 1 0 Operation Code (0Ah) Logical Unit Number (0) Reserved Fixed 2 : Transfer Length 4 5 Control The WRITE command causes data to be transferred to the drive in a Data Out and written to tape. If the Fixed flag is clear, the initiator transfers a single block of the length indicated in Transfer Length. If the Fixed flag is set, the initiator transfers a sequence of blocks. The number of blocks is given by the Transfer Length field.
| WRITE ATTRIBUTE | Table 105. WRITE ATTRIBUTE Command | 7 6 5 4 3 | 0 | 1 | : | 4 | 5 Volume Number (0) | 6 Reserved | 7 Partition Number (0) | 8 | : | 9 | 10 | : | 13 | 14 Reserved | | 15 Control 2 1 0 Operation Code (8Dh) Reserved Reserved Allocation Length | | Until the SCSI Primary Commands-3 (SPC-3) is published, refer to SCSI proposal T10/99-148r7 for support for the WRITE ATTRIBUTE command.
WRITE BUFFER Table 107. WRITE BUFFER Command 7 6 5 0 1 2 4 3 2 1 0 Operation Code (3Bh) Logical Unit Number (0) Reserved Mode Buffer ID 3 : Buffer Offset 5 6 : Parameter List Length 8 9 Control The WRITE BUFFER command transfers data into the memory on the drive for the purpose of diagnostics, tests, or firmware upgrade. If the Mode field is 000b, then the data to be written is sent with a 4-byte header, which must be set to all zeroes.
WRITE FILE MARKS The Write Set Mark (WSmk) field must be 0. Set marks are not supported. Table 108. WRITE FILE MARKS Command 7 6 5 0 1 4 3 2 1 0 WSmk(0) Immed Operation Code (10h) Logical Unit Number (0) Reserved 2 : Count 4 5 Control The WRITE FILE MARKS command causes a sequence of file marks to be written at the current logical position. The number of file marks to be written is indicated in the Count field.
Chapter 3. Error Sense Information Sense Data For a description of Sense data, see “Sense Data Format” on page 60. Sense Data Management The drive maintains three types of Sense data: Current Sense The Sense data associated with the last command received from the initiator. Deferred Sense The Sense data from a command that has been reported as Good, but has generated sense data after being reported. This may be a command with the Immediate flag set or may be a buffered write.
Persistent Errors When errors occur that prevent tape operation, they are reported persistently until the problem is cleared. For medium-related errors (usually reported with a Sense Key of 3), the error is reported until the cartridge is successfully unloaded. For hardware-related errors (usually reported with a Sense Key of 4), the error is reported until the drive successfully performs a power-on self test.
Chapter 4. Sense Keys and Additional Sense Note: If temporary error reporting is enabled, many combinations of the Additional Sense Code and Additional Sense Code Qualifier (ASC/ASCQ) are possible. Table 109. Sense Keys and Additional Sense Sense Key Additional Sense (ASC/ASCQ) Explanation No Sense (0h) No Additional Sense (0000h) The flags in the sense data indicate the reason for the command failure.
Table 109. Sense Keys and Additional Sense (continued) Sense Key 90 Additional Sense (ASC/ASCQ) Explanation Medium Error Write Error (0C00h) (3h) A WRITE operation has failed. This is probably due to bad media, but may be related to hardware. Medium Error Unrecovered Read (3h) Error (1100h) A READ operation failed. This is probably due to bad media, but may be related to hardware.
Table 109. Sense Keys and Additional Sense (continued) Sense Key Additional Sense (ASC/ASCQ) Explanation Illegal Request (5h) Medium Removal Prevented (5302h) An UNLOAD command has failed to eject the tape because medium removal has been prevented. Illegal Request (5h) Bad Microcode Detected (8283h) The data transferred to the drive during a firmware upgrade is corrupt or incompatible with the drive hardware.
Table 109. Sense Keys and Additional Sense (continued) Sense Key Additional Sense (ASC/ASCQ) Volume EOM (0002h) Overflow (Dh) 92 Explanation A WRITE or WRITE FILE MARKS command failed because the physical end of tape was encountered. A READ or SPACE command encountered EOM. The EOM flag is set.
Chapter 5. Attachment Features Types of Interface Attachments The Ultrium Tape Drive communicates with servers that use SCSI parallel or Fibre Channel interfaces. The interfaces share certain tape LUN behaviors, but also possess unique features. This chapter describes the common and unique features of both types of interfaces.
Attention Check Condition from each initiator gets a Check Condition status, with Unit Attention sense data for the reset. However, other commands may not be processed until the internal state of the drive has been reset. Any commands that allow Disconnects and cannot be processed are accepted and queued until the drive is ready to process them. Those commands that do not allow Disconnects receive Busy status response.
Table 110. Abort Condition Handling (continued) Command Abort Processing RECEIVE DIAGNOSTIC RESULTS None. RELEASE UNIT The command completes. REPORT DENSITY SUPPORT None. REPORT LUNs None. REQUEST SENSE Sense data is discarded. RESERVE UNIT The command completes. REWIND The command completes. SEND DIAGNOSTIC Vendor unique.
Multi-initiator Support SCSI-attached drives support a maximum of two initiators on the same bus. Fibre-Channel-attached drives support a minimum of two initiators. The drive supports untagged queuing when operating with multiple initiators. If a command from one initiator is being processed when a command other than INQUIRY, REPORT LUNs, REQUEST SENSE, and TEST UNIT READY is received from a second initiator, the new command is queued.
Features of the SCSI Interface The Ultrium Tape Drive’s SCSI parallel interface features the following: v LUN identification v Bus parity errors v Disconnect strategy v Messages LUN Identification Identify messages are used to identify the LUN to which an initiator is connecting and to identify which LUN is reconnecting to an initiator. These are required. The LUN field in SCSI-2 commands is not used.
Messages Message Out Table 112. Supported Outbound Messages Name 98 Code Support Abort 06h An abort condition is generated (see “Abort Handling” on page 94). Bus Device Reset 0Ch A reset condition is generated (see “Abort Handling” on page 94). Extended Message 01h See “Unit Attention Conditions” on page 87 for extended message support. Identify 80h+ The Identify Out message is sent by the initiator to identify the Logical Unit to be accessed and to set Disconnect Privilege.
Message In Table 113. Supported Inbound Messages Name Code Support Command Complete 00h This message is sent by the drive at the end of the Status phase to indicate that a command is complete. Once the message is sent, the drive releases the bus and goes to Bus Free. Disconnect 04h This message is sent by the drive to indicate that it is about to disconnect from the bus and go to Bus Free. During a Data phase, it is always preceded by a Save Data Pointers message.
Extended Messages Table 114. Supported Extended Messages Name 100 Code Support Synchronous Data Transfer Request 01h The default mode is for the drive to never initiate a Synchronous data transfer negotiation. The initiator is expected to do so. Since this mode is most important at power-on, no SCSI method of changing this mode is provided. Instead, an internal method of changing this mode is provided (VPD or jumper setting).
Features of the Fibre Channel Interface | The Ultrium Tape Drive Model T200F (Fibre Channel drive) is an Arbitrated-Loop-only device (also known as an NL port). The drive supports Fibre Channel Arbitrated Loop (FC-AL) protocol, and uses Class 3 Service frames. The drive also supports both public (switch-attached) and private loops. The World Wide Node Name and Port Name used by an Ultrium Tape Drive follows the format of the Institute of Electrical and Electronics Engineers (IEEE).
102 Ultrium Internal Tape Drive and 3580 Ultrium Tape Drive: SCSI Reference
Appendix. Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements, or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
Trademarks The following terms are trademarks of International Business Machines Corporation in the United States or other countries or both: AIX AS/400 eserver IBM IBMLink iSeries OS/400 pSeries SP RS/6000 The following are U. S. trademarks of Hewlett-Packard Company, International Business Machines Corporation, and Seagate Technology: Linear Tape-Open LTO Ultrium Intel is a registered trademark of Intel Corporation in the United States, or other countries, or both.
106 Ultrium Internal Tape Drive and 3580 Ultrium Tape Drive: SCSI Reference
Index A H abort condition, handling 94 AS/400 device driver support 4 requirements for attaching tape drive to attaching tape drive to server 3 high voltage differential (HVD) SCSI interface 2 HP device driver support 4 requirements for attaching tape drive to 3 HVD interface 2 3 B bus parity errors, handling I 97 Information Exceptions Mode Page 35 INQUIRY command 5, 7 Intel-compatible servers device driver support 4 requirements for attaching tape drive to interface attachment 93 iSeries device dri
P persistent errors 88 PERSISTENT RESERVE IN command 5, 36 PERSISTENT RESERVE OUT command 5, 39 Post A self test diagnostic 73 Post B tape test diagnostic 74 Post C media test diagnostic 75 Post D Head Test diagnostic 76 power-on procedure 93 PREVENT/ALLOW MEDIUM REMOVAL command 5, 41 pSeries, requirements for attaching tape drive to 3 R READ ATTRIBUTE command 5, 43 READ BLOCK LIMITS command 5, 48 READ BUFFER command 5, 49 READ command 5, 42 Read Error Counters log 21 READ POSITION command 5, 52 Read-Write
Readers’ Comments — We’d Like to Hear from You Ultrium Internal Tape Drive Models T200 and T200F and 3580 Ultrium Tape Drive SCSI Reference Publication No.
WB1109-02 ___________________________________________________________________________________________________ Readers’ Comments — We’d Like to Hear from You Cut or Fold Along Line _ _ _ _ _ _ _Fold _ _ _and _ _ _Tape _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please _ _ _ _ _do _ _not _ _ staple _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold _ _ _and _ _ Tape ______ NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO.
Printed in the United States of America on recycled paper containing 10% recovered post-consumer fiber.
