1. DL manuals
  2. IBM
  3. Storage
  4. Ultrium 3580
  5. Reference Manual

IBM Ultrium 3580 Reference Manual

Manual is about: Ultrium Internal Tape Drive SCSI Reference

Summary of Ultrium 3580

  • Page 1

    Ultrium internal tape drive models t200 and t200f and 3580 ultrium tape drive scsi reference wb1109-02.

  • Page 3

    Ultrium internal tape drive models t200 and t200f and 3580 ultrium tape drive scsi reference wb1109-02.

  • Page 4

    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...

  • Page 5: Contents

    Contents tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vii preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . Xi organization . . . . . . . . . . . . . . . . . . . . . . . . . . Xi related publications . . . . . . . . . . . . . . . . . . . . . . . Xi chapter 1. Introduc...

  • Page 6

    Read buffer . . . . . . . . . . . . . . . . . . . . . . . . 49 error log buffer . . . . . . . . . . . . . . . . . . . . . . . 51 read position . . . . . . . . . . . . . . . . . . . . . . . . 52 receive diagnostic results . . . . . . . . . . . . . . . . . 53 release unit . . . . . . . . . . . . . . ....

  • Page 7

    How to send your comments . . . . . . . . . . . . . . . . . . . 104 trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . 105 index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 contents v.

  • Page 8

    Vi ultrium internal tape drive and 3580 ultrium tape drive: scsi reference.

  • Page 9: Tables

    Tables 1. Supported common commands . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Erase command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Inquiry command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Standard inquiry data valid lun . . . . . . . . ...

  • Page 10

    54. Parameter data for a partition list service action request . . . . . . . . . . . . . . . 45 55. Format for medium auxiliary memory attribute . . . . . . . . . . . . . . . . . . . . 45 56. Attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 57. Device common attrib...

  • Page 11

    110. Abort condition handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 111. Status codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 112. Supported outbound messages . . . . . . . . . . . . . . . . . . . . . . . . . 98 113. Supported inbound messages . . . . ...

  • Page 12

    X ultrium internal tape drive and 3580 ultrium tape drive: scsi reference.

  • Page 13: Preface

    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...

  • Page 14

    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...

  • Page 15: Chapter 1. Introduction

    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 ...

  • Page 16

    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 i...

  • Page 17

    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...

  • Page 18

    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 nee...

  • Page 19

    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. Suppor...

  • Page 20

    Table 1. Supported common commands (continued) command name operation code scsi class 1 scsi spec 2 page applicable conditions 3 rvc uat nrd wrp mfc dcc write attribute 8dh o spc-3 84 y y y y - y write buffer 3bh o spc-2 83 y y - - - - write file marks 10h m ssc 86 y y y y y y note 1: o=optional m=m...

  • Page 21

    Inquiry table 3. Inquiry command 7 6 5 4 3 2 1 0 0 operation code (12h) 1 logical unit number (0) reserved evpd 2 page code 3 reserved 4 allocation length 5 control the inquiry command instructs the drive to return data about itself to the initiator. If the enable vital product data (evpd) flag is c...

  • Page 22

    Standard inquiry data valid lun table 4. Standard inquiry data valid lun 7 6 5 4 3 2 1 0 0 peripheral qualifier (000b) peripheral device type (01h) 1 rmb(1) device-type modifier (0) 2 iso version (0) ecma version (0) version (3) 3 aenc(0) obsolete naca(0) hisup(0) response data format (2) 4 addition...

  • Page 23

    Standard inquiry data invalid lun table 5. Standard inquiry data invalid lun 7 6 5 4 3 2 1 0 0 peripheral qualifier (011b) peripheral device type (1fh) 1 rmb(0) device-type modifier (0) 2 iso version (0) ecma version (0) version (3) 3 aenc(0) obsolete naca(0) hisup(0) response data format (2) 4 addi...

  • Page 24

    Supported vital product data page table 6. Supported vital product data inquiry page 7 6 5 4 3 2 1 0 0 peripheral qualifier (000b) peripheral device type (01h) 1 page code (00h) 2 reserved 3 page length (6h) 4 supported vital product data page code (00h) 5 vendor-unique page code (03h) 6 unit serial...

  • Page 25

    Device identification page table 8. Device identification inquiry page 7 6 5 4 3 2 1 0 0 peripheral qualifier (000b) peripheral device type (01h) 1 page code (83h) 2 reserved 3 page length (n-3) 4 : n identification descriptors the device identification descriptor page contains a series of device id...

  • Page 26

    The fibre channel identification descriptor is returned only on fibre-channel- attached devices. The format is given in table 10. Table 10. Fibre channel identification descriptor 7 6 5 4 3 2 1 0 0 reserved code set (1h) 1 reserved association type ( 00b) identifier type (3h) 2 reserved 3 identifier...

  • Page 27

    Drive component revision levels pages table 11. Drive component revision levels pages 7 6 5 4 3 2 1 0 0 peripheral qualifier (000b) peripheral device type (01h) 1 page code (c0h) 2 reserved 3 page length (27h) 4 : 15 component (cccccccccccc) 16 : 22 version (rrr.Vvv) 23 : 30 date (yyyymmdd) 31 : 42 ...

  • Page 28

    Load/unload table 12. Load/unload command 7 6 5 4 3 2 1 0 0 operation code (1bh) 1 logical unit number (0) reserved immed 2 reserved 3 reserved 4 reserved eot(0) reten(0) load 5 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 the...

  • Page 29

    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 (i...

  • Page 30

    Log select table 14. Log select command 7 6 5 4 3 2 1 0 0 operation code (4ch) 1 logical unit number (0) reserved pcr sp(0) 2 pc reserved 3 reserved 4 reserved 5 reserved 6 reserved 7 parameter list length 8 9 control the log select command causes log data on the drive to be reset to its default val...

  • Page 31

    Log sense table 15. Log sense command 7 6 5 4 3 2 1 0 0 operation code (4dh) 1 logical unit number (0) reserved ppc(0) sp(0) 2 pc page code 3 reserved 4 reserved 5 parameter pointer (0) 6 7 allocation length 8 9 control the log sense command causes log data to be sent to the initiator. If the page c...

  • Page 32

    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 6 5 4 3 2 1 0 0 reserved page code 1 reserved 2 page length 3 the page code is a byte value...

  • Page 33

    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 34

    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. Write error log parameters pa...

  • Page 35

    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. Read error log parameters param...

  • Page 36

    Sequential access device log the sequential access device log page is 0ch. Table 21. Sequential access device log parameters parameter description length du lp lbin 0h write data bytes received, before compression 8 0 0 0 1h write data bytes received, after compression 8 0 0 0 2h read data bytes sen...

  • Page 37

    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...

  • Page 38

    Table 22. Tapealert log parameters (continued) parameter description type du lp lbin 38 predictive failure critical 1 0 0 39 diagnostics required 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 clear...

  • Page 39

    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. Param...

  • Page 40

    Mode select table 26. Byte mode select command 7 6 5 4 3 2 1 0 0 operation code (15h) 1 logical unit number (0) pf reserved sp(0) 2 reserved 3 reserved 4 parameter list length 5 control table 27. Byte mode select command 7 6 5 4 3 2 1 0 0 operation code (55h) 1 logical unit number (0) pf reserved sp...

  • Page 41

    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 4 3 2 1 0 0 operation code (1ah) 1 logical unit number (0) reserved dbd reserved 2 pc page code 3 reserved 4 allocation length 5 control table 29. Byte mode sense command 7 6 5 4...

  • Page 42

    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 0 : 3 mode parameter header 4 : 11 mode block descr...

  • Page 43

    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 spe...

  • Page 44

    Read-write error recovery page table 34. Read-write error recovery page 7 6 5 4 3 2 1 0 0 ps (0) reserved page code (01h) 1 additional page length (0ah) 2 reserved tb (0) reserved eer(1) per dte(0) dcr(0) 3 read retry count (ffh) 4 reserved 5 reserved 6 reserved 7 reserved 8 write retry count (ffh) ...

  • Page 45

    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 fiel...

  • Page 46

    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 ...

  • Page 47

    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...

  • Page 48

    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. Fibre channel port control page 7 6 5 4 3 2 1 0 0 ps (0) reserved page code (19h) 1 page length (0eh) 2 reserved 3 dtfd (0) plpb (0) ddis (0)...

  • Page 49

    Information exceptions mode page table 40. Information exceptions mode page 7 6 5 4 3 2 1 0 0 ps (0) reserved page code (1ch) 1 page length (0a) 2 perf (0) reserved dexcept test reserved logerr(0) 3 reserved mrie (3) 4 : 7 interval timer (0) 8 : 11 report count (0) the information exceptions mode pa...

  • Page 50

    Persistent reserve in table 41. Persistent reserve in command 7 6 5 4 3 2 1 0 0 operation code (5eh) 1 reserved service action 2 reserved 3 reserved 4 reserved 5 reserved 6 reserved 7 : 8 allocation length 9 control the persistent reserve in command is used for reservation management to show what ty...

  • Page 51

    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 : 3 generation 4 : 7 additional length 8 : 15 first reservation key 16 : n additional reservation keys generation is a counter for persistent ...

  • Page 52

    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 : 7 reservation key 8 : 11 scope-specific address (0) 12 reserved 13 scope (0h) type 14 : 15 ...

  • Page 53

    Persistent reserve out table 45. Persistent reserve out command 7 6 5 4 3 2 1 0 0 operation code (5fh) 1 reserved service action 2 scope ( 0) type 3 reserved 4 reserved 5 reserved 6 reserved 7 : 8 parameter list length (18h) 9 control the persistent reserve out command is used for reservation manage...

  • Page 54

    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 : 7 reservation key 8 : 15 service action reservation key 16 : 19 scope-specific address (0) 20 reserved aptpl (0) 21 reserved 22 : 23 obsolete (0) any value is allowed...

  • Page 55

    Prevent/allow medium removal table 47. Prevent/allow medium removal command 7 6 5 4 3 2 1 0 0 operation code (1eh) 1 logical unit number (0) reserved 2 reserved 3 reserved 4 reserved prevent 5 control the prevent/allow medium removal command is used to prevent accidental removal of the medium while ...

  • Page 56

    Read table 48. Read command 7 6 5 4 3 2 1 0 0 operation code (08h) 1 logical unit number (0) reserved sili fixed 2 : 4 transfer length 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 singl...

  • Page 57

    Read attribute table 49. Read attribute command 7 6 5 4 3 2 1 0 0 operation code (8ch) 1 reserved (0) service action 2 : 3 reserved 4 reserved 5 volume number (0) 6 reserved 7 partition number (0) 8 : 9 first attribute id 10 : 13 allocation length 14 reserved 15 control until the scsi primary comman...

  • Page 58

    Table 51. Parameter data for an attribute values service action request 7 6 5 4 3 2 1 0 0 : 3 available data (n-3) 4 : x attribute #1 m : n attribute #y table 52 describes the format of the data returned for an attribute list service action request. Table 52. Parameter data for an attribute list ser...

  • Page 59

    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 : 1 available data (2) 2 first partition number (0) 3 number of partitions available (1) medium auxiliary memory attr...

  • Page 60

    Table 57 describes device common attributes. All device common attributes are read only. Table 57. Device common attributes id attribute name number of bytes format 0000h remaining capacity in partition 8 binary 0001h maximum capacity in partition 8 binary 0002h tapealert flags 8 binary 0003h load c...

  • Page 61

    Table 59 describes the medium common attributes. Table 59. Medium common attributes id attribute name number of bytes format 0400h medium manufacturer 8 ascii 0401h medium serial number 32 ascii 0402h medium length 4 binary 0403h medium width 4 binary 0404h assigning organization 8 ascii 0405h mediu...

  • Page 62

    Read block limits table 61. Read block limits command 7 6 5 4 3 2 1 0 0 operation code (05h) 1 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 bl...

  • Page 63

    Read buffer table 63. Read buffer command 7 6 5 4 3 2 1 0 0 operation code (3ch) 1 logical unit number (0) reserved mode 2 buffer id 3 : 5 buffer offset 6 : 8 allocation length 9 control the read buffer command reads data from the memory on the drive and sends it to the initiator. Modes 000b, 010b a...

  • Page 64

    Table 65. Drive buffers supported buffers id offset boundary main data 0 4 dump data (read only) 1 4 test 2 4 vpd 3 4 firmware 4 4 cartridge memory (read only) 5 4 error log (read only) 6 4 50 ultrium internal tape drive and 3580 ultrium tape drive: scsi reference.

  • Page 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 : 3 time stamp 4 entry number 5 error code 6 fsc 1st text 7 8 fsc 1st data 9 10 fsc 2nd text 11 12 fsc 2nd data 13 14 : 21 cartridge serial number 22 : 27 e...

  • Page 66

    Read position table 67. Read position command 7 6 5 4 3 2 1 0 0 operation code (34h) 1 logical unit number (0) reserved bt(0) 2 reserved 3 reserved 4 reserved 5 reserved 6 reserved 7 reserved 8 reserved 9 control the read position command returns current position information to the initiator. The da...

  • Page 67

    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 partiti...

  • Page 68

    Release unit table 70. Byte release unit command 7 6 5 4 3 2 1 0 0 operation code (17h) 1 logical unit number (0) 3rdpty third party device id (0) element 2 reservation identification 3 reserved 4 allocation length (0) 5 control table 71. Byte release unit command 7 6 5 4 3 2 1 0 0 operation code (5...

  • Page 69

    Report density support table 72. Report density support command 7 6 5 4 3 2 1 0 0 operation code (44h) 1 logical unit number (0) reserved media 2 reserved 3 reserved 4 reserved 5 reserved 6 reserved 7 allocation length 8 9 control the report density support command returns details about the tape for...

  • Page 70

    The header is followed by one or more report density support descriptor blocks with the format in table 74. Table 74. Report density support descriptor block 7 6 5 4 3 2 1 0 0 primary density code 1 secondary density code 2 wrtok dup(0) deflt reserved 3 reserved 4 reserved 5 : 7 bits per mm 8 media ...

  • Page 71

    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) 95367 assigning organization lto-cve dens...

  • Page 72

    Report luns table 76. Report luns command 7 6 5 4 3 2 1 0 0 operation code (a0h) 1 reserved 2 reserved 3 reserved 4 reserved 5 reserved 6 : 9 allocation length 10 reserved 11 control the server uses this command to retrieve information about the logical units that the drive supports. The allocation ...

  • Page 73

    Request sense table 78. Request sense command 7 6 5 4 3 2 1 0 0 operation code (03h) 1 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. Command support 59.

  • Page 74

    Sense data format table 79. Sense data format 7 6 5 4 3 2 1 0 0 valid error code 1 segment number (0) 2 file mark eom ili reserved sense key 3 : 6 information 7 additional sense length 8 : 11 command specific information 12 additional sense code 13 additional sense code qualifier 14 field replaceabl...

  • Page 75

    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 ind...

  • Page 76

    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 b...

  • Page 77

    Reserve unit table 80. Byte reserve unit command 7 6 5 4 3 2 1 0 0 operation code (16h) 1 logical unit number (0) 3rdpty(0) third party device id (0) reserved 2 reserved 3 reserved 4 reserved 5 control table 81. Byte reserve unit command 7 6 5 4 3 2 1 0 0 operation code (56h) 1 logical unit number (...

  • Page 78

    Rewind table 82. Rewind command 7 6 5 4 3 2 1 0 0 operation code (01h) 1 logical unit number (0) reserved immed 2 reserved 3 reserved 4 reserved 5 control 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 ...

  • Page 79

    Send diagnostic table 83. Send diagnostic command 7 6 5 4 3 2 1 0 0 operation code (1dh) 1 logical unit number (0) pf reserved selftest devofl unitofl 2 reserved 3 parameter list length 4 5 control self-test for the self-test diagnostic, the cdb values should be set as follows: v pf - 1 v selftest -...

  • Page 80

    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. Sim data structure 7 6 5 4 3 2 1 0 0 page code (31h) 1 reserved 2 page length (0044h) 3 4 parameter code (0000h) 5 6 parameter cont...

  • Page 81

    Table 84. Sim data structure (continued) 7 6 5 4 3 2 1 0 42 : 45 product id (8000h) 46 : 48 vendor id “ibm” 49 plant of manufacture 50 51 product id3 ’-’ 52 : 63 serial number 64 : 71 device type//dev sim_message_type the sim message code may be one of six values: v ’00’=no message v ’41’=device deg...

  • Page 82

    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 ...

  • Page 83

    Table 85. Mim data structure (continued) 7 6 5 4 3 2 1 0 30 : 33 error code 34 : 39 volume id volume serial number 40 volume id flag 41 reserved 42 : 45 product id (8000h) 46 : 48 vendor id “ibm” 49 plant of manufacture 50 51 product id3 ’-’ 52 : 63 serial number 64 : 71 device type the mim message ...

  • Page 84

    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...

  • Page 85

    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. T...

  • Page 86

    Write dump to cartridge table 87. Write dump to cartridge send diagnostic parameter data 7 6 5 4 3 2 1 0 0 page code (80h) 1 reserved 2 page length (0004h) 3 4 diagnostic id (0161h) 5 6 flags (0000000b) cartridge required (1b) 7 reserved table 88. Write dump to cartridge receive diagnostic parameter...

  • Page 87

    Post a self test diagnostic table 89. Post a self test send diagnostic parameter data 7 6 5 4 3 2 1 0 0 page code (80h) 1 reserved 2 page length (0004h) 3 4 diagnostic id (0100h) 5 6 flags (0000000b) cartridge required (bx) 7 reserved table 90. Post a self test receive diagnostic parameter data 7 6 ...

  • Page 88

    Post b tape test diagnostic table 91. Post b tape test send diagnostic parameter data 7 6 5 4 3 2 1 0 0 page code (80h) 1 reserved 2 page length (0004h) 3 4 diagnostic id (0101h) 5 6 flags (0000000b) cartridge required (1b) 7 reserved table 92. Post b tape test receive diagnostic parameter data 7 6 ...

  • Page 89

    Post c media test diagnostic table 93. Post c media test send diagnostic parameter data 7 6 5 4 3 2 1 0 0 page code (80h) 1 reserved 2 page length (0004h) 3 4 diagnostic id (0102h) 5 6 flags (0000000b) cartridge required (1b) 7 reserved table 94. Post c media test receive diagnostic parameter data 7...

  • Page 90

    Post d head test diagnostic table 95. Post d head test send diagnostic parameter data 7 6 5 4 3 2 1 0 0 page code (80h) 1 reserved 2 page length (0004h) 3 4 diagnostic id (0103h) 5 6 flags (0000000b) cartridge required (1b) 7 reserved table 96. Post d head test receive diagnostic parameter data 7 6 ...

  • Page 91

    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. Tabl...

  • Page 92

    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 diagnos...

  • Page 93

    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 2 1 0 0 page code (80h) 1 reserved 2 page length (n - 4) 3 4 diagnostic id (0191h) 5 6 flags (0) 7 reserved 8 reserved diagnostic...

  • Page 94

    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. Reset drive diagnostic pa...

  • Page 95

    Space table 101. Space command 7 6 5 4 3 2 1 0 0 operation code (11h) 1 logical unit number (0) reserved code 2 : 4 count 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 an...

  • Page 96

    Test unit ready table 102. Test unit ready command 7 6 5 4 3 2 1 0 0 operation code (00h) 1 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 4 3 2 1 0...

  • Page 97

    Write table 104. Write command 7 6 5 4 3 2 1 0 0 operation code (0ah) 1 logical unit number (0) reserved fixed 2 : 4 transfer length 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 ...

  • Page 98

    Write attribute table 105. Write attribute command 7 6 5 4 3 2 1 0 0 operation code (8dh) 1 : 4 reserved 5 volume number (0) 6 reserved 7 partition number (0) 8 : 9 reserved 10 : 13 allocation length 14 reserved 15 control until the scsi primary commands-3 (spc-3) is published, refer to scsi proposa...

  • Page 99

    Write buffer table 107. Write buffer command 7 6 5 4 3 2 1 0 0 operation code (3bh) 1 logical unit number (0) reserved mode 2 buffer id 3 : 5 buffer offset 6 : 8 parameter list length 9 control the write buffer command transfers data into the memory on the drive for the purpose of diagnostics, tests...

  • Page 100

    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 4 3 2 1 0 0 operation code (10h) 1 logical unit number (0) reserved wsmk(0) immed 2 : 4 count 5 control the write file marks command causes a sequence of file marks to b...

  • Page 101

    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 ...

  • Page 102

    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 r...

  • Page 103

    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 ...

  • Page 104

    Table 109. Sense keys and additional sense (continued) sense key additional sense (asc/ascq) explanation medium error (3h) write error (0c00h) a write operation has failed. This is probably due to bad media, but may be related to hardware. Medium error (3h) unrecovered read error (1100h) a read oper...

  • Page 105

    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)...

  • Page 106

    Table 109. Sense keys and additional sense (continued) sense key additional sense (asc/ascq) explanation volume overflow (dh) eom (0002h) 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. 92 ultr...

  • Page 107

    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 ...

  • Page 108

    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 q...

  • Page 109

    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 d...

  • Page 110

    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 ...

  • Page 111

    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 whic...

  • Page 112

    Messages message out table 112. Supported outbound messages name 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 pa...

  • Page 113

    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 s...

  • Page 114

    Extended messages table 114. Supported extended messages name 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 met...

  • Page 115

    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 (swit...

  • Page 116

    102 ultrium internal tape drive and 3580 ultrium tape drive: scsi reference.

  • Page 117: Appendix. Notices

    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...

  • Page 118

    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 produ...

  • Page 119

    Trademarks the following terms are trademarks of international business machines corporation in the united states or other countries or both: aix iseries as/400 os/400 eserver pseries ibm sp ibmlink rs/6000 the following are u. S. Trademarks of hewlett-packard company, international business machine...

  • Page 120

    106 ultrium internal tape drive and 3580 ultrium tape drive: scsi reference.

  • Page 121: Index

    Index a abort condition, handling 94 as/400 device driver support 4 requirements for attaching tape drive to 3 attaching tape drive to server 3 b bus parity errors, handling 97 c capacity 1 common commands, supported 5 compressed capacity 1 current sense data 87 d data compression log 25 data compre...

  • Page 122

    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, requi...

  • Page 123

    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 overall, how satisfied are you with the information in this book? Very satisfied satisfied neutral dissatisfied very dissatisfied over...

  • Page 124: Business Reply Mail

    Readers’ comments — we’d like to hear from you wb1109-02 wb1109-02 cut or fold along line cut or fold along line fold and tape please do not staple fold and tape 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 ...

  • Page 126

    Printed in the united states of america on recycled paper containing 10% recovered post-consumer fiber..