1. Manuals
  2. Brands
  3. HP Manuals
  4. Storage
  5. C737990900
  6. Technical reference manual

HP C737990900 Technical Reference Manual

Ultrium drives generation 2 scsi and fc drives volume 3: the scsi interface
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
the SCSI
interface
hp ultrium drives
technical reference manual
generation 2 SCSI and FC drives
volume 3: the SCSI interface
Part Number:
C7379–90900 Volume 3
Edition 4, February 2003

Advertisement

Table of Contents
loading

Related Manuals for HP C737990900

Summary of Contents for HP C737990900

  • Page 1 SCSI interface hp ultrium drives technical reference manual generation 2 SCSI and FC drives volume 3: the SCSI interface Part Number: C7379–90900 Volume 3 Edition 4, February 2003...
  • Page 2 Feb 2003 This document is frequently revised and updated. To find out if there is a later version, please ask your HP OEM Representative. Addition of Read and Write attribute commands and Drive Error Codes Inclusion of the Request Block Address command and the Control mode...

  • Page 3: The Purpose Of This Manual

    The Purpose of this Manual This is one of five volumes that document HP Ultrium drives. This volume provides background information for driver and application developers. The following products are covered. Capacities are when the drive is using data compression with a compression ratio of 2:1, where applicable:...

  • Page 4: Documentation Map

    Documentation Map The following will help you locate information in the 6-volume Technical Reference Manual: Drives—general Connectors Controller architecture Front Panel LEDs Mechanism and hardware Specifications Installation and Configuration Connectors Determining the configuration External drives In Libraries In Servers In Tape Arrays Modes of Usage Optimizing performance UNIX configuration...

  • Page 5: Maintenance And Troubleshooting

    Cartridges Cartridge Memory (LTO-CM) Cartridges Features Managing the use of cartridges Use of cartridges Interface SCSI Guide Commands Error codes Implementation Interpreting sense data Messages Mode pages —see the MODE SENSE command Pre-execution checks Responding to Sense Keys and ASC/Q Sense Keys and ASC/Q —see REQUEST SENSE command Maintenance and Troubleshooting...
  • Page 6 Dealing with Errors Error Codes Handling errors How error correction works Logs—see the LOG SENSE command Recovering from write and read errors Software response to error correction Software response to logs TapeAlert log Ultrium Features Adaptive Tape Speed (ATS) Autoload Automation Control Interface (ACI) Cartridge Memory (LTO-CM)s Data Compression, how it works...

  • Page 7: General Documents And Standardization

    General Documents and Standardization Copies of General Documents can be obtained from: ANSI ECMA Global Engineering Documents Small Computer System Interface (SCSI-1), ANSI X3.131-1986. This is the ANSI authorized standard for SCSI implementation, available through ANSI Enhanced Small Computer System Interface (SCSI-2), ANSI X3T9.2-1993 Rev.

  • Page 9: Table Of Contents

    The Purpose of this Manual 3 Related Documents 3 Documents Specific to HP Ultrium Drives 3 Documentation Map 4 General Documents and Standardization 7 Interface Implementation 13 The SCSI Interface 13 Supported Messages 14 Supported Commands 14 SCSI Features 15...
  • Page 10 Contents Messages 25 Message Out Support (Parallel SCSI only) Message In Support (Parallel SCSI only) Extended Message Support 27 Status 29 Commands—Introduction 31 Summary 31 Command Details 32 Pre-Execution Checks 32 Bad LUN Check 32 Deferred Error Check 33 Diagnostic Status Check 33 Fixed Bit Check 34 Flag Link Check 34 Illegal Command Check 34...
  • Page 11 LOCATE 2Bh 58 LOG SELECT 4Ch 60 LOG SENSE 4Dh 62 Log Page Format 63 Supported Log Pages Page 64 Write Error Counters Log Page 65 Read Error Counters Log Page 66 Sequential Access Device Log Page 66 TapeAlert Log Page 67 Tape Usage Log Page 69 Tape Capacity Log Page 69 Data Compression Log Page 70...
  • Page 12 Contents Host Common Attributes 107 READ BLOCK LIMITS 05h 110 READ BUFFER 3Ch 111 READ POSITION 34h 115 RECEIVE DIAGNOSTICS RESULTS 1Ch 119 RELEASE UNIT 17h/57h 121 REPORT DENSITY SUPPORT 44h 123 REPORT LUNS A0h 126 REQUEST SENSE 03h 128 Request Sense Data 129 Sense Data Management 131 Current Sense 132...

  • Page 13: Interface Implementation

    Interface Implementation HP Ultrium drives use SCSI-3 as the interface to connect to the host system. This chapter gives an overview of how the interface operates. Full details of the messages are given in Chapter 3 The SCSI Interface The Small Computer System Interface (SCSI) is an industry standard, approved by the American National Standards Institute (ANSI).

  • Page 14: Supported Messages

    Supported Messages The following messages are supported by the drives: For implementation details on these messages, see Supported Commands The following commands are supported by the drives. They include all Mandatory and Extended commands and most Optional commands. ERASE INQUIRY LOAD/UNLOAD LOCATE LOG SELECT...

  • Page 15: Scsi Features

    READ BUFFER READ POSITION RECEIVE DIAGNOSTIC RESULTS For implementation details on these commands, see Introduction” SCSI Features Design Approach The features supported by the drive are based on standards, both official and de facto. The drive is fully compliant with the SCSI-3 specification and supports all features required by that standard.

  • Page 16: Abort Handling

    default setting. The known base state is defined in the SCSI-3 specification and includes the following: The drive will be able to respond to SENSE first command other than these from any initiator will get a CONDITION other commands may not be processed until the internal state of the drive has been reset.
  • Page 17 status immediately. A GOOD INQUIRY Command Long erase is aborted as quickly as possible without corrupting tape format. ERASE Short erase completes. None INQUIRY Load completes and logically positions tape at BOT. Unload is aborted LOAD/UNLOAD leaving logical position at BOT unless operation is past the “point of no return”...

  • Page 18: Bus Parity Errors (Parallel Scsi Only)

    Command The command completes. RESERVE UNIT The command completes. REWIND Vendor Unique SEND DIAGNOSTIC The logical position is set back to that at the start of the operation unless the SPACE operation has passed its “point of no return”, in which case the operation completes.

  • Page 19: Disconnect Strategy (Parallel Scsi Only)

    ABORTED COMMAND Error). If the subsequent message is rejected with an Message Parity Error, then the drive goes to Status phase and sends is set to ABORTED COMMAND error). On detecting a bus parity error during a Message Out phase, the drive will handshake in all message bytes until ATN is deasserted.

  • Page 20: Fibre Channel Operation

    There at least eight different name formats distinguished by the Network Address Authority (NAA). Only one is used on HP Ultrium drives. This is the IEEE Registered Name (NNA=5) and has the following format:...

  • Page 21: Addresses

    The second (last bits = 01) is used as the Port B World Wide Name. The third name (last bits = 10) is used for the Device World Wide Name. (These are assigned during manufacture from HP’s pool of names, although only the first will actually be stored in the drive NV-RAM).

  • Page 22: Implications For Libraries

    The values of the names can be obtained using the Device Identification Vital Product Information Page (part of the Implications for Libraries Interface Implementation Normally a standalone drive will operate using its own ‘hard’ names. The drive knows it is in a library or other ‘managed’ environment since one of the signal lines on the ACI (Automation Control Interface) will be tied down.

  • Page 23: Field Replaceable Units

    These codes turn up in sense data byte 14 and as the sense code qualifier for sense codes 4400h (internal target failure) and 40XX (diagnostic failure). Although there are no actual Field Replaceable Units on HP Ultrium drives, the following sub-assemblies can be replaced at Repair Centres: Drive PCA...
  • Page 24 Signal Name Driven by Message -MSG Request -REQ Acknowledge -ACK Attention -ATN Reset -RST DB(15-0) Data Bus DB(P1-P0) Data Bus Interface Implementation True (low) Input to the initiator False (high) Output from the initiator Target Indicates a Message phase on the bus. True (low) Message phase False (high)

  • Page 25: Messages

    Messages This chapter includes all SCSI messages, both supported and unsupported. Parts of this chapter come from Section 5, Logical Characteristics, of the SCSI standards (see page 13). The message system provides an initiator and a target on the SCSI bus with a means of managing communication.

  • Page 26: Message In Support (Parallel Scsi Only)

    Name Code Message Parity The initiator has detected a parity error in a message. The drive will retry the message. (See Error details). If the message is received immediately after an Identify message or after the Command Complete message has been sent, the drive will go Bus Free.

  • Page 27: Extended Message Support

    Name Code This message is sent by the drive to the host to indicate that a byte on a Ignore Wide wide bus is not valid. Residue This is supported whenever a wide transfer is active. It should be sent at the end of the data phase.
  • Page 28 Name Code Parallel Protocol Request Synchronous Data Transfer Request Wide Data Transfer Request Parallel Protocol Request Messages The drive will never initiate a Parallel Protocol Request transfer negotiation but will expect the initiator to do so. If the message is received after selection and before the command phase, it will then go to message-in phase and respond with a valid response to complete the negotiation.

  • Page 29: Status

    CHECK CONDITION: Any error, exception, or abnormal condition that causes sense data to be set returns CHECK CONDITION following this status to determine the nature of the error. CONDITION MET: This status will never be returned by an HP Ultrium tape drive. Req/Ack Offset Transfer Width Exponent Reserved (0)
  • Page 30 Reservation check. COMAND TERMINATED: This status will never be returned by an HP Ultrium tape drive. QUEUE FULL: This status can be returned by an HP Ultrium FC drive but will never be returned by a SCSI tape drive. Messages...

  • Page 31: Commands-Introduction

    Commands—Introduction This chapter contains general notes relating to the SCSI commands listed in Chapter Summary The following table is a summary of the SCSI commands for sequential access devices, showing the operation code: Opcode Command Name (hex) TEST UNIT READY REWIND REQUEST SENSE READ BLOCK LIMITS...

  • Page 32: Command Details

    Command Details The command descriptions in this section are listed in alphabetical order of command name. Each command is described briefly. This is followed by a list of pre-execution checks which are described below. The Command Descriptor Block (CDB) is then given, with details of the various parameter bits and fields. Pre-Execution Checks Note Before executing a command, the drive makes a number of checks.

  • Page 33: Deferred Error Check

    If no Command Descriptor Block. If an Descriptor Block is ignored If the LUN is unsupported, and the host command is not CHECK CONDITION REQUEST If the LUN is unsupported, and the host command is original sense data is replaced with a sense key of additional sense of 2500h (logical unit not supported).

  • Page 34: Fixed Bit Check

    Fixed Bit Check For the the length parameter of the command is for fixed block mode. If fixed block mode is selected then the block size in the Mode Select block descriptor must not be zero. Otherwise set as described for the Flag Link Check This check ensures that the host has not set the Flag bit in the control byte of the command without setting the Link bit as well.

  • Page 35: Media Access Check

    The sense key specific bit is set and the sense key specific bytes will be a field pointer. The command/data bit is set, indicating that the illegal parameter was in the command. Note Media Access Check This checks if the drive is able to perform media access commands. If the media is inaccessible then key of NOT READY...

  • Page 36: Media Information Check

    Media Information Check During power-on and following a SCSI reset, knowledge of the whereabouts of the cartridge is unavailable. It is not possible to execute commands which assume that this knowledge is available until the drive has recovered from the power-on or reset.

  • Page 37: Media Write Check

    Media Write Check This checks whether the media is write-protected. If it is, reported with a sense key of (write-protected). Parameter List Check LOG SELECT associated data sent to the drive is in the form of parameter lists. These are described under the command names in the next chapter.

  • Page 38: Unit Attention Check

    Unit Attention Check This checks if a command. If it does, the drive reports key of unit attention condition which exists. See Unit Attention Sense in the description of the Command Descriptor Block A SCSI command descriptor block (CDB) is a sequence of 6, 10, 12 or 16 bytes sent by a host to a SCSI target with the bus in command phase.
  • Page 39 A reserved field should always be set to zero. The drive checks reserved fields, and if one is Reserved non-zero then it will reject the command with Multi-Byte A multi-byte parameter field in a command is “big-endian”, that is, bit 7 of the first byte of this field is the most significant.
  • Page 40 Commands—Introduction...

  • Page 41: Commands

    Commands This chapter describes all SCSI commands. Parts of the chapter are based on sections of the SCSI specification (see page 13). For general notes on the command descriptions, see Chapter Commands...

  • Page 42: Erase 19H

    ERASE position. The Long bit is used to decide whether the ‘old’ data is physically overwritten or not. Pre-Execution Checks: Illegal Field Media Access Command Descriptor Block: CDB Fields: Immed Long Note Commands command is used to erase data on tape from the current logical ERASE Reservation Media Write...
  • Page 43 Warning EOM (drive error code 2C98h) will only be given if the tape was logically positioned past EOT immediately prior to this command. Erase Specific Status: Event Status Additional Sense The erase fails CHECK CONDITION HARDWARE ERROR 5100h (erase failure) Commands...

  • Page 44: Inquiry 12H

    INQUIRY NQUIRY parameters to the host. These parameters cannot be changed. The drive returns Inquiry data to the host in a data-in phase. Note Pre-Execution Checks: Only the Illegal Field Check is performed before the command is executed. If the EVPD bit is clear, the page code must be zero, otherwise reported.

  • Page 45: Inquiry Data Pages

    If the EVPD bit is zero the Page Code field must be zero. Page Code If the EVPD bit is set to 1, the drive returns the Inquiry page in this Page Code field: Supported Vital Product Pages page Unit Serial Number page Device Identification page Firmware Revision Levels page Hardware Revision Levels page...
  • Page 46 (RMB) flag is set to 1 and the Device-type modifier is set to 0. Commands Reserved (0) EncSvr(0) VS(0) MultiP Obsolete WBus16 Sync Vendor Identification (“HP Product Identification Product Revision Level Reserved (0) Reserved (0) Reserved (0) Version Descriptor 1 - - - - - - - - Version Descriptor 8 Reserved (0)
  • Page 47 Inquiry Data Fields 000b There is a device on the logical unit selected, so the LUN field in the identify Peripheral Qualifier message was 0. 011b The LUN field in the identify message has specified an unsupported logical unit. This means any LUN other than 0. Peripheral Device Sequential Access Device Type...
  • Page 48 Vendor A vendor-specific, 8-byte string of ASCII characters, left justified and padded with space Identification characters “HP”. Product Identification A left-justified, vendor-specific, 16-byte string field of ASCII characters with space character padding on the right. The string consists of two parts: First half (bytes 16–23): “Ultrium”...

  • Page 49: Vital Product Data Pages

    These fields can be used to identify up to eight standards to which the drive conforms. The Version Descriptor values supported are listed below. For SCSI drives, it is recommended that the first version descriptor is used for the SCSI architecture standard, followed by the physical standard, if any, followed by the SCSI protocol, followed by the appropriate SPC version, followed by the device type command set, followed by the secondary command set, if any.

  • Page 50: Unit Serial Number

    This page contains a list of all the VPD page-codes supported by the drive. Peripheral Qualifier (0) Unit Serial Number Page The Unit Serial Number Page contains a single value which is a 10-byte ASCII string. The string, with the Vendor Identification and Product Identification fields in the standard Inquiry data, uniquely identifies the drive.

  • Page 51: Device Identification

    Device Identification Page The Device Identification page contains information that identifies the tape drive uniquely. For SCSI, a combination of the Vendor ID and Serial Number is returned. For Fibre Channel, the Port and Device Names are returned as well. Peripheral Qualifier (0) (MSB) Identification Descriptors are constructed as follows:...
  • Page 52 Device Serial Number (FC and SCSI) (MSB) (MSB) (MSB) Port Name (FC only) (MSB) Device Name (FC only) (MSB) Commands Reserved (0) Reserved (0) Reserved (0) Identifier Length (34) Vendor ID Product Identification Serial Number Reserved (0) Reserved (0) Reserved (0) Identifier Length (8) Port Name (IEEE Registered Name)

  • Page 53: Drive Component Revision Levels Pages

    Port Identifier (FC only) (MSB) The Port Identifier will be set to 1 if the addressed port is port A, and set to 2 if the addressed port is Port B. SCSI Type 3 Identifier (SCSI only) (MSB) Drive Component Revision Levels Pages Peripheral Qualifier (0) (MSB) Reserved (0)
  • Page 54 (MSB) (MSB) (MSB) The Drive Component Revision Levels pages contain details of the revisions of each of the major sub assemblies of the drive. For any given product, if these pages are the same then the drive has been built with the same components and with the same manufacturing process.

  • Page 55: Load/Unload 1Bh

    LOAD/UNLOAD LOAD present in the drive is either made ready for data transfer (“loaded”) or disabled for data transfer (if Prevent Media Removal is set). It can also cause the cartridge to be ejected from the drive (“unloaded”). Pre-Execution Checks: Illegal Field Unit Attention If an unload is to be performed, the drive checks if the tape is currently being...
  • Page 56 0 A normal load/unload will be performed. Hold 1 A load will cause the cartridge to be pulled in and seated in the drive, but the tape will not be threaded. An unload will cause the tape to be unthreaded, but the cartridge will not be ejected. In Hold position, the Cartridge Memory is accessible.

  • Page 57: Unloading A Cartridge

    If the Load was issued by some other host (or was an autoload) and completed successfully, CHECK CONDITION and additional sense of 2800h (not ready to ready UNIT ATTENTION transition). If the Load was issued by the current host and failed, reported, since a deferred error condition will exist for the current host.

  • Page 58: Locate 2Bh

    LOCATE specified by the command. The new position is specified by the offset from start of the media in terms of blocks. The first block (that is, BOT) is block address 0. Any unwritten data is written to tape before the command is executed. Pre-Execution Checks: Illegal Field Unit Attention...
  • Page 59 The Block Address specifies the number of blocks and filemarks between BOM and the Block Address position to be located. Partition Not supported. Locate Specific Status: Event Status EOD encountered CHECK CONDN EOM encountered CHECK CONDN Failed to read data—media CHECK CONDN error or non-fatal drive error...

  • Page 60: Log Select 4Ch

    LOG SELECT value or to be set to an initiator specific value. Pre-Execution Checks: Illegal Field Command Descriptor Block: (MSB) CDB Fields: The following are valid combinations of values for the PCR (Parameter Code Reset), Parameter List Length and PC (Page Control) fields: Parameter List Length Otherwise REQUEST...
  • Page 61 The Save Page (SP) flag is not supported and must be set to 0. The Page Control field defines the type of parameter values to be selected: No operation is performed. The Parameter List Length must be zero. If it is not, check condition invalid field in CDB is set.

  • Page 62: Log Sense 4Dh

    LOG SENSE LOG SENSE with each invocation of Pre-Execution Checks: Illegal Field The Page Code must match one of the supported log page codes. If it does not, then the Illegal Field Checks. Command Descriptor Block: (MSB) CDB Fields: The Page Control field defines the type of log parameter to be returned: 00b Current Threshold Values—any parameters in the log that are counters contain the maximum value that they can count to.

  • Page 63: Log Page Format

    11b Default Cumulative Values—any parameters in the log that are counters contain the initial values of those counters (set at power-on, reset, bus device reset and, in the case of media logs, load). The PC field has no effect on the data returned when the selected log contains event or trace codes rather than counts.

  • Page 64: Supported Log Pages Page

    (MSB) Parameter Code A two-byte value that uniquely identifies the parameter within the log. DU, TSD, ET and TMC 0 Must be zero. For a full description of these fields refer to the SCSI-2 standard. and LP 1 Must be 1, indicating that drive will maintain the saving of data itself. Note that LBIN 0 The parameter consists of ASCII characters.

  • Page 65: Write Error Counters Log Page

    (MSB) Write Error Counters Log Page The Write Error Counters log is page 02h. The Page Length is 38h. There are seven parameters, 0 through 6. Parameters 0 through 2 are not supported and are returned as zero. All fields are four bytes long. All these counters are updated when the data set is physically written.

  • Page 66: Read Error Counters Log Page

    Read Error Counters Log Page The Read Error Counters log is page 03h. The Page Length is 38h. There are seven parameters, 0 through 6. Parameters 0 through 2 are not supported and are returned as zero. All fields are four bytes long. All these counters are updated when the data set is physically read.

  • Page 67: Tapealert Log Page

    A non-zero value of the cleaning required parameter indicates that a condition requiring cleaning has been detected and a subsequent cleaning cycle has not yet been completed. The cleaning required parameter shall be persistent across hard resets and power cycles. TapeAlert Log Page The TapeAlert log page is page 2Eh.
  • Page 68 Parameter Commands Description Memory in Cartridge Failure Forced Eject Read-Only Format Tape Directory Corrupted Nearing Media Life Clean Now Clean Periodic Expired Cleaning Media Invalid Cleaning Cartridge Drive Maintenance Hardware A Hardware B Interface Eject Media Download Fault Drive Humidity Drive Temperature Drive Voltage Predictive Failure...

  • Page 69: Tape Usage Log Page

    Tape Usage Log Page The Tape Usage Log Page code is 30h. There are nine parameters. These are all read directly from the LTO-CM Tape Usage Log. This data can be neither reset nor written. Parm. Tape Capacity Log Page The Tape Capacity Log Page code is 31h.

  • Page 70: Data Compression Log Page

    Data Compression Log Page The Data Compression Log Page code is 32h and the page length is 4Ch. There are ten parameters, 0 through 9. Parameters 0 and 1 are two bytes long. Parameters 2 through 9 are each 4 bytes long. The supported fields are listed below.
  • Page 71 Parameter Description Maximum data rate Current data rate Native data rate All the parameters relate to the current tape. They are all cleared when the tape is unloaded, except Parameter 4, which is never cleared. All data will be reset when the log page is reset. The parameters are as follows. Number of tape direction changes per 100 MB written.

  • Page 72: Mode Select 15H/55H

    MODE SELECT ODE SELECT 10-byte versions of the command are supported. The Mode Select parameter list is transferred from the host to the drive during the data-out phase. It contains zero or more bytes of information. If any information is sent, it should consist of a Mode Parameter Header followed by zero or more mode select pages.
  • Page 73 Reserved (0) 10-Byte version Reserved (0) (MSB) (MSB) CDB Fields: Page Format MODE SELECT parameter header and block descriptor may be sent. The parameter data is SCSI-2 mode-page compatible. Save Pages This bit is not supported and must be zero. No data is transferred.

  • Page 74: Mode Parameter Pages

    key is set to parameters changed). Mode Parameter Pages Mode data is recovered from the drive by means of a After modification, it is returned to the drive via a real-life, many hosts do not use data suits them into the drive. Mode Page Representation Certain conventions are used in the following Mode Parameter pages in order to describe the nature of the parameters.
  • Page 75 (MSB) (MSB) Mode Parameter Pages HP Ultrium drives support the following pages: “Read-Write Error Recovery Mode Page” on page 78 “Disconnect-Reconnect Page” on page 79 “Control Mode Page” on page 81 “Data Compression Log Page” on page 70 “Device Configuration Page” on page 83 “Medium Partitions Mode Page”...
  • Page 76 10-byte Header The 10-byte Mode Parameter header has the following format: (MSB) (MSB) Header Fields Mode Data Length MODE SELECT: MODE SENSE: 00h The usual medium type when the drive is in normal tape drive mode. Medium Type Write Protect. Ignored for ODE SENSE ODE SENSE The drive will not report...

  • Page 77: Mode Block Descriptor

    The drive will report as all the data or marks specified in the command have been transferred to the data buffer and all buffered data from different initiators has been successfully written to the tape. This is the maximum value. Speed The Speed field is not used and should be zero.

  • Page 78: Read-Write Error Recovery Mode Page

    Read-Write Error Recovery Mode Page The Read-Write Error Recovery Mode Page has the following format: PS (0) Reserved (0) 4–7 9–11 Read-Write Error Recovery Page Fields: Transfer Block Always set to 0, meaning that an unrecoverable data block will not be transferred to the host.

  • Page 79: Disconnect-Reconnect Page

    The number of times the drive will attempt its recovery algorithm during a read operation Read Retry Count before reporting an unrecoverable error. The drive will not use its recovery algorithm during read operations. 15h The drive will attempt 21 retries. Write Retry Count The number of times the drive will attempt its recovery algorithm during a write operation before reporting an unrecoverable error.

  • Page 80: Fc Drives

    FC Drives The Disconnect-Reconnect Page has the following format for FC drives: PS (0) (MSB) (MSB) (MSB) (MSB) EMDP (0) 13–15 Disconnect-Reconnect Page Fields: 0 Buffer management is controlled by the drive, so this should always be zero. Buffer Full Ratio Connect Time Limit 0 Buffer management is controlled by the drive, so this should always be zero.

  • Page 81: Control Mode Page

    FAA (FC only) This bit, together with FAB and FAC, indicate whether the drive will use fairness arbitration to send frames to the initiator. 0 The drive will not use fairness when arbitrating to send FCP_DATA frames. 1 The drive will use fairness when arbitrating to send FCP_DATA frames. FAB (FC only) 1 The drive will use fairness when arbitrating to send FCP_XFER_RDY frames.

  • Page 82: Data Compression Characteristics Page

    Control Mode Page Fields: Autoload Mode If a cartridge is inserted, the drive pulls it in and threads the tape. 1 or When a cartridge is inserted, the drive pulls it in but does not thread the tape. In this position, only the Cartridge Memory is accessible.

  • Page 83: Device Configuration Page

    Data Decompression Enable Read only. It will have the value of 1, indicating that compression is enabled. Report Exception on Decompression Read only. It will have the value 0, meaning that the drive returns status when it encounters data that cannot be decompressed. This applies when data has been compressed with an unknown or unsupported compression algorithm.
  • Page 84 Pre-Execution Checks: The only check made when this page is sent in Mode Select data is Parameter List. Changeable Parameters: Write Delay This field can be modified by a Time subsequent MODE SENSE as zero, and so the data in the buffer will never be flushed. The default value is zero. The field is fully supported.

  • Page 85: Medium Partitions Mode Page

    0 The Report Set Marks flag should be clear since this feature is not supported. Rsmk 0 The Automatic Velocity Control flag should be clear since velocity control is managed by the drive. SOCF 0 The Stop On Consecutive Filemarks flag should be clear since this feature is not supported. 0 The Recover Buffer Order flag should be clear since this feature is not supported.

  • Page 86: Fibre Channel Logical Unit Control Mode Page

    None of the fields in this mode page are changeable. Maximum Additional Partitions Additional Partitions Defined POFM CLEAR ADDP Medium Format recognition PSUM Partition Units Partition Size Fibre Channel Logical Unit Control Mode Page This page is supported for Fibre Channel only: PS (0) 4–7 Commands...

  • Page 87: Fibre Channel Port Control Mode Page

    0 The target does not use the precise delivery function and ignores the contents of the CRN field EPDC in the Fibre Channel Extended Link Service FCP_CNTL. HP Ultrium drives support this feature by default. 1 The logical unit uses the precise delivery function defined in the FCP-2 standard. It makes use of the CRN field.
  • Page 88 Disable Loop Master. 0 The target may become loop master during the loop initialization process. 1 The target does not become loop master. It only repeats LISM frames it receives. This allows the initiator to be loop master during loop initialization. Require Hard Address 0 The target follows the normal initialization procedure, including the possibility of obtaining a soft address during the loop initialization process.

  • Page 89: Information Exceptions Mode Page

    Information Exceptions Mode Page The Information Exceptions Mode page is used to control exception reporting through the PS (0) Rsvd (0) Perf (0) (MSB) (MSB) 0 Informational exception operations that cause delays are acceptable. Perf Disable Exception Control. It must be zero when the Test Flag Number is zero. When the Test DExcpt Flag Number contains a valid non-zero value, the DExcpt flag can be 0 or 1.
  • Page 90 0 Log Errors bit. This bit must be zero, indicating that the logging of informational LogErr exception conditions within the drive is vendor-specific. Method of Reporting Informational Exceptions MRIE 3h This field indicates the method used by the target to report informational exception conditions and must be set to 3.

  • Page 91: Mode Sense 1Ah/5Ah

    MODE SENSE ODE SENSE which configuration parameters can be changed through The mode sense header, block descriptor (optional), and zero or more of the are sent to the host. Mode pages contain drive configuration parameters. Some of these parameters are fixed, others are configurable (through the MODE SELECT which drive parameters are configurable and what their current values are before using mode select to alter them.
  • Page 92 10-Byte Version (MSB) (MSB) CDB Fields: Disable Block Descriptors flag Allows the drive to return the Prevents the drive from returning the Page Control—Indicates the type of page parameter values to be returned to the host, as shown in the following table: Report Current Values: the current values of the parameters are returned.
  • Page 93 Any mode The drive returns that page. page code The drive returns all mode pages. Allocation Specifies the number of bytes that the host has allocated for returned MODE SENSE data. Length No data transfer will occur. This is not considered an error. The maximum number of bytes which the drive should return in its data-out phase.

  • Page 94: Prevent/Allow Medium Removal 1Eh

    PREVENT/ALLOW MEDIUM REMOVAL PREVENT removal of the cartridge. When cartridge removal is prevented, the front panel eject button is completely disabled (though a ‘forced eject’ will still work). An Unload command issued by a host will result in REQUEST When cartridge removal is enabled, pressing the front panel eject button or sending an Unload command from a host will cause the media to be unloaded and ejected.

  • Page 95: Read 08H

    READ transfers zero or more data blocks to the host starting at the current READ logical position. Pre-Execution Checks: Illegal Field Unit Attention If both the SILI and Fixed bits are set, Sense data is as described in the Illegal Field Checks. The field pointers indicate the Fixed bit field.
  • Page 96 If the fixed flag is set and the Transfer Length field is not zero and the Suppress Illegal Length Indicator (SILI) flag is clear, a sequence of blocks of the currently configured block length is to be returned, the number of blocks being indicated in the Transfer Length field.
  • Page 97 The Transfer Length field specifies the length of the transfer in blocks. The size of each block (in bytes) is specified by the current block length specified in the Mode Parameter block descriptor. If SILI = 0, a sequence of blocks of the currently configured block length is to be returned, the number of blocks being indicated in the Transfer Length field.
  • Page 98 Event Status Failure to read data CHECK MEDIUM through media COND’N ERROR error or non-fatal drive error Corrupt data CHECK MEDIUM format COND’N ERROR Blank media CHECK BLANK encountered during COND’N CHECK a read Note Residue Information: The Valid bit will be set. The information bytes will be as follows: Variable Block Mode The requested transfer length (in bytes).

  • Page 99: Read Attribute 8Ch

    READ ATTRIBUTE READ ATTRIBUTE values to MAM (Medium Auxiliary Memory) and also to discover what MAM exists at the device server. Pre-Execution Checks: Illegal Field Bad LUN Unit Attention If the MAM is not accessible because there is no tape in the drive, CONDITION of 3A00h (medium not present).
  • Page 100 (MSB) (MSB) CDB Fields: Service Action Service actions are defined as follows. The data returned for each Service Action is described below. Code Attribute Values Attribute List Volume List Partition List 04h–1Fh Reserved Element Address Set to zero to indicate that Ultrium tapes only support a single element. Set to zero to indicate that Ultrium tapes only support a single element.
  • Page 101 Returned Data for Service Actions: Attribute Values Service Action This service reads the values of attributes for the specified volume and partition, starting at the First Attribute ID. The attributes are returned in ascending numerical order. The format of the returned data is as follows: (MSB) For details of the available attributes and the format of the data returned for each, see...
  • Page 102 The Available Data field specifies the length in bytes of the following data. If the amount of parameter data sent to the application client is reduced due to insufficient allocation length, the Available Data field shall not be altered. A two-byte Attribute ID is returned for each attribute available on the device server.

  • Page 103: Mam Attribute Data

    The Number of Volumes Available indicates the number of partitions available. Since Ultrium drives do not support multiple volumes, this is 1. MAM Attribute Data Attribute data sent with a to a READ ATTRIBUTE (MSB) Read-Only (MSB) (MSB) The format implies nothing about the physical representation of the data in the Medium Auxiliary Memory.

  • Page 104: Attribute Id Values

    Attribute ID Values The values in the Attribute ID field are assigned according to the source of changes or updates as follows. Device Common Attributes The device server maintains and updates the contents of these attributes within the MAM when it and the associated tape are present. All the attributes are read-only (Read-Only bit set to 1).
  • Page 105 Remaining Capacity in Partition Maximum Capacity in Partition Load Count MAM Space Remaining Device Make/Serial Number at Last Load Device Make/Serial Number at Load – n (MSB) (MSB) The same value as is returned in the SCSI Vendor Identification device server. return ASCII spaces (20h).

  • Page 106: Medium Common Attributes

    Partition Usage History Product Serial Number Total MB Written in Medium Life Total MB Read in Medium Life Total MB Written in Current/ Last Load Total MB Read in Current/Last Load Medium Usage History Medium Common Attributes These attributes are hard coded into the MAM at manufacture time. The attributes defined are shown in Table 16.

  • Page 107: Host Common Attributes

    The MAM Capacity is the total capacity of the MAM, in bytes, at manufacture time. It does not indicate the free space of a ‘blank’ MAM as some of the MAM space may be reserved for device-specific use that is inaccessible to the application client.
  • Page 108 The Application Name identifies the name of the application client. The Application Version identifies the version of the application client. The User Medium Text Label is the user level identifier for the medium. The Data & Time Last Written specifies when the application client last wrote to the MAM.
  • Page 109 The Partition User Text Label is a user level identifier for the partition specified in the CDB Partition Number field The Load/Unload at Partition attribute indicates whether the media can be loaded or unloaded at the Partition specified in the CDB Partition Number field.

  • Page 110: Read Block Limits 05H

    READ BLOCK LIMITS EAD BLOCK LIMITS size that it can support. Note that this is the maximum supportable, not the fixed block size. Pre-Execution Checks: Illegal Field Command Descriptor Block: Read Block Limits Data: (MSB) (MSB) 110 Commands tells the drive to return data defining the maximum block Reservation Deferred Error Operation Code (05h)

  • Page 111: Read Buffer 3Ch

    READ BUFFER EAD BUFFER initiator. The value of the Mode field determines whether only the 4-byte descriptor is returned, only the data is returned, or whether both are returned. Pre-Execution Checks: Illegal Field If any of the following rules are broken then reported.
  • Page 112 00011b The drive returns a 4-byte descriptor for the buffer identified by the Buffer ID field. Invalid buffer IDs will return a buffer descriptor of all zeros. The Buffer Offset field must be zero. 01010b The drive returns data from the Echo Buffer. The Buffer ID and Offset are ignored. 01011b The drive returns the Echo Buffer descriptor.

  • Page 113: Returned Data

    Not all of the Processor Memory space is accessible. The following table shows valid Processor Memory address segments: Segment Start Address 000000h 180000h 200000h 240000h 280000h FF8000h SCSI Burst Buffer SCSI drives: 192 KB FC drives: 7F0000 bytes Size = 4 KB LTO-Cartridge Memory Size = 8 KB Mechanism EEPROM...
  • Page 114 (MSB) The format of the 4-byte Echo buffer descriptor for Mode 01011b is as follows: (MSB) 114 Commands Buffer Capacity Reserved (0) Echo Buffer Size (1000h) (LSB) EBOS (1) (LSB)

  • Page 115: Read Position 34H

    READ POSITION READ POSITION position to the host. The position is the count of all marks and blocks between BOM and the current logical position. The first block is block 0. Two forms of the command are supported, the ’traditional’ short form with BT=0 and a new (SCSI-2) long form where a distinction between partitions, marks and blocks is drawn.
  • Page 116 Block address Type The Long bit and the TCLP bit must be equal. If they are not, the command will terminate with REQUEST Returned Data—Short Read Position: The format of the 20 bytes of data returned in short format for is as follows: (MSB) (MSB)
  • Page 117 Block Position Unknown The First and Last Block Location fields are valid. Block position is unknown. First and Last Block Location fields are undefined. This will only occur after a “hard” read error that has caused a sense key of additional sense of 3B00h (sequential positioning error).
  • Page 118 Mark Position Unknown The File Number and Set Number fields are valid. Mark position is unknown. If set, then the File Number and Set Number fields are undefined. This would be set only after a “hard” read error which resulted in the setting of positioning error sense such as 3B00h (sequential positioning error).

  • Page 119: Receive Diagnostics Results 1Ch

    RECEIVE DIAGNOSTICS RESULTS ECEIVE DIAGNOSTIC RESULTS diagnostic test requested through the SEND DIAGNOSTIC command. If none has been sent, the data refers to the power-on self-test. Pre-Execution Checks: Illegal Field Command Descriptor Block: (MSB) CDB Fields: The page code is valid. This flag must be set. Page Code Identifier for the diagnostic information page to be returned.
  • Page 120 If other invalid pages are requested, ILLEGAL REQUEST supported”. Data Returned Page Code 70h — Self-Test (Read/Write) Page Format for Write: (MSB) No parameters are needed. Sending this page is equivalent to a Diagnostic Page Format for Read: (MSB) (MSB) 120 Commands CHECK CONDITION and additional sense of 2601h, “parameter not...

  • Page 121: Release Unit 17H/57H

    RELEASE UNIT ELEASE UNIT drive. Reserving a device is a way of ensuring exclusive access to that device from a single initiator for the period of the reservation. The drive may be reserved using a The 10-byte RELEASE UNIT command is supported by all drives. Its functionality is the same as for the 6-byte command, but it also supports third- party reservation.
  • Page 122 (MSB) 10-Byte Only 3rd Pty LongID This is always zero because device IDs greater than 255 are not supported. This is required and used only when the 3rd Pty bit is set. The device will perform the Third-Party Device ID release operation only if the initiator ID, the 3rd Pty bit and the Third-Party Device ID are identical to those in the The drive ignores any attempt to release the reservation made by any other initiator,...

  • Page 123: Report Density Support 44H

    REPORT DENSITY SUPPORT Report Density Support supported by the drive. The data is returned as a header and a series of descriptor blocks. Pre-Execution Checks Illegal Field Command Descriptor Block (MSB) CDB Fields Media One descriptor block is returned for each format supported by the drive. The capacity field in the descriptor block will indicate the capacity of the current media.
  • Page 124 Header (MSB) The available length gives the total amount of data that is available to be returned. Descriptor Blocks The header is followed by one or more Report Density Support descriptor blocks with the following format: WRTOK (MSB) (MSB) (MSB) (MSB) (MSB) 124 Commands...
  • Page 125 (MSB) (MSB) The values reported for the Ultrium 2 format tapes are as follows: Primary Density Code Secondary Density Code WRTOK The Write OK flag indicates whether the drive can write at the density indicated by the Density Code. The Duplicate flag will be set to zero for every descriptor block indicating that each density is only reported once.

  • Page 126: Report Luns A0H

    REPORT LUNS Description: logical units the drive supports. The standard drive only has a single LUN. Pre-Execution Checks: Illegal Field Command Descriptor Block: (MSB) CDB Fields: Allocation Length Data Returned: (MSB) (MSB) 126 Commands command allows the host to retrieve information about what Report LUNS Operation Code (A0h) Reserved (0)
  • Page 127 List of LUNs (MSB) LUN 0 (0) (LSB) Commands 127...

  • Page 128: Request Sense 03H

    REQUEST SENSE host during a data-in phase. The data is valid in the following circumstances: Positional sense data is valid whenever media is present and loaded and no higher priority sense data is present. An unsolicited request sense (that is, one with no preceding data, which will be all zeros.

  • Page 129: Request Sense Data

    CDB Fields: Logical Unit This field is ignored. Number Allocation No data is transferred to the host. Length >0 The maximum amount of sense data in bytes that should be transferred to the host. The drive returns up to Allocation Length bytes of data; any extra sense data is lost. Request Sense Data The following diagram shows the format of the data returned for the command following the reporting of...
  • Page 130 Returned Sense Data Fields: Valid Indicates that the information bytes contain valid information as defined in the SCSI specification. 70h Indicates that the error is current, that is, it is associated with the command for which Error Code CHECK CONDITION 71h Indicates that the error is deferred.

  • Page 131: Sense Data Management

    The codes should not be relied on by “generic” host drivers, since these are specific to the product. For a list of codes, see Integration Guide, Volume 1 of the HP Ultrium Technical Reference Manual The drive is OK.

  • Page 132: Current Sense

    Unless otherwise stated, all the following descriptions apply to the sense data for a single host whose command is being executed. Current Sense Current sense is the data that is returned in response to a command. It is modified or updated in the following circumstances: Clearing Current Sense: Clearing the Current sense involves setting sense fields as follows: UNIT ATTENTION Sense...

  • Page 133: Deferred Error Sense

    Power On, SCSI Reset, Bus Device Reset Media inserted A load command executed by a third party Mode Sense parameters changed by another initiator Drive firmware has been updated NIT ATTENTION that has Unit Attention as part of its pre-execution checks. When the Unit Attention pre-execution check fails, the Current sense and ATTENTION...
  • Page 134 When any one of the above occurs, the sense generated will be ERROR Attention as part of its pre-execution checks. When the Deferred Error pre- execution check fails, the to issue a otherwise the data will be lost. Write-Behind Deferred Errors: If the Buffered Mode field of the data buffering is enabled.

  • Page 135: Sense Keys

    Sense Keys The following table lists the sense keys that may be returned by HP Ultrium drives. SCSI sense keys are 4-bit codes returned in the sense data. They indicate in what general area the problem that has just been experienced falls.

  • Page 136: Additional Sense Codes

    Never returned by HP tape drives Additional Sense Codes This section contains a list of all the additional sense codes that an HP Ultrium drive can return, in numerical order. The Sense Keys under which each code could appear are also listed. The ASCQ bytes are present at bytes 12 and 13 of the sense data.
  • Page 137 Code Description 04 00h LUN not ready, cause not reportable LUN in process of becoming ready 04 01h LUN not ready, Initializing command required A tape is present in the drive but is not logically loaded. A 04 02h 04 03h LUN not ready, manual intervention required A tape is present in the drive but could not be loaded or Immediate mode command in progress 04 07h 04 10h Media Auxiliary Memory is not accessible...
  • Page 138 Code Description SCSI bus reset 29 02h Bus device reset 29 03h 29 04h Internal firmware reboot Transceivers to SE 29 05h 29 06h Transceivers to LVD Mode parameters changed 2A 01h 30 00h Incompatible medium installed Unknown format 30 01h 30 02h Cannot read media: incompatible format Cleaning cartridge installed 30 03h...
  • Page 139 Code Description 3B 00h Sequential positioning error Invalid bits in Identify message 3D 00h 3E 00h Logical unit has not self-configured yet Microcode download 3F 01h Echo buffer overrun 3F 0Fh 3F 11h Media Auxiliary Memory accessible Diagnostic failure on component XX 40 XX h Message error 43 00h...

  • Page 140: Error Codes

    Bad microcode detected 82 83h Error Codes The error codes that can be reported in bytes 16 and 17 are listed in Chapter 10 of the Hardware Integration Guide, Volume 1 of the HP Ultrium Technical Reference Manual. 140 Commands Explanation...

  • Page 141: Reserve Unit 16H/56H

    RESERVE UNIT This command enables the host to reserve the drive. Reserving a device is a way of ensuring exclusive access to that device from a single initiator for the period of the reservation. Once reserved, the drive will execute commands received from the reserving initiator or from the third-party initiator if the 3rd-Pty option has been selected.
  • Page 142 3rdPty This is always zero because third-party reservation is not supported. This is always zero because third-party reservation is not supported. Third-Party Device ID 10-Byte (MSB) 3rd Pty LongID This is always zero because device IDs greater than 255 are not supported. 142 Commands Reserved (0) 3rd Pty(0)
  • Page 143 This is required and used only when the 3rd Pty bit is set, in which case this field Third-Party Device ID specifies the SCSI ID of the initiator to be granted the reservation of the logical unit. The drive preserves the reservation until one of the following occurs: It is superseded by another valid It is released by the same initiator with a third-party the same value in the Third-Party Device ID field.

  • Page 144: Rewind 01H

    REWIND EWIND Before rewinding, the drive writes any write-behind data in the buffer to tape. Once a rewind is started, it will complete even if the SCSI operation is aborted (for example, if the host selects and sends an abort message). Pre-Execution Checks: Illegal Field Unit Attention...

  • Page 145: Send Diagnostic 1Dh

    SEND DIAGNOSTIC END DIAGNOSTIC diagnostics specified in the parameter list on itself. The parameter list is transferred to the drive in a series of data-out phases; each 8-byte data-out phase specifies a diagnostic to be performed by the drive. It is not an error to set Self-Test = 0 and to have a zero-length parameter list.

  • Page 146: Data Required

    Perform the diagnostics specified in the parameter list. The UnitOffL bit must be set, Self-Test otherwise been completed. Perform the standard self-test depending on the value of UnitOffL (see above). The Parameter List Length must be 0 otherwise report GOOD command.

  • Page 147: Standard Self-Test

    Standard Self-Test With a tape If Self-Test = 1 and UntOffl = 0, a test is performed that does not affect the inserted: contents of the tape. This test is a more extensive set of the tests carried out at power-on.

  • Page 148: Space 11H

    SPACE PACE and Count fields in the Command Descriptor Block. Both forward (towards EOM) and reverse (towards BOM) positioning are provided. Any unwritten data in the buffer is flushed to tape before the space is started. The logical media position is then modified according to the Code and Count fields.
  • Page 149 When spacing over blocks or filemarks this field indicates how many blocks or marks Count should be crossed. Spacing is forward (towards EOM) unless Count is negative (twos complement) when the spacing is towards BOM. When spacing to EOD the Count field is ignored. When not spacing to EOD, if Count is zero, the operation.
  • Page 150 Early warning end of medium information is not reported. If a space records or space filemarks command fails then the sense data information bytes will be set to the absolute value of the difference between the requested number of marks/records and the actual number of marks/ records spaced over and the Valid bit set.

  • Page 151: Test Unit Ready 00H

    TEST UNIT READY EST UNIT READY tape. This is done by the pre-execution Media Access check; it is not a request for a self-test. If the drive has a tape loaded, the command returns a status. Otherwise, READY Pre-Execution Checks: Illegal Field Unit Attention Command Descriptor Block:...

  • Page 152: Verify 13H

    VERIFY ERIFY The verification is media verification only. It reads data from the tape as it would for a read but then immediately discards it. No data is transferred between the host and drive. The command is identical to the execution checks are identical.
  • Page 153 The Byte compare option is not supported, so this bit must be 0. BCmp The Verification Length field specifies the length of the data to be verified in bytes. Fixed The Verification field specifies the length of the data to be verified in blocks. The size of each block (in bytes) is specified by the current block length specified in the Mode Parameter block descriptor.

  • Page 154: Write 0Ah

    WRITE Zero or more blocks of data are transferred from the host to tape starting at the current logical position. It is recommended that the Buffered Mode field of the is set to either 1 or 2 so that Immediate reporting is enabled; upon a write command the drive will report transferred to the data buffer (but not necessarily to tape).
  • Page 155 CDB Fields: Fixed The Transfer Length field specifies the length of the transfer in bytes. The Transfer Length field specifies the length of the transfer in blocks. The size of each block (in bytes) is determined by the current Block Length given in the Mode Select Parameter block descriptor.
  • Page 156 Block Mode Variable Fixed Variable Fixed Residue information is set in the sense data byte, with the Valid bit set and the information bytes set to the residue. 156 Commands Immediate or Non-Immediate Report (Buffered mode). Buffered Mode Number of unwritten bytes Number of unwritten blocks not 0 Total number of unwritten bytes and marks (including those...

  • Page 157: Write Attribute 8Dh

    WRITE ATTRIBUTE WRITE ATTRIBUTE values to MAM (Medium Auxiliary Memory). Application clients should issue READ ATTRIBUTE support the device server has for MAM. Pre-Execution Checks: Illegal Field If the combination of Volume Number and Partition Number is not valid, CHECK CONDITION additional sense of 2400h (invalid field in CDB).
  • Page 158 Command Descriptor Block: (MSB) 158 Commands If the MAM is not accessible even though there is a tape in the drive. is reported with a sense key of HECK CONDITION additional sense of 0410h (Media Auxiliary Memory not accessible). None of the attributes are changed. If the MAM has failed (for example from a bad checksum).
  • Page 159 CDB Fields: Volume The number of the volume within the MAM. The number of volumes of the MAM must be equal to that of the tape. In the case of Ultrium, the only has a single volume, so this field is be set to 0. Number Partition The number of the partition within the MAM.

  • Page 160: Write Buffer 3Bh

    Mode and Buffer ID fields of the command. Caution The firmware download functions are intended for use by manufacturing and by customers using upgrade utilities supplied by HP. Pre-Execution Checks: Illegal Field Command Descriptor Block:...
  • Page 161 CDB Fields: Mode This field can be set to one of the following values: 00000b The drive transfers a 4-byte header from the host (which should be set to zeros), followed by (allocation length identified by the Buffer ID, starting from offset zero in the buffer. The Buffer ID and Buffer Offset must both be zero.
  • Page 162 Buffer ID Specifies which buffer to read. Main buffer (RAM) Offset Boundary: 1 byte Processor addressable memory (RAM) Offset Boundary: 1 byte SCSI burst buffer (RAM) Offset Boundary: 4 bytes or FC burst buffer (RAM) Offset boundary: 512 bytes PCA EEPROM Offset Boundary: 1 byte Main buffer segment 0 (RAM) —...
  • Page 163 Main Processor Not all the Processor Memory space is accessible. The following table shows Memory: valid address segments: Start Address End Address 180000h 200000h 240000h 280000h FF80000h SCSI Burst Buffer: The buffer is 192 Kb, that is, addresses from 00000h through 30000h. PCA EEPROM: The write range is limited to 100h bytes, starting at 100h.

  • Page 164: Write Filemarks 10H

    WRITE FILEMARKS RITE FILEMARKS beginning at the current logical position on tape. If the Immed bit is set, data buffer. Otherwise, all buffered data and marks are written before status is reported. If zero filemarks are to be written, the Immed bit must be zero. The drive writes any buffered data and marks to tape before reporting.

  • Page 165: Glossary

    glossary Glossary algorithm A rigorous set of rules for a procedure. In the context of data compression, the rules are for transforming the way data is represented. ANSI American National Standards Institute, which sets standards for, amongst other things, SCSI and the safety of electrical devices. asynchronous data transfer phase Beginning Of Media.
  • Page 166 (16-bit) data transfer, two bytes are transferred at the same time instead of a single byte. HP Ultrium drives support asynchronous, synchronous and wide transfers. A procedure in which the original data is generated from compressed data. decompression Data Set Information Table. Part of the DSIT European Computer Manufacturers Association.
  • Page 167 Small Computer System Interface—a standard command specification and command set that enables computers and peripherals to communicate with each other. HP’s Ultrium drives adhere to the SCSI specifications (see Chapter 1, “Interface Implementation” in Volume 3, The SCSI Interface, of the HP Ultrium Technical Reference Manual) and support all features required by those standard.
  • Page 168 SCSI bus as wide devices using a suitable adapter. HP’s Generation 1 Ultrium drives are Ultra2, wide SCSI-3 compatible devices. They can be used with both LVD and SE host bus adapters.

  • Page 169: Index

    Index abort handling Aborted Command ACK signal 130, 136 additional sense codes addressing, fibre channel algorithms compression decompression 3, 165 ANSI append error asynchronous asynchronous data transfer ATN signal Bad LUN check bit pointer BLANK CHECK blank media, met during read blocks, spacing over 130, 165 detected...
  • Page 170 170 Index READ ATTRIBUTE READ BLOCK LIMITS READ BUFFER READ POSITION RECEIVE DIAGNOSTIC RESULTS RELEASE UNIT REPORT DENSITY SUPPORT REPORT LUNS REQUEST SENSE RESERVE UNIT REWIND SEND DIAGNOSTIC SPACE supported VERIFY WRITE WRITE ATTRIBUTE WRITE BUFFER WRITE FILEMARKS compatibility compression algorithm ratio control byte...
  • Page 171 command phase 65, 66 counters data phase deferred invalid message message parity read, unrecovered sequential positioning write write append write-behind deferred EVPD bit EW-EOM met during locate 56, 155 failed cartridge memory faults, predicting fibre channel addressing names Fibre Channel Logical Unit Control Mode page fibre channel operation Fibre Channel Port Control Mode page...
  • Page 172 172 Index Performance Data Log page Read Error Counters Log page Sequential Access Device Log page Supported Log Pages page Tape Capacity Log page Tape Usage Log page TapeAlert Log page Write Error Counters Log pages logs clearing Data Compression parameter pages Performance Data reading...
  • Page 173 Bad LUN Deferred Error Diagnostic Status Fixed Bit Flag Link Illegal Command Illegal Field Media Access Media Information Media Write Parameter List Reservation Unit Attention prevent media removal problems, predicting READ ATTRIBUTE command READ BLOCK LIMITS command READ BUFFER command READ command Read Error Counters Log page READ POSITION command...
  • Page 174 174 Index CHECK CONDITION GOOD RESERVATION CONFLICT Summary supported commands Supported Log Pages page synchronous synchronous data transfer synchronous data transfer request tape faulty incompatible loaded loading removal prevented unloading Tape Capacity log Tape Usage log TapeAlert log TapeAlert Log page third-party, reserving for Unit Attention check 132, 135...

Table of Contents