1. Manuals
  2. Brands
  3. Spectra Logic Manuals
  4. Storage
  5. Spectra 12K
  6. User manual

Spectra Logic Spectra 12K User Manual

Gator library
Hide thumbs Also See for Spectra 12K:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Installation Manual
Gator Library
Developer Guide
• Spectra
• Spectra
• Spectra
®
12K Library
®
20K Library
®
64K Library
P.N. 90910850 Revision D

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Spectra 12K and is the answer not in the manual?

Questions and answers

Related Manuals for Spectra Logic Spectra 12K

Summary of Contents for Spectra Logic Spectra 12K

  • Page 1 Gator Library Developer Guide ® • Spectra 12K Library ® • Spectra 20K Library ® • Spectra 64K Library P.N. 90910850 Revision D...

  • Page 2: Notices

    In no event will Spectra Logic be liable for any loss of profits, loss of business, loss of use or data, interruption of business, or for indirect, special, incidental or consequential damages of any kind, even if Spectra Logic has been advised of the possibility of such damages arising from any defect or error.

  • Page 3: License Agreement

    License Agreement This program is copyrighted and licensed (not sold). If you are not willing to be bound by the terms of this License Agreement, you should promptly return the package, and you will receive a refund of your money. This License Agreement represents the entire agreement concerning the program between you and Spectra Logic Corporation (referred to as “Licensor”), and it supersedes any prior proposal, representation, or understanding between the parties.

  • Page 4: Table Of Contents

    Contents Notices ............2 License Agreement .
  • Page 5 Chapter 5. Inquiry—12h Command Description ..........34 Command Response .
  • Page 6 Chapter 12. Receive Diagnostic Results—1Ch Command Description ..........76 Supported Diagnostics Pages .
  • Page 7 Chapter 18. Error Reporting Sense Keys ........... . .106 Sense Codes and Qualifiers .

  • Page 8: List Of Tables

    List of Tables Chapter 1. Introduction Chapter 2. SCSI Basics Table 2-1: SCSI Bus Phases ......... 18 Table 2-2: Supported Message Codes .
  • Page 9 Chapter 5. Inquiry—12h Table 5-1: Inquiry Command–12h ........34 Table 5-2: Inquiry Command Field Values .
  • Page 10 Table 11-10: Storage Element Fields ........
  • Page 11 Table 12-7: Element Type Descriptor Values ......81 Table 12-8: Enclosure Status Page–02h (Spectra 12K and Spectra 20K Libraries) . . 82 Table 12-9: Enclosure Status Page–02h (Spectra 64K Libraries) .
  • Page 12 Table 16-5: Supported Diagnostic Page Field Values ..... . .100 Table 16-6: Enclosure Services Control Page Format (for Spectra 12K and Spectra 20K Libraries) .
  • Page 13 List of Tables Appendix A. Extended Copy—83h—143r1 Specifications Table A-1: Extended Copy Command (143r1 Specifications) ....121 Table A-2: Extended Copy Parameter List .......122 Table A-3: Extended Copy Descriptor Codes .
  • Page 14 List of Tables Appendix B. Extended Copy—83h—SPC2 Specifications Table B-2: Extended Copy Parameter List .......161 Table B-3: Extended Copy Descriptor Type Codes .
  • Page 15 Appendix C. Receive Copy Results—84h Table C-2: Receive Copy Results Service Action Codes .....197 Table C-3: Parameter Data for the Copy Status Service Action ....198 Table C-4: Copy Status Status Values .

  • Page 16: Chapter 1. Introduction

    These libraries can be configured as one or more logical libraries; the Spectra 12K and 20K libraries have a maximum of four logical libraries, and the Spectra 64K library has a maximum of 16 logical libraries.

  • Page 17: Related Publications

    Related Publications The following publications are also available from Spectra Logic: • Spectra 12K Library User Guide (P.N. 90910889) describes the installation and operation of the Spectra 12K library. • Spectra 20K Library User Guide (P.N. 90920001) describes the installation and operation of the Spectra 20K library.

  • Page 18: Chapter 2. Scsi Basics

    SCSI Basics SCSI-2 Interface Basics SCSI Bus Communications Bus Phases The SCSI interface can be in any one of eight states or phases while communications are occurring. The SCSI bus can only be in one phase at a time. The SCSI bus phases and a brief description of each phase are listed in Table 2-1.
  • Page 19 “element” to identify any place where a unit of media can reside, such as in storage slots or a drive. Each element has a unique numerical address. The four types of elements defined in the SCSI standard (and how they apply to Gator libraries) are as follows: •...

  • Page 20: Scsi Messages

    SCSI Messages The SCSI-2 messaging system defines the communication protocol for exchanges between an initiator and a target. Table 2-2 on page 21 lists supported message codes for Gator libraries configured with S-QIPs and L-QIPs. Note: SCSI-2 requires devices to support the IDENTIFY message. The following steps complete the transfer of data between the host computer (initiator) and the library (target): 1.

  • Page 21: Table 2-2: Supported Message Codes

    SCSI-2 Message Codes Table 2-2 lists messages supported by Gator libraries configured for S-QIP and L-QIP. Note: Gator libraries do not support any extended message, such as a wide data transfer request, nor any vendor-specific messages. This does not affect which messages the installed tape drives will support, as those messages are transmitted directly to the drives.

  • Page 22: Table 2-3: Identify Message Format

    Disconnect (04h) The library sends the DISCONNECT message to an initiator to request a pause in the present I/O connection; the library releases the BSY signal and disconnects from the SCSI bus. The disconnect implies that the library will later reconnect to the initiator to complete the paused I/O process.

  • Page 23: Scsi Commands

    SCSI Commands This section describes fundamental concepts and terms common to most SCSI commands. It describes the SCSI command formats, command field definitions, and command status bytes. Descriptions of individual commands and instructions on how to use them with Gator libraries are contained in their own chapters in this guide.

  • Page 24: Table 2-5: 10-Byte Cdb

    Table 2-5: 10-Byte CDB Bits Byte Reserved (LUN) (MSB) (MSB) Table 2-6: 12-Byte Command Format Bits Byte Reserved (MSB) (MSB) Chapter 2. SCSI Basics Operation Code Service Action LOGICAL BLOCK ADDRESS (if required) Reserved TRANSFER LENGTH (if required) PARAMETER LIST LENGTH (if required) ALLOCATION LENGTH (if required) CONTROL Operation Code...

  • Page 25: Table 2-7: 16-Byte Command Format

    Table 2-7: 16-Byte Command Format Bits Byte Reserved (MSB) (MSB) (MSB) Command Field Definitions Operation Code (byte 00, bits 7-0) The operation code for the command descriptor block is a group code field and a command code field. The three-bit group code field provides for eight groups of command codes.

  • Page 26: Table 2-9: Group Codes

    Table 2-9: Group Codes Group Code 1h-2h 6h-7h The five-bit command code field provides for 32 command codes in each group. A total of 256 possible operation codes exist. Specific operation codes are described in detail in the sections for the individual SCSI commands. Logical Unit Number (Byte 1, Bits 7-5) The logical unit number (LUN) for the library will usually be 0, particularly over the SCSI interface.

  • Page 27: Table 2-10: Control Byte

    Control Byte (varies, see specific command) The control field is the last byte of every CDB. The control field is defined below. Table 2-10: Control Byte Bits Byte Final Byte of Command Vendor-Unique Vendor Unique The Vendor-Unique fields, if used, are defined for each specific command.

  • Page 28: Table 2-11: Status Byte Format

    Status Byte Codes The table below describes the Gator library status byte format: Table 2-11: Status Byte Format Bits Byte Reserved Status Byte Field Descriptions Reserved The reserved fields are reserved for future use. Status Byte Code See Table 2-12 for Status Byte Code field descriptions. Table 2-12: Status Byte Code Field Descriptions 0 x 0 0 x 2...
  • Page 29 The CHECK CONDITION status is reported immediately after a command is completed unless the library is disconnected from the SCSI bus. If the library is disconnected, CHECK CONDITION status is reported to the initiator immediately following the reconnect process. CHECK CONDITION status is reported upon receipt of a command in the following cases: •...
  • Page 30 HARDWARE ERROR (04h) This is returned to the initiator when the library detects a non- recoverable hardware failure while performing a command or during a self-test. ILLEGAL REQUEST (05h) An ILLEGAL REQUEST sense key is returned to the initiator when the library detects an illegal parameter in the command descriptor block or in the additional parameters supplied as data.

  • Page 31: Chapter 3. Initialize Element Status-07H

    Initialize Element Status—07h Command Description The INITIALIZE ELEMENT STATUS command instructs Gator libraries to take an inventory of their elements. This includes reading the bar codes of the cartridges. This information can be returned using the READ ELEMENT STATUS (B8h) command. Note: Gator libraries automatically perform and store an element inventory on power-up, and each time the front door is opened...

  • Page 32: Command Response

    Chapter 3. Initialize Element Status—07h Command Response No data is expected to be returned in Gator libraries when the INITIALIZE ELEMENT STATUS command is issued. To get information on the status of elements, issue a READ ELEMENT STATUS command.

  • Page 33: Chapter 4. Initialize Element Status With Range-E7H

    Initialize Element Status With Range—E7h Command Description INITIALIZE ELEMENT STATUS WITH RANGE is a vendor-specific command for other vendors’ tape libraries. It is included in the Gator libraries’ command set to support the library’s emulation of other libraries. When the library receives this command, it performs as though it had received the INITIALIZE ELEMENT STATUS (07h) command, ignoring any additional parameters supplied with this command.

  • Page 34: Chapter 5. Inquiry-12H

    Inquiry—12h Command Description The INQUIRY command instructs the library to send information regarding its parameters to the initiator. The table below shows the CDB for the INQUIRY command. Table 5-1: Inquiry Command–12h Bits Byte Logical Unit Number Operation Code (12h) Reserved Page Code Reserved...

  • Page 35: Table 5-2: Inquiry Command Field Values

    Table 5-2: Inquiry Command Field Values Values Field Name Allowed Logical Unit Number EVPD (Enable Vital Product Data) Page Code Allocation Length 00-FFh Chapter 5. Inquiry—12h Meaning This is ignored in SCSI-2. Requests the library to return only the standard Inquiry Data page. (Note: If the EVPD=0, then the Page Code must be 0 also.) Requests that the library return the Page Code page.

  • Page 36: Command Response

    Command Response If the EVPD bit in the INQUIRY command is 0, the library returns standard INQUIRY data, as shown in Table 5-3. Table 5-3: Standard Inquiry Data Format Bits Byte Peripheral Qualifier ISO Version AENC TRMIOP 05-06 RelAdr WBus32 (MSB) 08 -15 (MSB)

  • Page 37: Table 5-4: Standard Inquiry Data Field Values

    Table 5-4: Standard Inquiry Data Field Values Value Field Name Returned 000b Peripheral Qualifier 011b Peripheral Device Type Device Type Modifier ISO Version ECMA Version 000b ANSI-approved Version 010b AENC TrmIOP Response Data Format Additional Length RelAdr WBus 32 WBus 16 Sync Linked CmdQue...

  • Page 38: Table 5-5: Supported Pages Page

    Table 5-4: Standard Inquiry Data Field Values Value Field Name Returned Product Identification GATOR Product Revision Level Variable Patch Level Variable BCPres The Vendor Identification, Product Identification, Product Revision Level, and Patch Level data fields all return ASCII-format data. Unused bytes are filled with space characters (20h) left-justified.

  • Page 39: Table 5-6: Serial Number Page

    Table 5-6: Serial Number Page Bits Byte Peripheral Qualifier 04-23 Table 5-7: Serial Number Page Field Values Value Field Name Returned Peripheral Qualifier 000b Peripheral Device Type Page Code Page Length Varies Serial Number Varies The serial number can be up to 20 characters in length. Chapter 5.

  • Page 40: Table 5-8: Library Identification Page

    Table 5-8: Library Identification Page Bits Byte Peripheral Qualifier Reserved Reserved 8 - 15 16 - 31 32 - 51 56 - 63 Applicable only to Fibre Channel, Gigabit Ethernet, NDMP, and iSCSI Gator libraries. These will not be reported on SCSI (S-QIP and L-QIP) interface systems.

  • Page 41: Table 5-9: Serial Number Page Field Values

    Table 5-9: Serial Number Page Field Values Value Field Name Returned Peripheral Qualifier 000b Peripheral Device Type Page Code Page Length Code Set Identifier Type Identifier Length Serial Number Variable Vendor Identification SPECTRA Product Identification GATOR World Wide Name Variable The serial number can vary between two and seven digits in length.

  • Page 42: Chapter 6. Mode Select-15H

    Mode Select—15h Command Description The MODE SELECT command allows the initiator to change device parameters of the library. An initiator uses these parameters to configure the library after power-up or a bus device reset message. The library parameters that can be set with MODE SELECT are as follows: •...

  • Page 43: Table 6-1: Mode Select Command-15H

    To change parameter values, send a MODE SELECT command, followed by a mode parameter list in the Data Out phase. Table 6-1 shows the CDB for the MODE SELECT command. Table 6-1: Mode Select Command–15h Bits Byte Logical Unit Number–0h Table 6-2: Mode Select Command Field Values Values Field Name...
  • Page 44 Mode Parameter Lists Following the command block, in the data out phase, the initiator sends a parameter list containing the new parameter values of the library. This parameter list has the same format as the data the library returns to a MODE SENSE command, with the restriction that only one type of mode page per command is allowed for MODE SELECT.

  • Page 45: Chapter 7. Mode Sense-1Ah

    Mode Sense—1Ah Command Description The MODE SENSE command asks the library to report its operating mode parameters to the initiator. The parameters are returned in mode pages. The library supports the following pages: • Tape alert—1Ch • Element address assignments—1Dh •...

  • Page 46: Table 7-2: Mode Sense Command Field Values

    Table 7-2: Mode Sense Command Field Values Field Name Values Allowed DBD (Disable Block 0 or 1 Descriptors) Page Control Page Code Allocation Length 00-FFh Chapter 7. Mode Sense—1Ah Meaning The library does not return block descriptors even if requested to do so. This is not an error condition.

  • Page 47: Command Response

    Command Response If all mode pages are requested, the library returns 66 bytes of mode sense data to the initiator, structured as follows: • 12 bytes of tape alert • 4 bytes of parameter list header data • 20 bytes of element address assignments •...

  • Page 48: Table 7-4: Tape Alert Page Parameters-1Ch

    Tape Alert Page 1Ch This returns the Tape Alert configuration. (Sets the configuration when sent with MODE SELECT.) Table 7-4: Tape Alert Page Parameters–1Ch Bits Byte Perf Reserved Chapter 7. Mode Sense—1Ah Page Code (1Ch) Page Length (0Ah) Reserved DExcpt Interval Timer Report Count / Test Flag Number Test...

  • Page 49: Table 7-5: Tape Alert Page Fields

    Table 7-5: Tape Alert Page Fields Field Name Values Allowed Perf DExcpt Test LogErr Used to indicate the method of reporting INFORMATIONAL EXCEPTION conditions. MRIE Interval Timer 1 - FFFFFFFEh FFFFFFFFh Chapter 7. Mode Sense—1Ah Meaning INFORMATIONAL EXCEPTION operations that can cause delays are acceptable.
  • Page 50 Table 7-5: Tape Alert Page Fields Field Name Values Allowed If Test Bit is 0 Report Count/ Test Flag If Test Bit is not 0 Number If Test Bit is 1, -64 to 64, or 32677 Chapter 7. Mode Sense—1Ah Meaning There is no limit on the number of times the target will report the INFORMATIONAL EXCEPTION condition.

  • Page 51: Table 7-6: Element Address Assignments Page-1Dh

    Page Code–1Dh Parameter List Length (following this byte)(12h) Medium Transport Element Address (Default=02C3h) Number of Medium Transport Elements (01h for all Gator Libraries) First Storage Element Address (Default=001Eh) Number of Storage Elements (Depends on Partition Size) First Import/Export Element Address (Default=0000h)

  • Page 52: Table 7-7: Transport Geometry Parameter Page-1Eh

    Transport Geometry Parameters The transport geometry parameter page identifies that the tape picker does not rotate media. Table 7-7: Transport Geometry Parameter Page–1Eh Bits Byte PS–0 Reserved Note: These values cannot be modified with the MODE SELECT command. The Rotate (byte 02, bit 0) field identifies the ability of the picker to handle two-sided media. The library uses only one-sided media, so the value returned for this bit is 0.

  • Page 53: Table 7-8: Device Capabilities Fields Format-1Fh

    Device Capabilities The device capabilities mode page is described in the table below. Table 7-8: Device Capabilities Fields Format–1Fh Bits Bytes PS–0 Reserved Reserved (0) Reserved (0) Reserved (0) Reserved (0) Reserved (0) 08 - 11 Reserved (0) The cells for Byte 06 indicate values with QUEUED UNLOADS turned OFF. Note: When using QUEUED UNLOADS (default operating mode), importing via MOVE commands is inhibited.
  • Page 54 DT: Data transfer element (tape drive) IE: Import/export element ST: Storage element (magazine slot) MT: Medium transport element (tape picker) Stor: A value of 1 in a StorXX bit indicates media can be stored at elements of type XX.

  • Page 55: Table 7-9: Vendor-Specific Parameters-00H

    Vendor-Specific Parameters The library has vendor-specific parameters which report and control the functions of the bar code scanner. Table 7-9: Vendor-Specific Parameters–00h Bits Byte PS–1 Reserved The EBarCo (byte 02, bit 0) bit indicates whether the bar code reader is enabled, as follows: •...

  • Page 56: Chapter 8. Move Medium-A5H

    Move Medium—A5h Command Description The MOVE MEDIUM command asks the library to move media from one element location to another. The locations are identified by their element addresses. The MODE SENSE data contains a matrix with the valid element source-destination combinations for the MOVE MEDIUM command, as described in Table 7-8: Device Capabilities Fields Format–1Fh on page 53.

  • Page 57: Table 8-2: Move Medium Command Field Values

    Table 8-2: Move Medium Command Field Values Values Field Name Allowed Transport Element Address Varies Source Address Varies Destination Address Varies Invert Clean Permitted values for the Transport Element, Source, and Destination Addresses can be changed with the MODE SELECT command. Use the MODE SENSE command to determine element address settings.

  • Page 58: Chapter 9. Position To Element-2Bh

    Position To Element—2Bh Command Description POSITION TO ELEMENT requests the picker to position itself at a specific element address. No movement occurs for a POSITION TO ELEMENT command. It does not reduce access time for loading or unloading a tape drive. This command is included for compatibility with other media changer devices.

  • Page 59: Chapter 10. Prevent/Allow Medium Removal-1Eh

    10 Prevent/Allow Medium Removal—1Eh Command Description The PREVENT/ALLOW MEDIUM REMOVAL command determines whether the library permits the removal of data cartridges through the entry/exit ports. Table 10-1: Prevent/Allow Medium Removal Command–1Eh Bits Byte Logical Unit Number–0h Table 10-2: Prevent/Allow Medium Removal Command Values Field Name Values Allowed Prevent...

  • Page 60: Chapter 11. Read Element Status-B8H

    11 Read Element Status—B8h Command Description The READ ELEMENT STATUS command requests that the library return the status of the selected elements in the library. An element’s status includes its element address, element type, whether it contains media, and whether it is in an abnormal state. If the VolTag command option is set, media bar code information is also returned.

  • Page 61: Command Response

    Return status for all element types. Return status only for medium transport elements (tape picker). Return status only for storage elements (cartridge magazine slots). Return status only for entry/exit elements (entry/exit magazine). Return status only for Data Transfer elements (tape drives).
  • Page 62 Chapter 11. Read Element Status—B8h through 10-13 illustrate the Element Descriptors for each element type.

  • Page 63: Table 11-3: Element Status Data Header Format

    Table 11-3: Element Status Data Header Format Bits Byte (MSB) (MSB) (MSB) Table 11-4: Element Status Data Header Field Values Field Name Value Returned FIrst Element Address Varies Reported Number of Elements Varies Reported Byte Count of All Varies Element Status Pages Chapter 11.

  • Page 64: Table 11-5: Element Status Page Header Format

    The Element Status Data Header is followed immediately by Element Status Pages for each element type reported. Each Element Status Page consists of a header followed by Element Descriptors for each element reported. Table 11-5: Element Status Page Header Format Bits Byte PVolTag...

  • Page 65: Element Descriptors

    Meaning Descriptors in this page are for medium transport elements (tape picker). Descriptors in this page are for storage elements (cartridge magazine slots). Descriptors in this page are for entry/exit elements. Descriptors in this page are for data transfer elements (tape drives).

  • Page 66: Table 11-7: Medium Transport Element Descriptor (Tape Picker)

    (Field moved to [12-47] if Primary Volume Tag Information field is omitted.) Chapter 11. Read Element Status—B8h Element Address Reserved Reserved Additional Sense Code Additional Sense Code Qualifier Reserved Reserved Source Storage Element Address Primary Volume Tag Information (Field omitted if PVolTag=0) Reserved (LSB) Except Reserved Full (LSB)

  • Page 67: Table 11-8: Medium Transport Element Descriptor Fields

    Meaning The address used to identify the particular element, i.e., tape picker, cartridge storage slots, or tape drive. Each element in the library must have a unique address. Element addresses are used by almost all medium changer device SCSI commands to identify locations applicable to the particular command. Each element has a factory-set default address, but the addresses can be reassigned with the MODE SELECT command.

  • Page 68: Table 11-9: Storage Element Descriptor (Magazine Slots)

    Cartridge Slots–Storage Elements The slots in the Gator libraries’ data cartridge magazines are the storage elements. Table 11-9: Storage Element Descriptor (Magazine Slots) Bits Byte (MSB) 06 - 08 SValid Invert–0 (MSB) (MSB) 12 - 47 48 -51 Reserved (Field moved to [12-47] if Primary Volume Tag Information field is omitted.) Chapter 11.

  • Page 69: Table 11-10: Storage Element Fields

    Chapter 18. Error Reporting. Sense Code Varies Qualifier (ASCQ) A value of 1 indicates that the value found in the Source Storage Element Address field is valid. SValid (Source Valid) A value of 0 indicates that the value found in the Source Storage Element Address field is not valid.

  • Page 70: Table 11-11: Data Transfer Element Descriptor (Tape Drive)

    Access=1 Reserved Additional Sense Code Additional Sense Code Qualifier ID Valid LU Valid Reserved SCSI ID Reserved Source Storage Element Address Primary Volume Tag Information (Field omitted if PVolTag=0) Reserved Reserved Reserved Identifier Length Identifier (Field omitted if DVCID=0) (LSB)

  • Page 71: Table 11-12: Data Transfer Element Descriptor Fields

    Value Field Name Returned Meaning The address used to identify the particular element, i.e., tape picker, cartridge storage slots, or tape drive. Each element in the library must have a unique address. Element addresses Element Varies are used by almost all medium changer device type-specific SCSI commands to identify Address locations applicable to the particular command.
  • Page 72 Length Identifier Varies ASCII representation of the drive serial number. A value of 1 indicates that the value found in the Source Storage Element Address field is valid. SValid (Source Valid) A value of 0 indicates that the value found in the Source Storage Element Address field is not valid.

  • Page 73: Table 11-13: Entry/Exit Element Descriptor

    Chapter 11. Read Element Status—B8h Element Address Default value=0 InEnab=1 ExEnab Access Reserved Additional Sense Code Additional Sense Code Qualifier Reserved Reserved Source Storage Element Address Primary Volume Tag Information (Field omitted if PVolTag=0) Reserved Reserved (LSB) Except Picker Full (LSB) (LSB)

  • Page 74: Table 11-14: Entry/Exit Element Fields

    Meaning The address used to identify the particular element, i.e., tape picker, cartridge storage slots, or tape drive. Each element in the library must have a unique address. Element addresses are used by almost all medium changer device type-specific SCSI commands to identify locations applicable to the particular command.
  • Page 75 Information The Range of Values is supported by the MODE SELECT command. All Storage Element Addresses in the library report access by the robotic tape picker. See Chapter 18. Error Reporting for supported ASC and ASCQ values. The library only supports the first eight characters of a bar code. If the bar code is larger than eight characters, only the first eight characters will be reported.

  • Page 76: Chapter 12. Receive Diagnostic Results-1Ch

    12 Receive Diagnostic Results—1Ch Command Description The RECEIVE DIAGNOSTIC RESULTS command asks the library to return data to the initiator of the command. The data returned is either: • The results of a previously sent SEND DIAGNOSTIC command, or, • If the PCV bit is set, the Page Code field specifies the format of the data. The support for this command includes three pages: •...

  • Page 77: Supported Diagnostics Pages

    Table 12-2: Receive Diagnostic Results Command Values Field Name Values Allowed Meaning (Page Code Valid) Page Code Allocation Length 0 - FFFFh Supported Diagnostics Pages This page is a variable length page. Future revisions of library firmware may introduce more pages, but currently only three diagnostic pages are supported: •...

  • Page 78: Table 12-3: Supported Diagnostics Page Format-00H

    Supported Diagnostics Page Table 12-3: Supported Diagnostics Page Format–00h Bits Byte (MSB) Chapter 12. Receive Diagnostic Results—1Ch Page Code - 00h Reserved Page Length - 03h First Supported Page - 00h Second Supported Page - 01h Third Supported Page - 02h (LSB)

  • Page 79: Table 12-4: Enclosure Configuration Page Format-01H

    Enclosure Configuration Page Table 12-4: Enclosure Configuration Page Format–01h Bits Byte (MSB) 04 - 07 12 - 19 20 - 27 28 - 43 44 - 47 48 - 51 52 - 55 56 - 59 60 - 63 Chapter 12. Receive Diagnostic Results—1Ch Page Code - 01h Number of Sub-Enclosures - 00h Allocation Length...

  • Page 80: Table 12-5: Enclosure Configuration Page Field Values

    Table 12-5: Enclosure Configuration Page Field Values Field Name Values Allowed Meaning Page Code Number of Sub-Enclosures Page Length Generation Code Sub-Enclosure Identifier Number of Element Types Supported Enclosure Descriptor Length Enclosure Logical Unique Identifier Enclosure Vendor SPECTRA Identification Enclosure Product GATOR Identification Product Revision...

  • Page 81: Table 12-6: Element Type Descriptor Format

    The page code for the temperature sensor diagnostic. The page code for the door lock diagnostic. There is one power supply on Spectra 12K and Spectra 20K libraries (01h). There are four power supplies on a Spectra 64K library (04h).

  • Page 82: Table 12-8: Enclosure Status Page-02H (Spectra 12K And Spectra 20K Libraries)

    Enclosure Status Page Table 12-8: Enclosure Status Page–02h (Spectra 12K and Spectra 20K Libraries) Bits Byte Reserved (MSB) 04 - 07 08 - 11 12 - 15 16 - 19 20 - 23 24 - 27 28 - 31 32 - 35...

  • Page 83: Table 12-9: Enclosure Status Page-02H (Spectra 64K Libraries)

    Table 12-9: Enclosure Status Page–02h (Spectra 64K Libraries) Bits Byte Reserved (MSB) 04 - 07 08 - 11 12 - 15 16 - 19 20 - 23 24 - 27 28 - 31 32 - 35 36 - 39 40 - 43 44 - 47 48 - 51 52 - 55...

  • Page 84: Table 12-10: Enclosure Status Page Field Values

    Unrecov bit should not be set. The amount of bytes to follow this field for Spectra 12K and Spectra 20K libraries. The amount of bytes to follow this field for Spectra 64K libraries.

  • Page 85: Element Status Pages

    Table 12-10: Enclosure Status Page Field Values Field Name Values Allowed Meaning Overall Temperature Sensor Status Varies Temperature Sensor Status Overall Door Lock Status Varies Door Lock Status Overall Element Status fields always have a Status Code of 00h (unsupported) and report 00h for all Status Information bytes. Element Status Pages Each element type has its own format for the four bytes in the Enclosure Status Page.

  • Page 86: Table 12-12: Supported Status Codes For All Element Types

    Table 12-12: Supported Status Codes for All Element Types Status Code Name Unsupported Critical Non-Critical Not Installed Individual element status formats and descriptions follow below. Table 12-13: Power Supply Status Bits Byte Reserved Table 12-14: Power Supply Status Values Field Name Meaning This bit is set to indicate that the power supply is not providing power.

  • Page 87: Table 12-15: Fan Status

    Table 12-15: Fan Status Bits Byte Reserved Table 12-16: Fan Status Values Field Name Meaning This bit is set to indicate that the fan is not providing cooling. This bit and the Non-Critical Status code (03h) are always set together. 000b indicates that the fan has stopped.

  • Page 88: Table 12-19: Door Lock Status

    Table 12-18: Temperature Sensor Status Values Field Name Meaning The value in the temperature field indicates the temperature at the sensor in degrees Celsius, offset by 20 degrees. (I.e., the range of the value is 0 to 255, but it expresses a temperature Temperature between -19 and +235 degrees Celsius.

  • Page 89: Chapter 13. Release-17H

    13 Release—17h Command Description The RELEASE command enables the initiator to release reservations on the library or library elements that were set by the RESERVE (16h) command. See the RESERVE Command Description on page 94 for more information. Only the initiator that reserved the library or its elements can release them. If another initiator attempts to release a reserved library or its elements, the library returns a RESERVATION CONFLICT status.

  • Page 90: Chapter 13. Release-17H

    Device ID Element Reservation ID Varies Any valid storage slot in the library reported by the MODE SENSE command. You cannot reserve an Import/Export, Medium Transport, or Data Transfer Element. Chapter 13. Release—17h Meaning RELEASE is not being requested for a third-party reservation.

  • Page 91: Chapter 14. Request Sense-03H

    14 Request Sense—03h Command Description The REQUEST SENSE command requests the library to send sense data to the initiator. It is generally issued immediately after the library reports a CHECK CONDITION status for the previous command. The table below shows the CDB for the REQUEST SENSE command. Table 14-1: Request Sense Command–03h Bits Byte...

  • Page 92: Command Response

    Command Response The sense data is valid for the CHECK CONDITION status just presented to the initiator. This sense data is preserved in the library for the initiator receiving the CHECK CONDITION status. Sense data is cleared when any subsequent command that is not a REQUEST SENSE or an INQUIRY (12h) command is received from the initiator.

  • Page 93: Table 14-3: Sense Data Fields

    Table 14-3: Sense Data Fields Field Name Value Returned Valid Error Code Sense Key General Error Category Chapter 18. Error Reporting for more information. Additional Sense Length Additional Sense Varies Code (ASC) Additional Sense Varies Code Qualifier (ASCQ) Field Replaceable Unit Code SKSV ASCII Representation...

  • Page 94: Chapter 15. Reserve-16H

    15 Reserve—16h Command Description The RESERVE command allows the initiator to reserve either the whole library or specific elements. Reserving the whole library or a specific element will prevent another user from moving media to the import/export element (the E/E port) of the library via the library’s control panel.

  • Page 95: Chapter 15. Reserve-16H

    Table 15-2: Reserve Command Field Values Field Name Values Allowed 3rdPty Third Party Device ID 0-7h Element Reservation ID Assigned by initiator Element List Length Any Valid Element You cannot reserve import/export elements, medium transport elements, or data transfer elements. Chapter 15.

  • Page 96: Table 15-3: Element List Descriptor Format

    Element List If the initiator requests a reservation for specific elements within the library it must specify the elements in a list of one or more Element List Descriptors. The data format for these descriptors is shown in the table below. Table 15-3: Element List Descriptor Format Bits Byte...

  • Page 97: Chapter 16. Send Diagnostic-1Dh

    16 Send Diagnostic—1Dh Command Description The SEND DIAGNOSTIC command requests that the library perform diagnostic tests on itself. The support for this command includes two pages: Page 0x00 (Supported Pages) and Page 0x02 (Enclosure Control). The Supported Pages page allows the initiator to query the library for a list of Supported Diagnostic Pages.

  • Page 98: Command Response

    Table 16-2: Send Diagnostic Command Field Values Field Name Values Allowed (Page Format) SelfTest DevOfL (Device Off-Line) UnitOfL (Unit Off-Line) Parameter List Length 0-FFFFh Command Response There is no data returned from the SEND DIAGNOSTIC command. If the command is successful, a GOOD status is returned.

  • Page 99: Parameter Lists

    Parameter Lists Following the Command Block in the Data Out phase, the initiator sends a parameter list containing the diagnostic to be performed. Each parameter list contains a Parameter List Header followed by the data for the diagnostic. These parameter lists are shown below.

  • Page 100: Supported Diagnostics

    Supported Diagnostics The Supported Diagnostic Page format contains no additional data. The Diagnostic Parameter List Header contains all the data to be transferred to the library. To retrieve the results of this command, a RECEIVE DIAGNOSTIC RESULTS command with the PCV bit set to OFF must be sent to the library.

  • Page 101: Table 16-6: Enclosure Services Control

    See the following tables for Enclosure Services Control Page formats and field values. Table 16-6: Enclosure Services Control Page Format (for Spectra 12K and Spectra 20K Libraries) Bits Byte Reserved (MSB) 04 - 07 08 - 11 12 - 15...

  • Page 102: Table 16-7: Enclosure Services Control Page Format (For Spectra 64K Libraries)

    Table 16-7: Enclosure Services Control Page Format (for Spectra 64K Libraries) Bits Byte Reserved (MSB) 04 - 07 08 - 11 12 - 15 16 - 19 20 - 23 24 - 27 28 - 31 32 - 35 36 - 39 40 - 43 44 - 47 48 - 51...

  • Page 103: Table 16-8: Enclosure Services Control Page Field Values

    Ignored by the library. This is not an error condition. Specifies that the additional data length be transferred to the library. For Spectra 12K and 20K libraries, this should be set to 28h. Specifies that the additional data length be transferred to the library. For Spectra 64K libraries, this should be set to 38h.

  • Page 104: Chapter 17. Test Unit Ready-00H

    17 Test Unit Ready—00h Command Description The TEST UNIT READY command determines if the library is on and ready to accept commands. Table 17-1: Test Unit Ready Command–00h Bits Byte Logical Unit Number–0h Command Response This command returns a GOOD status if the library is ready to accept SCSI commands. This command returns CHECK CONDITION status with UNIT ATTENTION (6h) in the sense key after power-up, after a bus device reset message is sent to the library, and after a power-on reset, or a CHECK CONDITION with appropriate sense key for the error conditions.

  • Page 105: Chapter 18. Error Reporting

    18 Error Reporting This section lists the error codes and corresponding meanings that can be returned by the library. Note: For the error codes returned by Sony AIT tape drives (Medium Error—3h), refer to the tape drive manual on the Sony Web site at http://sony.storagesupport.com/ait/software_dwn.htm.

  • Page 106: Sense Keys

    Sense Keys The following table describes the sense key valuations returned by the library. The sense key indicates the nature of the error condition in a very general way. Table 18-1: Sense Key Values Sense Key Meaning No Sense Not Ready Hardware Error Illegal Request Unit Attention...

  • Page 107: Sense Codes And Qualifiers

    Sense Codes and Qualifiers Combining the Sense Key with the Additional Sense Code (ASC) and Additional Sense Code Qualifier (ASCQ) returned to a REQUEST SENSE command, gives the most complete error description available from the library. The following table describes the error codes returned by the library.
  • Page 108 Table 18-2: Library SCSI Error Codes Sense Key ASCQ Hardware Errors (continued) Chapter 18. Error Reporting Error Description Entry/exit door could not be retracted. Unit failed initialization. Move failed; drive did not unload. Tape failed load; move marked successful. Drive failed to come ready. Move failed;...
  • Page 109 2. If that fails, manually remove the tape from the slot. 3. If that fails, try to reseat the magazine. If the problem persists, contact Spectra Logic Technical Support. The robot may be misaligned or the tape may be broken (with the tape possibly wrapped around the drive heads).
  • Page 110 Table 18-2: Library SCSI Error Codes Sense Key ASCQ Hardware Errors (continued) Chapter 18. Error Reporting Error Description FPROM write operation failed. General picker definition error. Invalid picker type. Invalid rack type. Invalid library size. Invalid chassis type. Invalid E/E door type. Internal SCSI error unknown.
  • Page 111 Table 18-2: Library SCSI Error Codes Sense Key ASCQ Hardware Errors (continued) Chapter 18. Error Reporting Error Description DMA error. Command phase overrun—device demanded more CDB bytes than available. Device supplied excess status bytes. Device did not complete command with Command Complete. Device skipped MSG OUT phase after Selection.
  • Page 112 Table 18-2: Library SCSI Error Codes Sense Key ASCQ Hardware Errors (continued) Chapter 18. Error Reporting Error Description Bad IOQB entry submitted to hardware. Device does not respond—it is powered off, not attached, or non- functional. Interface command queue is full. Device operation did not complete for unknown reason.
  • Page 113 Table 18-2: Library SCSI Error Codes Sense Key ASCQ Hardware Errors (continued) Chapter 18. Error Reporting Error Description CAN sequence error. Data overrun sequence error. Data underrun sequence error. Command underrun sequence error. Invalid CAN command during code load. Invalid CAN address during code load. Invalid CAN from address during code load.
  • Page 114 Table 18-2: Library SCSI Error Codes Sense Key ASCQ Illegal Request Chapter 18. Error Reporting Error Description Operation in progress. The initiator is trying to initiate an additional command to the target device before the first command is complete. Parameter list length error. Invalid command code.
  • Page 115 Table 18-2: Library SCSI Error Codes Sense Key ASCQ Illegal Request (continued) Chapter 18. Error Reporting Error Description Unsupported segment descriptor type code. Unexpected inexact segment. Inline data length exceeded. Invalid operation for copy source or destination. Command sequence error. FLASH code download to tape drive via Write Buffer failed.
  • Page 116 Exit Only; it can export tapes but not import them. 1. If you wish to use the software to import tapes from the E/E port to the storage slots, you must disable the Queued Unloads option. 2. In a multi-partition library, you must...
  • Page 117 E/E port when Queued Unloads is enabled AND when the source slot is not an actual storage slot. Possible initial source slot moves that cause this error include moving a tape to a drive from the E/E port, or moving a...
  • Page 118 Table 18-2: Library SCSI Error Codes Sense Key ASCQ Unit Attention Vendor- Specific Chapter 18. Error Reporting Error Description Inventory possibly altered. Door element accessed. A reset has occurred. Drive failed power-on self test (POST) or user issued diagnostic test. This is a Sony-unique error code.
  • Page 119 Table 18-2: Library SCSI Error Codes Sense Key ASCQ Copy Aborted Chapter 18. Error Reporting Error Description Third party device failure— hardware failure of the target device. Copy target device not reachable— device is not responding after having been found. Incorrect copy target device type—...

  • Page 120: Appendix A Extended Copy-83H143R1 Specifications

    Appendix A Extended Copy—83h— Fibre Channel Command Description Note: The EXTENDED COPY command is not supported by the SCSI QIP. The EXTENDED COPY command (Table A-A-1 on page 121) provides a means to copy data from one set of logical units to another or to the same set of logical units. The device server that receives and performs the EXTENDED COPY command is called the copy manager.

  • Page 121: Table A-1: Extended Copy Command (143R1 Specifications)

    Table A-1: Extended Copy Command (143r1 Specifications) Byte (MSB) Before the copy manager is instructed to move data, the application controlling the data movement will independently execute any activities necessary to prepare the devices for the EXTENDED COPY command; these activities include media changer commands, loading tapes, MODE SELECT commands, positioning tape, etc.

  • Page 122: Table A-2: Extended Copy Parameter List

    segment descriptor list. Immediately following the header is one or more target descriptors, followed by one or more segment descriptors, then followed by any optional inline data. Table A-2: Extended Copy Parameter List Byte Reserved (MSB) The List ID field is a user-defined value that is used by the copy manager to return status for that command.

  • Page 123: Table A-3: Extended Copy Descriptor Codes

    descriptor. All target descriptors will have their formats specified by an EXTENDED COPY descriptor code. A copy manager need not support all target descriptor codes for its device type. The target descriptors will be indexed in ascending order beginning with 0 to a maximum of 65535.
  • Page 124 Table A-3: Extended Copy Descriptor Codes Peripheral Device Type (Note 5) Source Destination Block devices Stream devices (Device types 0,4,5,7) (Device types 1,3,9) Stream devices Block devices (Device types 1,3,9) (Device types 0,4,5,7) Block devices Block devices (Device types 0,4,5,7) (Device types 0,4,5,7) Stream devices Stream devices...
  • Page 125 The Priority field of the EXTENDED COPY parameter list establishes the relative priority of this EXTENDED COPY command to other commands being executed by the same copy manager. Priority 0 is the highest priority, with increasing priority values indicating lower priorities. All other commands are assumed to have a priority of 1. The Str bit is an indication to the copy manager that most of the disk references in the parameter list represent sequential access of several stripped disks.
  • Page 126 Errors Detected During Execution of Segment Descriptors Errors may occur after the copy manager has begun executing segment descriptors. These include invalid parameters in segment descriptors, invalid segment descriptors, unavailable targets referenced by segment descriptors, inability of the copy manager to continue operating, and errors reported by source or destination target devices.

  • Page 127: Target Descriptors

    Target Descriptors All target descriptors begin with a four-byte header that contains the Descriptor Type Code field. The Descriptor Type Code identifies the format of the descriptor. The assigned values for target descriptors type codes are shown in Table A-A-4. Table A-4: Target Descriptor Format Byte Reserved...

  • Page 128: Table A-6: World Wide Name Target Descriptor Format

    its Mode Sense Page 0Eh. If the number of target descriptors exceeds the allowed number, the copy manager terminates the command with a CHECK CONDITION; the sense key is set to ILLEGAL REQUEST, and the ASC and ASCQ indicate TOO MANY TARGET DESCRIPTORS. World Wide Name Target Descriptor Format The target descriptor format shown in Table A-A-6 may be used to identify targets using their World Wide Names.

  • Page 129: Table A-7: N_Port D_Id Target Descriptor Format

    The Address Type is 0, and Bytes 4-11 of the target descriptor are defined as the World Wide Name for the target device. The Device Type Field is as identified in Target Descriptors on page 127. The Logical Unit Number field specifies the LUN for the target device. The Device-Type Specific field is defined in Target Descriptor Device-Specific Fields on page 132.

  • Page 130: Table A-8: World Wide Name Target Descriptor Format

    The Address Type is 1, and Bytes 5-7 of the target descriptor are defined as the N_PORT D_ID for the target device. The Device Type Field is as identified in Target Descriptors on page 127. The Logical Unit Number field specifies the FCP LUN for the target device. The Device-Type Specific field is defined in Target Descriptor Device-Specific Fields on page 132.
  • Page 131 Table A-8: World Wide Name Target Descriptor Format Byte (MSB) The Address Type is 2, and Bytes 5-7 of the target descriptor are defined as the N_PORT D_ID for the target device. The D_ID field is the 24-bit (3-byte) Destination Identifier field that is used to actually route the commands through a fabric.

  • Page 132: Table A-9: Scsi B_T_L Target Descriptor Format

    SCSI B_T_L Target Descriptor Format Targets identified using their SCSI Bus, Target ID, and LUN are identified using the target descriptor format shown in Table A-A-9. The Descriptor Type Code for this descriptor is E3h. Table A-9: SCSI B_T_L Target Descriptor Format Byte Reserved The Address Type is 3.

  • Page 133: Table A-10: Device-Specific Field - Device Type 00H

    Device-specific information is currently defined for device types 00h and 01h. Device- specific information for device types other than 00h and 01h are not yet defined. Until device-specific information is defined for these other types, all block devices will use device-specific information of type 00h and all stream devices will use the device- specific information of type 01h.

  • Page 134: Table A-12: Tape Transfer Lengths

    For stream devices (Device Type 01h), the Fixed Bit and Tape Block Length fields in the device-specific information are combined with the Device Transfer Length field in the segment descriptor to determine the length of the stream data transfer (see Table A-A-12 on page 134).

  • Page 135: Segment Descriptors

    Segment Descriptors All segment descriptors begin with an eight-byte field as shown in Table A-A-13. Table A-13: Segment Descriptor Header Byte (MSB) (MSB) The first byte of the segment descriptor is the descriptor type code field which is used to describe the operation for the segment. A list of defined segment descriptor type codes can be found in Table A-A-3 on page 123.

  • Page 136: Table A-14: Pad Bit And Cat Bit Interaction

    Table A-14: PAD Bit and CAT Bit Interaction SRC PAD DST PAD The Descriptor Length provides the length in bytes of the current segment descriptor. The length is defined as the actual length of the descriptor minus four. The Descriptor Length does not include any embedded data where applicable.

  • Page 137: Table A-15: Segment Descriptor For Codes 00H, 01H, 0Bh, And 0Ch

    Block Device to Stream Device Operation Descriptor Code 00h The segment descriptor format for EXTENDED COPY transfers from a block device to a stream device is shown in Table A-A-15. This format is required for EXTENDED COPY descriptor code 00h. The field definitions for the first eight bytes are as defined in Target Descriptors on page 127.
  • Page 138 The Block Device Number of Blocks field specifies the number blocks in the current segment to be copied. A value of 0 indicates that no blocks will be transferred in this segment; this will not be considered an error. The Block Device Logical Block Address field specifies the starting address on the logical unit for this segment.

  • Page 139: Table A-16: Segment Descriptor For Codes 02H And 0Dh

    Block Device to Block Device Operation Descriptor Code 02h The segment descriptor format for EXTENDED COPY transfers between block devices is shown in Table A-A-16. This format is required for EXTENDED COPY descriptor code 02h. The field definitions for the first eight-bytes are as defined in Segment Descriptors on page 135.

  • Page 140: Table A-17: Segment Descriptor For Codes 03H And 0Eh

    The DC bit is used to indicate whether the Block Device Number of Blocks field refers to the source or destination logical unit. A DC bit of 0 indicates that the Block Device Number of Blocks field refers to the source logical unit. A DC bit of 1 indicates that the Block Device Number of Blocks field refers to the destination logical unit.
  • Page 141 Table A-17: Segment Descriptor for Codes 03h and 0Eh Byte (MSB) The Source Device Transfer Length specifies the amount of data to be read from the source stream device on each read operation. See Table A-A-12 on page 134 for information on how the segment descriptor Source Device Transfer Length interacts with the Tape Block Length Parameter of the device-specific information.

  • Page 142: Table A-18: Segment Descriptor For Code 04H

    Inline Data to Stream Device Operation Descriptor Code 04h The segment descriptor format for EXTENDED COPY operation that moves inline data to a stream device is shown in Table A-A-18. This format is required for EXTENDED COPY descriptor code 04h. The field definitions for the first eight-bytes are as defined in Segment Descriptors on page 135, except for Bytes 4 and 5, which are reserved instead of having the Source Target Identifier.

  • Page 143: Table A-19: Segment Descriptor For Code 05H

    processed in a sequential manner from first to last to ensure that the inline data at the end of the parameter list is properly assigned. Inline data must begin on and should be padded up to a four-byte boundary. The Number of Bytes field indicates the actual data length, not including any PAD bytes.
  • Page 144 Table A-19: Segment Descriptor for Code 05h Byte (MSB) The Destination Device Transfer Length specifies the amount of data to be written to the destination stream device on each write operation. See Table A-A-12 on page 134 for information on how the segment descriptor Device Transfer Length interacts with the Tape Block Length Parameter of the device-specific information.

  • Page 145: Table A-20: Segment Descriptor For Codes 06H And 0Fh

    Stream Device to Discard Operation Descriptor Code 06h The segment descriptor format for EXTENDED COPY operation that discards data from a stream device is shown in Table A-A-20. This format is required for EXTENDED COPY descriptor code 06h. The field definitions for the first eight bytes are as defined in Segment Descriptors on page 135, except for Bytes 6 and 7, which are reserved instead of having the Destination Target Identifier.

  • Page 146: Table A-21: Segment Descriptor For Code 07H

    Verify Target Operation Descriptor Code 07h The segment descriptor format for EXTENDED COPY operation that verifies the existence of a block or stream device is shown in Table A-A-21. This format is required for EXTENDED COPY descriptor code 07h. The field definitions for the first eight-bytes are as defined in Segment Descriptors on page 135, except for Bytes 6 and 7, which are reserved instead of having the Destination Target Identifier.

  • Page 147: Table A-22: Segment Descriptor For Code 10H

    Write Filemarks Operation Descriptor Code 10h The segment descriptor format for the EXTENDED COPY write filemarks operation is shown in Table A-A-22. This format is required for EXTENDED COPY descriptor code 10h. Table A-22: Segment Descriptor for Code 10h Byte (MSB) (MSB) The WRITE FILEMARKS operation constructs a WRITE FILEMARKS command using the WSmk and...

  • Page 148: Table A-23: Segment Descriptor For Code 11H

    SPACE Operation Descriptor Code 11h The segment descriptor format for EXTENDED COPY SPACE operation shown in Table A-A-23. This format is required for EXTENDED COPY descriptor code 11h. Table A-23: Segment Descriptor for Code 11h Byte (MSB) (MSB) The SPACE operation constructs a SPACE command using the Code and Count fields from the segment descriptor in the corresponding command fields of the SPACE command that is issued to the target device.

  • Page 149: Mode Sense Page For Extended Copy Command

    command that is issued to the target device. All other fields of the issued command are set to 0. Table A-24: Segment Descriptor for Code 12h Byte (MSB) (MSB) Mode Sense Page for Extended Copy Command MODE SENSE information pertaining to the operation of the EXTENDED COPY command’s copy manager is obtained from the copy manager using the 0Eh MODE SENSE page shown in Table A-A-25 on page 151.
  • Page 150 Maximum Segment Count The maximum number of segment descriptors that the copy manager allows in a single EXTENDED COPY segment descriptor list (32 KB). Maximum Descriptor List Length Field The maximum length, in bytes, of the target descriptor list and segment descriptor list; this length includes the embedded data but excludes inline data that follows the parameter list (1 MB).

  • Page 151: Table A-25: Mode Sense Page For Extended Copy Command

    Descriptor List A list of one-byte descriptor types that are supported by the copy manager. The descriptor list will be ordered in ascending order. Table A-25: Mode Sense Page for Extended Copy Command Byte Rsvd (MSB) (MSB) (MSB) (MSB) (MSB) (MSB) (MSB) Page Code (0x0E)

  • Page 152: Sense Key Specific Field Changes

    Table A-25: Mode Sense Page for Extended Copy Command Byte 33 + n Sense Key Specific Field Changes The Sense Key Specific field as defined to support the EXTENDED COPY command is shown in Table A-A-26. Table A-26: Segment Pointer Bytes Byte SKSV (MSB)
  • Page 153 The Segment Descriptor (SD) bit is used to indicate if the field pointer is with reference to the start of the parameter list or a segment descriptor. A value of 1 indicates that the Field Pointer is relative to the start of the segment descriptor indicated by the third and fourth bytes of the command-specific information field.

  • Page 154: Receive Copy Results Command

    Receive Copy Results Command The RECEIVE COPY RESULTS command is used to return the results of a previous (or current) EXTENDED COPY command. The results that can be returned from the previous (or current) EXTENDED COPY command are either copy manager status information, inline data from read operations, or information about the order in which the segments were processed during the EXTENDED COPY command.

  • Page 155: Table A-28: Mode Field Definitions

    CHECK CONDITION. The Sense Key is set to ILLEGAL REQUEST, and the ASC and ASCQ indicate INVALID FIELD IN CDB. Table A-28: Mode Field Definitions Mode Value Receive Copy Results Operation Return the current Copy Status of the executing EXTENDED COPY command identified by List ID. Return the Inline data read by EXTENDED COPY command identified by List ID.
  • Page 156 COPY RESULTS command immediately following completion of the EXTENDED COPY command to ensure that the data is not discarded by the copy manager. The copy manager will discard the Segment Order List: • After it has been successfully transferred to the host; •...

  • Page 157: Table A-29: Return Data Format - Mode 0 (Status)

    Copy Status Mode When the Mode field is set to return copy results, the copy manager returns the current status of the EXTENDED COPY command identified by the List ID field. Table A-A-29 shows the format of the information returned by the copy manager in response to a request for Copy Status.

  • Page 158: Table A-31: Transfer Count Format

    The Transfer Count Format field specifies the format of the transfer count. The Transfer Count Format is coded as shown in Table A-A-31. Table A-31: Transfer Count Format Transfer Count Format Value The Transfer Count field specifies the amount of data transferred by the EXTENDED COPY command prior to receiving the request for copy status.

  • Page 159: Appendix B Extended Copy-83H-Spc2 Specifications

    Appendix B Extended Copy—83h— Fibre Channel Command Description Note: The EXTENDED COPY command is not supported by the SCSI QIP. The EXTENDED COPY command (Table B-B-1 on page 160) provides a means to copy data from one set of logical units to another or to the same set of logical units. The entity within a device server that receives and performs the EXTENDED COPY command is called the copy manager.
  • Page 160 Table B-1: Extended Copy Command (SPC2 Specifications) Byte (MSB) Before the copy manager is instructed to move data, the application controlling the data movement will independently execute any activities necessary to prepare the devices for the EXTENDED COPY command; these activities include media changer commands, loading media, MODE SELECT commands, positioning media, etc.

  • Page 161: Table B-2: Extended Copy Parameter List

    target descriptors, followed by one or more segment descriptors, followed by any optional inline data. Table B-2: Extended Copy Parameter List Byte Reserved (MSB) (MSB) (MSB) n-31 The List Identifier field is a unique value selected by the application client to identify the EXTENDED COPY operation to the copy manager.
  • Page 162 Appendix B. Extended Copy—83h—SPC2 Specifications CONDITION status; the sense key is set to ILLEGAL REQUEST, and the ASC and ASCQ indicate OPERATION IN PROGRESS. The Priority field establishes the priority of this EXTENDED COPY command relative to other commands being executed by the same device server. All commands other than copy commands have a priority of 1.
  • Page 163 The Inline Data Length field contains the number of bytes of inline data, after the last segment descriptor. A value of zero indicates that no inline data is present. The copy manager will move data from the source devices to the destination devices in the manner prescribed by the segment descriptors.
  • Page 164 Appendix B. Extended Copy—83h—SPC2 Specifications descriptor in the parameter list is assigned descriptor number 0, the second is assigned 1, etc.; 4. If any data has been transferred for the segment being processed at the time the error occurred, the residual for the segment will be placed in the Information field, and the valid bit will be set to 1.

  • Page 165: Table B-3: Extended Copy Descriptor Type Codes

    Abort Task Management Functions When a device server processes an ABORT TASK, ABORT TASK SET, or CLEAR TASK SET task management function that terminates an EXTENDED COPY command, the copy manager will ensure that all commands and data transfers generated by the terminated EXTENDED COPY command have been terminated and are no longer transferring data before allowing the task manager to complete the task management function.
  • Page 166 Table B-3: Extended Copy Descriptor Type Codes Descriptor Type Code Reference 15h-BFh C0h-DFh E5h-FFh Block devices are those with peripheral device type codes 0h, 4h, 5h, 7h, and Eh. Stream devices are those devices with peripheral device type codes 1h and 3h. Sequential-access tape devices are those devices with peripheral device type code 01h. Not supported.

  • Page 167: Table B-4: Target Descriptor Format

    will be set to ILLEGAL REQUEST, and the additional sense code will be set to UNSUPPORTED TARGET DESCRIPTOR TYPE CODE. Table B-4: Target Descriptor Format Byte Reserved The Descriptor Type Code Field is described in Descriptor Type Codes on page 165. A null device (NUL) bit of zero indicates that the target descriptor identifies a SCSI device that is expected to respond to an INQUIRY command and to which data movement commands may be sent.

  • Page 168: Table B-5: Device Type Specific Parameters In Target Descriptors

    The value in the Peripheral Device Type field determines the format of the device type specific parameters that follow the target descriptor parameters. The device type specific parameters convey information specific to the type of device identified by the target descriptor. Table B-B-5 lists the peripheral device type code values having formats defined for the device type specific parameters in a target descriptor.

  • Page 169: Table B-7: N_Port Target Descriptor Format

    The Descriptor Type Code, Peripheral Device Type and NUL fields and the device type specific parameters are described in Target Descriptors on page 166. The Logical Unit Number field specifies the logical unit within the SCSI device addressed by the data in the World Wide Name field that will be the target (source or destination) for EXTENDED COPY operations.

  • Page 170: Table B-8: N_Port With World Wide Name Checking Target Descriptor Format

    The Descriptor Type Code, Peripheral Device Type and NUL fields and the device type specific parameters are described in Target Descriptors on page 166. The Logical Unit Number field specifies the logical unit within the SCSI device addressed by the data in the N_PORT field that will be the target (source or destination) for EXTENDED COPY operations.

  • Page 171: Table B-9: Parallel Interface T_L Target Descriptor Format

    The World Wide Name field will contain the port World Wide Name defined by the PLOGI extended link service. The N_PORT field will contain the FC-PH port D_ID to be used to transport frames including PLOGI and FCP-2 related frames. When the copy manager first processes a segment descriptor that references this target descriptor, it will confirm that the D_ID in the N_PORT field is associated with the World Wide Name in the World Wide Name field.

  • Page 172: Table B-10: Identification Descriptor Target Descriptor Format

    The Logical Unit Number field specifies the logical unit with in the SCSI device addressed by the data in the Target Identifier field that will be the target (source or destination) for EXTENDED COPY operations. The Target Identifier field specifies the SCSI target identifier to be used when this target descriptor identifies the source or destination of an EXTENDED COPY operation.

  • Page 173: Table B-11: Device Type Specific Target Descriptor Parameters For Block Device Types

    The identifier length will be 20 or less. If the identifier length is 20, there will be no reserved bytes between the target descriptor parameters and the device type specific parameters. Some combinations of code set, association, identifier type, identifier length and identifier do not uniquely identify a logical unit to serve as a copy target device.

  • Page 174: Table B-12: Device Type Specific Target Descriptor Parameters For Stream Device Types

    Device Type Specific Target Descriptor Parameters for Stream Device Types The format for the device type specific target descriptor parameters for the sequential- access device type (device type code value 01h) is shown in Table B-B-12. Table B-12: Device Type Specific Target Descriptor Parameters for Stream Device Types Byte The contents of the Fixed bit and Stream Block Length field are combined with the Stream Device Transfer Length field in the segment descriptor to determine the length...

  • Page 175: Types

    The copy manager will not read ahead from sources of stream device type. That is, the read operations required by a segment descriptor for which the source is a stream device will not be started until all write operations for previous segment descriptors have completed.

  • Page 176: Table B-15: Segment Descriptor Header Format

    The destination count (DC) bit is used in those segment descriptors where both the source and destination devices have the same storage structure (block or stream). The DC bit is only applicable to segment descriptors with descriptor type code values of 02h, 03h, 0Dh, and 0Eh.

  • Page 177: Table B-16: Descriptor Type Code Dependent Copy Manager Processing

    Except as otherwise specified by particular segment descriptor type codes: 1. Just enough whole-block read operations will be performed to supply (together with residual source data from the previous segment or segments) the number of bytes to be processed; 2. Processing consists of removing bytes from the source data and designating them as destination data, without change.
  • Page 178 Table B-16: Descriptor Type Code Dependent Copy Manager Processing Segment Descriptor Type Code 07h (verify device operation) 10h (filemark -> tape) 11h (space -> tape) 12h (locate -> tape) 14h (register key) 08h (block<o> -> stream) 0Ah (block<o> -> block<o>) 0Fh (stream ->...

  • Page 179: Table B-17: Pad And Cat Bit Definitions

    Table B-17: PAD and CAT Bit Definitions Pad Bit in ... Source Destination Target Target Descriptor Descriptor Copy Manager Action Any residual source data will be retained as source data for a subsequent segment descriptor. Any residual destination data will be retained as destination data for a subsequent segment descriptor.

  • Page 180: Table B-18: Block Device To Or From Stream Device Segment Descriptor

    The Source Target Descriptor Index field contains an index into the target descriptor list identifying the source target device. The Destination Target Descriptor Index field contains an index into the target descriptor list identifying the destination target device. Some segment descriptor formats do not require a Source Target Descriptor Index field or a Destination Target Descriptor Index field, in which case the field is reserved.
  • Page 181 Appendix B. Extended Copy—83h—SPC2 Specifications The Descriptor Type Code field is described in Descriptor Type Codes on page 165 and Segment Descriptors on page 176. Two Descriptor Type Code values use the segment descriptor format shown in Table B-B-18 on page 180 and described in this clause. For descriptor type code 00h (block->stream) or descriptor type code 0Bh (block->stream+application client), the copy manager will copy the data from the source block device identified by the Source Target Descriptor Index field to the...
  • Page 182 Appendix B. Extended Copy—83h—SPC2 Specifications Stream Device to Block Device Operations The segment descriptor format shown in Table B-B-18 on page 180 also is used by the copy operations that move data from a stream device to a block device. Two Descriptor Type Code values use the segment descriptor format shown in Table B-B-18 on page 180 and described in this clause.

  • Page 183: Table B-19: Block Device To Block Device Segment Descriptor

    Block Device to Block Device Operations The segment descriptor format shown in Table B-B-19 is used by the copy operations that move data from a block device to a block device. Table B-19: Block Device to Block Device Segment Descriptor Byte (MSB) (MSB)
  • Page 184 Appendix B. Extended Copy—83h—SPC2 Specifications descriptor for the source device times the contents of the Block Device Number of Blocks field, and as many writes as possible will be performed using any residual destination data from the previous segment and the data processed in this segment. If the DC bit equals one, the number of blocks specified by the Block Device Number of Blocks field will be written to the destination block device, as many bytes will be processed as necessary for these writes to be performed, and as many blocks will be...

  • Page 185: Table B-20: Stream Device To Stream Device Segment Descriptor

    Stream Device to Stream Device Operations The segment descriptor format shown in Table B-B-20 is used by the copy operations that move data from a stream device to a stream device. Table B-20: Stream Device to Stream Device Segment Descriptor Byte (MSB) (MSB)

  • Page 186: Table B-21: Inline Data To Stream Device Segment Descriptor

    For descriptor type code 0Eh (stream->stream+application client), the copy manager also will hold a copy of the processed data for delivery to the application client upon completion of the EXTENDED COPY command in response to a RECEIVE COPY RESULTS command with RECEIVE DATA service action.
  • Page 187 Table B-21: Inline Data to Stream Device Segment Descriptor Byte (MSB) (MSB) (MSB) (MSB) (MSB) The Descriptor Type Code field is described in Descriptor Type Codes on page 165 and Segment Descriptors on page 176. Descriptor type code 04h (inline->stream) instructs the copy manager to write inline data from the EXTENDED COPY parameter list to a stream device.

  • Page 188: Table B-22: Embedded Data To Stream Device Segment Descriptor

    The value in the Inline Data Offset field is added to the location of the first byte of inline data in the EXTENDED COPY parameter list (see Table B-B-2 on page 161) to locate the first byte of inline data to be written to the stream device. The Inline Data Offset value will be a multiple of 4.
  • Page 189 Appendix B. Extended Copy—83h—SPC2 Specifications The Descriptor Type Code field is described in Descriptor Type Codes on page 165 and Segment Descriptors on page 176. Descriptor type code 05h (embedded->stream) instructs the copy manager to write embedded data from the segment descriptor to a stream device.

  • Page 190: Table B-23: Stream Device To Discard Segment Descriptor

    Stream Device to Discard Operation The segment descriptor format shown in Table B-B-23 instructs the copy manager to read data from a stream device and not copy it to any destination device. Table B-23: Stream Device to Discard Segment Descriptor Byte (MSB) (MSB)

  • Page 191: Table B-24: Verify Device Operation Segment Descriptor

    The CAT bit is described in Segment Descriptors on page 176. The Descriptor Length field will contain 12 (000Ch). The Destination Target Descriptor Index field is described in Segment Descriptors on page 176. The Source Stream Device Transfer Length field specifies the amount of data to be read from the source stream device on each read operation.

  • Page 192: Table B-25: Write Filemarks Operation Segment Descriptor

    The Descriptor Length field will contain 4 (0004h). The Source Target Descriptor Index field is described in Segment Descriptors on page 176. Support for a value of one in the TUR (Test Unit Ready) bit is optional. If a TUR value of one is supported and the TUR bit contains one, then a TEST UNIT READY command will be used to determine the readiness of the device.

  • Page 193: Table B-26: Space Operation Segment Descriptor

    will be set to COPY ABORTED and the additional sense code will be set to INVALID OPERATION FOR COPY SOURCE OR DESTINATION. The Descriptor Length field will contain 8 (0008h). The Destination Target Descriptor Index field is described in Segment Descriptors on page 176. If the write setmark (WSMK) bit is one, the Transfer Length field specifies the number of setmarks to be written.

  • Page 194: Table B-27: Locate Operation Segment Descriptor

    The Descriptor Length field will contain 8 (0008h). The Destination Target Descriptor Index field is described in Segment Descriptors on page 176. The Code and Count field contents in the SPACE command sent to the destination tape device will be copied from the Code and Count fields in the segment descriptor. All other fields in the SPACE command sent to the destination tape device that affect the positioning of the tape will be set to zero.
  • Page 195 The Block Address field contents in the LOCATE command sent to the destination tape device will be copied from the Block Address field in the segment descriptor. All other fields in the LOCATE command sent to the destination tape device that affect the positioning of the tape will be set to zero.

  • Page 196: Appendix C Receive Copy Results84H

    Appendix C Receive Copy Results— Fibre Channel Command Description Note: The RECEIVE COPY RESULTS command is not supported by the SCSI QIP. The RECEIVE COPY RESULTS command (Table D-C-1 on page 197) provides a means for the application client to receive information about the copy manager or the results of a previous (or current) EXTENDED COPY command (see Appendix B.

  • Page 197: Table C-2: Receive Copy Results Service Action Codes

    Table C-1: Receive Copy Results Command Byte Reserved (MSB) The service actions defined for the RECEIVE COPY RESULTS command are shown in Table C-C- Table C-2: Receive Copy Results Service Action Codes Code Name Copy Status Receive Data Operating Parameters Failed Segment Details 05h - 1Eh Appendix C.

  • Page 198: Table C-3: Parameter Data For The Copy Status Service Action

    Not supported. The List Identifier field identifies the EXTENDED COPY command (see Appendix B. Extended Copy—83h—SPC2 Specifications) about which information is desired. The RECEIVE COPY RESULTS command will return information from the EXTENDED COPY command received from the same initiator with a list identifier that matches the list identifier specified in the RECEIVE COPY RESULTS CDB.

  • Page 199: Table C-4: Copy Status Status Values

    After completion of an EXTENDED COPY command, the copy manager will preserve all data returned by a COPY STATUS service action for a vendor specific period of time. The copy manager will discard the COPY STATUS data when: 1. A RECIEVE COPY RESULTS command with COPY STATUS service action is received from the same initiator with a matching list identifier;...

  • Page 200: Failed Segment Details Service Action

    Table C-5: Copy Status Transfer Count Units Values 06h - FFh The Transfer Count field specifies the amount of data written to a destination device for the EXTENDED COPY command identified by the List Identifier field in the CDB prior to receiving the RECEIVE COPY RESULTS command with COPY STATUS service action.
  • Page 201 The application client should issue a RECEIVE COPY RESULTS command with FAILED SEGMENT DETAILS service action immediately following failure of the EXTENDED COPY command to insure that the information is not discarded by the copy manager. The copy manager will discard the failed segment details: 1.

  • Page 202: Appendix D Report Luns-A0

    A SCSI device will support a REPORT LUNS command that is addressed to logical unit zero. Support of the REPORT LUNS command by logical units other than logical unit zero is not supported. The REPORT LUNS command is supported on Spectra Logic’s Fibre Channel and iSCSI libraries.
  • Page 203 The default report of the logical unit inventory will contain at least LUN 0. Spectra Logic Gator libraries support a maximum of six LUNs (four tape drives and two libraries). If the logical unit inventory changes for any reason, including completion of initialization, removal of a logical unit, or creation of a logical unit, the device server will generate a unit attention command for all initiators.

  • Page 204: Table D-2: Example Configurations

    Table D-2: Example Configurations LUNs Config 1 Drive 1 Drive 2 Drive 3 Drive 4 If installed. Config 1 is a QIP that only has tape drives attached. Config 2 is an exporting library QIP with tape drives. Config 3 and Config 4 are QIPs that are configured as two separate libraries. Table D-3: Report LUNs Parameter Data Format Byte (MSB)
  • Page 205 Table D-3: Report LUNs Parameter Data Format Byte (MSB) (MSB) (MSB) Appendix D. Report LUNs—A0 First LUN (00) Second LUN (01) Last LUN (LSB) (LSB) (LSB)

  • Page 206: Index

    ABORT message 27 additional sense code qualifiers 106 additional sense codes 106 address cartridge slots 68 entry/exit 73 medium transport element 66 storage elements 68 tape picker 66 alert UNIT ATTENTION 42 ANSI see SCSI-2 standards ASC 106 ASCQ 106...
  • Page 207 68 data transfer element 70 element list 96 entry/exit element 73 medium transport 66 storage element 68 tape picker 66 Developer Guide about this guide 16 glossary 17 device medium changer 19 DEVICE RESET message 27 diagnostics...
  • Page 208 Fibre Channel commands EXTENDED COPY (143r1) 120, 159, RECEIVE COPY RESULTS 196 REPORT LUNS 202 formats SCSI commands 23 Gator library architecture 16 product identification value 38, 41 glossary of terms 17 GOOD status 28, 104 hardware error sense key 106, 107, 108, 109, 110, 111, 112, 113 hexadecimal numbering 17 identification...
  • Page 209 messages ABORT 27 ATTENTION 20 COMMAND COMPLETE 20 DEVICE RESET 27 DISCONNECT 20 errors 105 IDENTIFY 20 MSG OUT PHASE 20 SCSI 20 mode parameters reading 45 reloading 42 saving 42 setting 42 MODE SELECT command 42 MODE SENSE command 45 page for EXTENDED COPY command MODE SENSE command 45 MOVE MEDIUM command 56...
  • Page 210 106, 118 Shared Library Services (SLS) 16 software license agreement 3 specifications 143r1 (see EXTENDED COPY) Spectra vendor identification value 37, 41 Spectra Logic libraries 16 status BUSY 29 byte codes 28 CHECK CONDITION 28, 91, 104, 105 element 19, 60...
  • Page 211 terms (glossary) 17 TEST UNIT READY command 104 exception 20 tests diagnostic 76, 97 tracking media 19 UNIT ATTENTION alert 42 sense key 106, 118 unsupported sense keys 106 values product identification 38, 41 sense keys 106 vendor identification 37, 41 vendor identification 37, 41 vendor-specific sense keys 106, 118...

This manual is also suitable for:

Spectra 20kSpectra 64k

Table of Contents