IBM DDRS-39130 - Ultrastar 9.1 GB Hard Drive Specifications
  1. Manuals
  2. Brands
  3. IBM Manuals
  4. Storage
  5. DDRS-39130 - Ultrastar 9.1 GB Hard Drive
  6. Specifications

IBM DDRS-39130 - Ultrastar 9.1 GB Hard Drive Specifications

3.5-inch hard disk drive ( 9130 / 4560 mb )
Hide thumbs Also See for DDRS-39130 - Ultrastar 9.1 GB Hard Drive:
Table of Contents

Advertisement

Quick Links

S00K-0097-03
OEM HARD DISK DRIVE SPECIFICATIONS for
DDRS-39130 / DDRS-34560
3.5-Inch Hard Disk Drive ( 9130 / 4560 MB )
Revision (2.0)

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the DDRS-39130 - Ultrastar 9.1 GB Hard Drive and is the answer not in the manual?

Questions and answers

Related Manuals for IBM DDRS-39130 - Ultrastar 9.1 GB Hard Drive

Summary of Contents for IBM DDRS-39130 - Ultrastar 9.1 GB Hard Drive

  • Page 1 S00K-0097-03 OEM HARD DISK DRIVE SPECIFICATIONS for DDRS-39130 / DDRS-34560 3.5-Inch Hard Disk Drive ( 9130 / 4560 MB ) Revision (2.0)
  • Page 3 S00K-0097-03 OEM HARD DISK DRIVE SPECIFICATIONS for DDRS-39130 / DDRS-34560 3.5-Inch Hard Disk Drive ( 9130 / 4560 MB ) Revision (2.0)
  • Page 4 It is possible that this publication may contain reference to, or information about, IBM products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that IBM intends to announce such IBM products, programming, or services in your country.

  • Page 5: Table Of Contents

    ..........Copyright IBM Corp. 1997...
  • Page 6 6.3.3 80-Pin Model ..........6.4 Environment .
  • Page 7 7.6.3 Inquiry Data Format - EVPD = 1 - Page Code = 80h ..... . 7.7 LOG SELECT (4C) ..........7.8 LOG SENSE (4D) .
  • Page 8 7.32 SYNCHRONIZE CACHE (35) ........7.33 TEST UNIT READY (00) .
  • Page 9 10.1.6 Command Processing During Start-up and Format Operations ....10.1.7 Internal Error Condition ........10.1.8 Deferred error .
  • Page 10 12.2.4 Sense Key (Bit 3 - 0 of byte 2) ........12.2.5 Information Bytes (Byte 3 thru 6) .

  • Page 11: General

    1.0 General 1.1 Introduction | This document describes the specifications of the following IBM 3.5 inch SCSI drives. DDRS-39130 SCSI-3 FAST-20 SE 50-pin (with SCSI terminator) SCSI-3 FAST-20 SE 68-pin WIDE (with SCSI terminator) SCSI-3 FAST-20 SE 80-pin SCA-2 FAST-40...

  • Page 12: Glossary

    32 x 1,024 bytes 64KB 64 x 1,024 bytes Mb/sq.in 1,000,000 bits per square inch Machine Level Control Predictive Failure Analysis (Trademark of IBM Corp.) S.M.A.R.T. Self-Monitoring Analysis and Reporting Technology Automatic Drive Maintenance SCAM SCSI Configured AutoMatically Single Ended SCSI Low Voltage Differential SCSI 1.4 General Caution...

  • Page 13: Outline Of The Drive

    7200rpm spindle rotation. Closed loop actuator servo Dedicated head landing zone Automatic actuator lock Informational Exceptions Control Page of SCSI-3 support as PFA or S.M.A.R.T. function Note: PFA which means Predictive Failure Analysis is Trademark of IBM Corporation. Copyright IBM Corp. 1997...
  • Page 14 O E M Spec. of DDRS-3xxxx...

  • Page 15: Part 1. Functional Specification

    Part 1. Functional Specification Copyright IBM Corp. 1997...
  • Page 16 O E M Spec. of DDRS-3xxxx...

  • Page 17: Fixed Disk Subsystem Description

    The actuator assembly is balanced to allow vertical or horizontal mounting without adjustment. When the drive is powered off, the actuator automatically moves the head to a dedicated landing zone outside of the data area, where the actuator is locked. Copyright IBM Corp. 1997...
  • Page 18 O E M Spec. of DDRS-3xxxx...

  • Page 19: Drive Characteristics

    6 x 64 Kbyte 3 x 128 Kbyte Rotational speed [ R P M ] 7200 Recording density [ Kbpi] 134 (Ave) / 156 (Max) Track density [ TPI] 10000 Areal density [ Mb/sq.in.] 1560 (Max) Data zone Copyright IBM Corp. 1997...

  • Page 20: Cylinder Allocation

    3.3 Cylinder Allocation Phys. Cyl. Sectors/Trk System Area Data Zone 0 0-695 Data Zone 1 696-1332 Data Zone 2 1333-2181 Data Zone 3 2182-3283 Data Zone 4 3284-4234 Data Zone 5 4235-6602 Data Zone 6 6603-8105 Data Zone 7 8106-8419 System Area Mode page 03 (Format Device Parameters) and 0C (Notch Parameters) provide methods to determin medium format and zone parameters.

  • Page 21: Command Overhead

    3.4.1 Command overhead Command overhead is defined as the time required: from last byte of command phase to the first byte of data phase excluding Physical seek time Latency time Initiator delay with reconnections Read Command Case with 6x64KB buffer (Drive is in quiescence state) Time Cache Not Hit <0.40msec...

  • Page 22: Full Stroke Seek

    3.4.2.2 Full Stroke Seek Figure 5. Full Stroke Seek Time Function Typical Max. Read [ msec] 15.0 16.0 Write [ msec] 15.8 16.8 Full stroke seek is measured as the average of 1000 full stroke seeks with a random head switch from both directions (inward and outward).

  • Page 23: Drive Ready Time

    3.4.3 Drive Ready Time Figure 9. Drive Ready Time Model Typical Max. DDRS-39130 15.5 [ sec] 19.9 [ sec] DDRS-34560 10.5 [ sec] 19.9 [ sec] Ready The condition in which the drive is able to perform a media access command (eg. read, write) immediately.

  • Page 24: Buffering Operation (Lookahead/Write Cache)

    Sustained disk-buffer transfer rate (Mbyte/sec) is defined by considering head/cylinder change time. This gives a local average data transfer rate. It is derived by: (Sustained Transfer Rate) = A/ ( B + C + D ) A = (Number of data sectors per cylinder) * 512 B = ((# of Surface per cylinder) - 1) * (Head switch time) C = (Cylinder change time) D = (# of Surface) * (One revolution time)

  • Page 25: Throughput

    3.4.7 Throughput 3.4.7.1 Simple Sequential Access Figure 12. Simple Sequential Access Performance Operation Typical Sequential Read/Write Zone 0 1300 [ msec] Zone 0 2086 [ msec] Zone 7 1348 [ msec] Zone 7 2172 [ msec] The above table gives the time required to read/write for a total of 8000x consecutive blocks (16,777,216 bytes) accessed by 128 read/write commands.
  • Page 26 O E M Spec. of DDRS-3xxxx...

  • Page 27: Data Integrity

    “Write fault” is detected. 4.2 Error Recovery Errors occurring with the drive are handled by the error recovery procedure. Errors that are uncorrectable after application of the error recovery procedures are reported to the host system as non-recoverable errors. Copyright IBM Corp. 1997...
  • Page 28 O E M Spec. of DDRS-3xxxx...

  • Page 29: Physical Format

    Total 1750 spare sectors are available at shipment. A cylinder for spare sectors is prepared in every 256 cylinders. Note: There is possibility to have G-List entry during the first 4 or 6 surface scan. It is mainly caused by handling problem, and G-List entry is normal maintenance work of Hard Disk Drive. Copyright IBM Corp. 1997...
  • Page 30 O E M Spec. of DDRS-3xxxx...

  • Page 31: Specification

    Connector of 80-pin models comply with SFF-8046 Revision 2.1. Power pin assignment of 50-pin and 68-pin models is as shown below. Voltage + 12 V G N D G N D + 5 V Figure 14. Power Connector Pin Assignments Copyright IBM Corp. 1997...
  • Page 32 6.1.1.2 SCSI Signal Connector (50-pin) The SCSI signal connector complies with ANSI SCSI-2. Figure 15. Table of Signals SIGNAL SIGNAL Ground -DB(0) Ground -DB(1) Ground -DB(2) Ground -DB(3) Ground -DB(4) Ground -DB(5) Ground -DB(6) Ground -DB(7) Ground -DB(P) Ground Ground Ground Ground Ground...
  • Page 33 6.1.1.3 SCSI Signal Connector (68-pin SE) The pin assignments of interface signals conforms to ANSI SCSI-3 X3T10/855D as follows. Figure 16. Table of Signals Connector Signal Name Connector Signal Name Contact Contact Number Number Ground -DB(12) Ground -DB(13) Ground -DB(14) Ground -DB(15) Ground...
  • Page 34 6.1.1.4 SCSI Signal Connector (68-pin LVD) | The pin assignments of interface signals conforms to ANSI SPI-2 T10 Project 1142D Revision 19 as follows. Figure 17. Table of Signals Connector Signal Name Connector Signal Name Contact Contact Number Number + D B ( 1 2 ) -DB(12) + D B ( 1 3 ) -DB(13)
  • Page 35 6.1.1.5 SCSI Signal Connector (80-pin SE) The pin assignments of interface signals conform to SFF-8046 as follows. Figure 18. Table of Signals Connector Signal Name Connector Signal Name Contact Contact Number Number 12 Volt Charge 12V Ground 12 Volt 12V Ground 12 Volt 12V Ground 12 Volt...
  • Page 36 6.1.1.6 SCSI Signal Connector (80-pin LVD) | The 80-pin SCA-2 model uses an AMP connector which is compatible with SFF-8046 Revision 2.1. Figure 19. Table of Signals Connector Signal Name Connector Signal Name Contact Contact Number Number 12 Volt Charge 12V Ground 12 Volt 12V Ground...

  • Page 37: Scsi Cable

    6.1.2 SCSI Cable 6.1.2.1 SE model The maximum cumulative cable length when using single-ended transceiver should be 3 meters. Implementa- tions that limit the transfer rate to a maximum of 5 Mbyte transfers per second may extend the cumulative cable length to 6 meters. (ANSI SCSI-3 X3T10/855D Revision 15a). The maximum cumulative signal path between terminators shall be 3.0 meters when using up to 4 maximum capacitance (25pF) devices.

  • Page 38: Scsi Bus Electrical Characteristics

    6.1.5 SCSI Bus Electrical Characteristics 6.1.5.1 SE model The interface logic signals has the following electrical specifications: I n p u t s I n p u t H i g h V o l t a g e = 2 . 0 V m i n . I n p u t L o w V o l t a g e = 0 .

  • Page 39: Auxiliary Connector On 68-Pin Model

    6.1.6 Auxiliary Connector on 68-pin Model The 68-pin models contain Auxiliary Connector between power connector and 68-pin SCSI connector in addition to Option Jumper Block. The setting at Option Jumper Block and the Auxiliary Connector work as logical OR. The drive conforms SFF-8009 Rev3.0. Pin #1,3,5,7 specify SCSI-ID as -DAS0,1,2,3.

  • Page 40: Option Jumper Block

    P i n # : D i s k E n c l o s u r e Figure 21. Jumper Pins Note: The pin alocation is not compatible with previous IBM HDDs such as DPES-xxxxx, DALS-xxxxx. O E M Spec. of DDRS-3xxxx...
  • Page 41 N o t e : ( x ) s h o w s P o s i t i o n N u m b e r G R O U N D ( 1 ) D A S 3 ( 2 ) D A S 2 ( 3 )

  • Page 42: Jumper Signal Description

    6.2.1 Jumper Signal Description Throughout this paragraph ON means a shunt jumper is installed and O F F means that no shunt jumper is installed. 6.2.1.1 Device address select lines. (-DAS0, -DAS1, -DAS2, -DAS3) These four lines defines DDRS-3xxxx device ID on the SCSI BUS. -DAS0 is the least significant bit and -DAS3 is the most significant bit.
  • Page 43 6.2.1.6 Disable Unit Attention. (Position 7) Grounding this pin (jumper on) enables control of UAI (Unit Attention Inhibit) bit in Mode Page 0. 6.2.1.7 Enable TI-SDTR (50-pin) / Enable TI-SDTR/WDTR (68,80-pin) Grounding this pin (jumper on) enables the following. Target Initiated Wide Data Transfer Request Negotiation (68,80-pin) Target Initiated Synchronous Data Transfer Request Negotiation (50,68,80-pin) 6.2.1.8 Auto Start Delay &...
  • Page 44 6.2.1.9 Disable SCSI Parity Check (Position 11) Grounding this pin will disable SCSI Parity checking. 6.2.1.10 LED pins (Position 12) The LED pins are used to drive an external Light Emitting Diode. Up to 30 mA of sink current capability is provided.

  • Page 45: Shipping Default

    6.2.2 Shipping Default | No jumper is set as shipping default on 80-pin models. | SCSI ID is set to #6 as shipping default on 50/68-pin models. | SCSI terminator is enabled as shipping default on SE 50/68-pin models. | Auto Spin up is enabled on all models. S h i p p i n g D e f a u l t S e t t i n g o f S E 5 0 / 6 8 p i n .

  • Page 46: Led Circuit

    6.3 LED Circuit Jumper pin #1 and #2 are used to drive an external LED. Instead of the the jumper pins, the following pins can be used to drive LED. 68-Pin Model : Auxiliary Connector Pin #8 and #11. 80-Pin Model : SCA-2 Connector Pin #77 as shown in 6.3.3, “80-Pin Model” on page 38. The schematics of LED circuit on each model are as follows.

  • Page 47: 68-Pin Model

    6.3.2 68-Pin Model D D R S 3 9 1 3 0 / D D R S 3 4 5 6 0 6 8 P i n M o d e l E x a m p l e o f U s a g e a t S y s t e m S i d e A u x i l i a r y C o n n e c t o r P i n # 1 1...

  • Page 48: 80-Pin Model

    6.3.3 80-Pin Model D D R S 3 9 1 3 0 / D D R S 3 4 5 6 0 8 0 P i n ( S C A 2 ) M o d e l : E x a m p l e o f U s a g e a t S y s t e m S i d e + 5 V + 5 V...

  • Page 49: Environment

    6.4 Environment Figure 31. Environmental Condition Operating Conditions Temperature 5 to 55[ ˚ C] (See note) Relative Humidity 8 to 90 [ % R H ] non-condensing Maximum Wet Bulb Temperature 29.4[ ˚ C] non-condensing Maximum Temperature Gradient 15[ ˚ C / Hour] Altitude 300 to 3048 [ m] Non-Operating Conditions...

  • Page 50: Cooling Requirements

    6.5 Cooling Requirements The system has to provide sufficient ventilation to maintain a surface temperature below 60˚ C at the center of the top cover of the drive. The system has to provide sufficient ventilation to keep the limits of component temperature as shown below.

  • Page 51: Dc Power Requirements

    6.6 DC Power Requirements Connection to the product should be made in isolated secondary circuits (SELV). The following voltage specification is applied at the power connector of the drive. No special power on/off sequencing is required. Figure 34. Input Voltage During run and spin up Absolute max spike voltage Supply rise time...

  • Page 52: Start Up Current

    Figure 37. Power Supply Generated Ripple at Drive Power Connector Maximum Notes + 5 V DC 100 [ mV pp] 0-10 [ MHz] + 1 2 V DC 150 [ mV pp] 0-10 [ MHz] During drive start up and seeking, 12 volt ripple is generated by the drive (referred to as dynamic loading). If several files have their power daisy chained together then the power supply ripple plus other drive's dynamic loading must remain within the regulation tolerance of ±...

  • Page 53: Reliability

    6.7 Reliability 6.7.1 Contact Start Stop (CSS) The drive is designed to withstand a minimum of 40,000 contact start/stop cycles at 40˚ C with 13-25% rela- tive humidity. The drive is designed to withstand a minimum of 10,000 contact start/stop cycles at operating environment conditions specified in 6.4, “Environment”...

  • Page 54: Automatic Drive Maintenance (Adm)

    6.7.6 Automatic Drive Maintenance (ADM) A D M function can be enabled by EADM bit in Mode Page 0, and the shipping default is disable. A D M function is equipped to enhance the reliability in continuous usage. A D M function is to perform a CSS automatically after detection of idling time for 1 minute at intervals of 1 week.

  • Page 55: Mechanical Specifications

    6.8 Mechanical Specifications 6.8.1 Outline 6.8.1.1 50-pin Model Figure 39. Outline of 50-pin Model Specification...
  • Page 56 6.8.1.2 68-pin Model Figure 40. Outline of 68-pin Model O E M Spec. of DDRS-3xxxx...
  • Page 57 6.8.1.3 80-pin Model Figure 41. Outline of 80-pin Model Specification...

  • Page 58: Mechanical Dimensions

    6.8.2 Mechanical Dimensions The following chart describes the dimensions and the weight. Figure 42. Physical Dimension Height [ mm] 25.4 ± 0.4 Width [ mm] 101.6 ± 0.4 Length [ mm] 146.0 ± 0.6 Weight [ gram] 630 Max. Figure 43. Mechanical Dimension O E M Spec.

  • Page 59: Interface Connector

    6.8.3 Interface Connector 6.8.3.1 50-pin Model Figure 44. Interface Connector (50-pin Model) Specification...
  • Page 60 6.8.3.2 68-pin Model Figure 45. Interface Connector (68-pin Model) O E M Spec. of DDRS-3xxxx...
  • Page 61 6.8.3.3 80-pin Model Figure 46. Interface Connector (80-pin Model) Specification...

  • Page 62: Mounting Positions And Tappings

    6.8.4 Mounting Positions and Tappings Figure 47. Mounting Positions and Tappings O E M Spec. of DDRS-3xxxx...

  • Page 63: Shipping Zone And Lock

    6.8.4.1 Drive Mounting The drive will operate in all axes (6 directions). Performance and error rate will stay within specification limits if the drive is operated in the other orientations from which it was formatted. The recommended mounting screw torque is 0.6 - 1.0 [ N m ] (6 - 10 [ Kgf.cm]). The recommended mounting screw depth is 4 [ mm] Max for bottom and 4.5 [ mm] Max for horizontal mounting.

  • Page 64: Vibration And Shock

    6.9 Vibration and Shock All vibration and shock measurements in this section are made with the drive that has no mounting attach- ments for the systems. The input power for the measurements is applied to the normal drive mounting points. 6.9.1 Operating Vibration 6.9.1.1 Random Vibration The drive is designed to operate without unrecoverable errors while being subjected to the following...

  • Page 65: Non-Operating Vibrations

    6.9.2 Non-Operating Vibrations The drive does not sustain permanent damage or loss of recorded data after being subjected to the environ- ment described below. 6.9.2.1 Random Vibration The test consists of a random vibration applied for each of three mutually perpendicular axes with the time duration of 10 minutes per axis.

  • Page 66: Acoustics

    6.10 Acoustics The following shows the acoustic levels. 6.10.1 Sound Power Levels The upper limit criteria of the A-weighted sound power levels are given in Bel relative to one pico watt and are shown in the following table. The measurment method is in accodance with ISO7779. Figure 51.

  • Page 67: Sound Pressure (Reference)

    6.10.2 Sound Pressure (Reference) 6.10.2.1 Unit Sound Pressure Level Measurment The hard disk drives are measured in a semi-anechoic chamber, with background noise = < 25 dBA. Sur- faces to be measured are top cover side and card side. Microphone is set one meter above the drive surface. Random operation mode is simulated with 40% seek and 60% idle in time.

  • Page 68: Identification Labels

    The drive, when installed in a suitable enclosure and exercised with a random accessing routine at maximum data rate, meets the worldwide EMC requirements listed below. IBM will provide technical support to meet the requirements to comply with the EMC specifications. United States Federal Communications Commission (FCC) Rules and Regulations (Class B), Part 15.

  • Page 69: Safety

    6.13 Safety The following shows the safety standards for different countries. 6.13.1 Underwriters Lab (UL) Approval DDRS-3xxxx comply with UL 1950. 6.13.2 Canadian Standards Authority (CSA) Approval DDRS-3xxxx comply with CSA C22.2 No.0-M91, and CSA C22.2 No.950-M1993. 6.13.3 IEC Compliance DDRS-3xxxx comply with IEC 950.
  • Page 70 O E M Spec. of DDRS-3xxxx...

  • Page 71: Part 2. Scsi Interface Specification

    Part 2. SCSI Interface Specification Copyright IBM Corp. 1997...
  • Page 72 O E M Spec. of DDRS-3xxxx...

  • Page 73: Scsi Command Set

    RESERVE (10) REZERO UNIT SEEK SEEK EXTENDED SEND DIAGNOSTICS START/STOP UNIT SYNCHRONIZE CACHE TEST UNIT READY VERIFY WRITE WRITE AND VERIFY WRITE BUFFER WRITE EXTENDED WRITE LONG WRITE SAME Figure 53. SCSI Commands Supported. (In Alphabetical order) Copyright IBM Corp. 1997...

  • Page 74: Flag And Link Bits

    SCSI-1 SCSI-2 CODE COMMAND TEST UNIT READY REZERO UNIT REQUEST SENSE FORMAT UNIT REASSIGN BLOCKS READ WRITE SEEK INQUIRY MODE SELECT (6) RESERVE (6) RELEASE (6) MODE SENSE (6) START/STOP UNIT RECEIVE DIAGNOSTICS SEND DIAGNOSTICS READ CAPACITY READ EXTENDED WRITE EXTENDED SEEK EXTENDED WRITE AND VERIFY VERIFY...

  • Page 75: Abbreviations

    LINK This bit is set to one to indicate that the initiator desires an automatic link to the next command upon successful completion of the current command. Upon successful completion of the command, the file will return INTERMEDIATE GOOD status and then send one of the two mes- sages defined under Flag above.

  • Page 76: F O R M A T Unit (04)

    7.4 FORMAT UNIT (04) Byte Command Code = 04h FmtData CmpList Defect List Format VU = 0 (MSB) Interleave Factor (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 55. F O R M A T UNIT (04) The F O R M A T command performs a physical formatting of the file media. This includes handling of defec- tive sectors, and the overwriting of all data areas with a constant data pattern.
  • Page 77 Byte Reserved = 0 DPRY DCRT STPF IP = 0 DSP = 0 Immed (MSB) Defect List Length (LSB) Figure 56. Format of Defect List Header. Format of the defect list header sent during the data out phase when FmtData set to one. The Target has a limited implementation of the Format Option bits located in Bits 2 through 7 of Byte 1 of the Defect List Header (See Figure 56).

  • Page 78: Defect Descriptor

    Immed (Immediate) bit set to zero requests that status be returned at the end of the format operation. An immediate bit set to one requests that status be returned immediately. Good Status is returned fol- lowing the CDB validation and transfer of data in the Data Out phase. If the immediate format opera- tion terminates in error, Deferred Error Sense data is generated.
  • Page 79 Byte (MSB) Cylinder Number of Defect (LSB) Head Number of Defect (MSB) Defect Bytes from Index (LSB) 8n - Defect Descriptor n 8n + 7 Figure 58. Defect Descriptor - Bytes From Index Format. Format of the defect list sent during the data out phase when FmtData set to one.

  • Page 80: Inquiry (12)

    7.5 INQUIRY (12) Byte Command Code = 12h Reserved = 0 EVPD Page Code Reserved = 0 Allocation Length VU = 0 Reserved = 0 FLAG LINK Figure 60. INQUIRY (12) The INQUIRY command requests the parameters of the target to be sent to the initiator. An EVPD bit of one specifies that the file shall return the vital product data page identified by the Page Code field in the CDB.

  • Page 81: Inquiry Data

    7.6 Inquiry data Fields with a value shown inside quotes (e.g. Value = 'xyz') are character fields. A value not in quotes is a numeric value. Character fields are alpha-numeric and represented in either ASCII or EBCDIC as stated. SCSI C O M M A N D SET...

  • Page 82: Inquiry Data Format - Evpd

    RSVD = 0 RDF = 2 Additional Length = 159 (9Fh) Reserved = 0 REL_A Wb_32 Wb_16 Sync Link TTD CmdQu SftRe 8 15 Vendor ID = 'IBM (ASCII) 16 31 Product ID (ASCII) 32 35 Product Revision Level (ASCII)
  • Page 83 SftRe is set to zero to indicate that the target supports Hard Reset only. Vendor ID is 'IBM' padded with ASCII blanks. Product ID is specified in ASCII character. Product ID...

  • Page 84: Inquiry Data Format - Evpd = 1 - Page Code = 00

    7.6.2 Inquiry Data Format - EVPD = 1 - Page Code = 00 BYTE Qualifier = 0 Peripheral Dev Type = 0 Page Code = 00h Reserved = 0 Page Length = 01h Supported Page Code = 80h Figure 63. INQUIRY DATA - EVPD = 1 (Page Code = 00) Qualifier is set to zero to indicate that the L U N specified in the Command Block is currently supported.

  • Page 85: Inquiry Data Format - Evpd = 1 - Page Code = 80H

    7.6.3 Inquiry Data Format - EVPD = 1 - Page Code = 80h BYTE Qualifier = 0 Peripheral Dev Type = 0 Page Code = 80h Reserved = 0 Page Length = 16 (10h) 4 19 Serial Number (ASCII) Figure 64. INQUIRY DATA - EVPD = 1 (Page Code = 80h) Qualifier is set to zero to indicate that the L U N specified in the Command Block is currently supported.

  • Page 86: Log Select (4C)

    7.7 LOG SELECT (4C) Byte Command Code = 4Ch Reserved = 0 Reserved = 0 Reserved = 0 (MSB) Parameter List Length = 0 (LSB) Reserved = 0 FLAG LINK Figure 65. L O G SELECT (4C) The LOG SELECT command provides a means for the initiator to clear statistical information maintained by the drive and reported via the Log Sense command.

  • Page 87: Log Sense (4D)

    7.8 LOG SENSE (4D) Byte Command Code = 4Dh Reserved = 0 PPC = 0 Page Code Reserved = 0 (MSB) Parameter Pointer = 0 (LSB) (MSB) Allocation Length (LSB) Reserved = 0 FLAG LINK Figure 66. L O G SENSE (4D) The LOG SENSE command allows the initiator to retrieve the statistical data about the drive.

  • Page 88: Log

    7.8.1 Log Page parameters Each log page begins with a four-byte page header followed by zero or more variable-length log parameters. Page Header Page Code field identifies which log page is being transferred. The Page Length field specifies the length in bytes of the following log parameters. Log Parameters Each log parameter begins with a four-bytes parameter header followed by one or more bytes of parameter value data.

  • Page 89: Log Sense

    7.8.2 Log Sense Page 0 Byte Reserved Page code = 0 Reserved Page Length = 0006h (Number of Pages Supported) First supported page 0h Second supported page 2h Third supported page 3h Fourth supported page 5h Fifth supported page 6h Sixth supported page 3Ah Page 0 indicates the supported log sense pages.

  • Page 90: Log Sense

    7.8.3 Log Sense Page 2 This page contains counters for write errors Byte Reserved Page code = 02h Reserved 2 - 3 PageLength = 38h 4 - 5 Parameter Code = 00h T M C = 0 LBIN Parameter Length = 04h 8 - 11 Errors recovered without delay = 0 12 - 13...
  • Page 91 Byte 44 - 45 Parameter Code = 05h T M C = 0 LBIN Parameter Length = 04h 48 - 51 Total bytes written 52 - 53 Parameter Code = 06h T M C = 0 LBIN Parameter Length = 04h 56 - 59 Count of LBA's with hard error SCSI C O M M A N D SET...

  • Page 92: Log Sense

    7.8.4 Log Sense Page 3 This page contains counters for read errors Byte Reserved Page code = 03h Reserved 2 - 3 PageLength = 38h 4 - 5 Parameter Code = 00h T M C = 0 LBIN Parameter Length = 04h 8 - 11 Errors recovered without delay = 0 12 - 13...
  • Page 93 Byte 44 - 45 Parameter Code = 05h T M C = 0 LBIN Parameter Length = 04h 48 - 51 Total bytes read 52 - 53 Parameter Code = 06h T M C = 0 LBIN Parameter Length = 04h 56 - 59 Count of LBA's with hard error The drive will attempt to read data after a seek before the head has fully settled on track.

  • Page 94: Log Sense

    7.8.5 Log Sense Page 5 This page contains counters for verify errors Byte Reserved Page code = 05h Reserved 2 - 3 PageLength = 38h 4 - 5 Parameter Code = 00h T M C = 0 LBIN Parameter Length = 04h 8 - 11 Errors recovered without delay = 0 12 - 13...
  • Page 95 Byte 44 - 45 Parameter Code = 05h T M C = 0 LBIN Parameter Length = 04h 48 - 51 Total bytes written 52 - 53 Parameter Code = 06h T M C = 0 LBIN Parameter Length = 04h 56 - 59 Count of LBA's with hard error The drive will attempt to read data after a seek before the head has fully settled on track.

  • Page 96: Log Sense

    7.8.6 Log Sense Page 6 This page contains counters for non-medium errors. This includes seek errors and other hardware type fail- ures. Byte Reserved Page code = 06h Reserved 2 - 3 PageLength = 08h 4 - 5 Parameter Code = 00h T M C = 0 LBIN Parameter Length = 04h...

  • Page 97: Log Sense Page 3A

    7.8.7 Log Sense Page 3A Log Sense Page 3A is reserved and this page of the specification is intentionally left blank. SCSI C O M M A N D SET...

  • Page 98: Mode Sense (1A)

    7.9 MODE SENSE (1A) Byte Command Code = 1Ah Reserved = 0 Page Code Reserved = 0 Allocation Length VU = 0 Reserved = 0 FLAG LINK Figure 67. M O D E SENSE (1A) The M O D E SENSE (1A) command provides a means for the file to report various device parameters to the initiator.
  • Page 99 Report saved value. The file returns the saved value for the page code specified. Saved values are one of following : the values saved as a result of M O D E SELECT command identical to the default values zero when the parameters are not supported The Page Length byte value of each page returned by the file indicates up to which fields are sup- ported on that page.

  • Page 100: Mode Parameter List

    7.9.2 Mode Parameter List The mode parameter list contain a header, followed by zero or more block descriptors, followed by zero or more variable-length pages. 7.9.2.1 HEADER The six-byte command descriptor block header is defined below. 7.9.2.1.1 Mode parameter header (6) BYTE 0 Mode Data Length BYTE 1...

  • Page 101: Block Descriptor

    When used with the M O D E SENSE command, a Write Protect (WP) bit of zero indicates that the medium is write enabled. Block Descriptor Length specifies the length in bytes of the block descriptors. When used with the M O D E SELECT command, zero or eight are supported by the file. When used with the M O D E SENSE command, the file returns eight to indicate that only a single block descriptor is available.
  • Page 102 BYTE 0 PS RSVD=0 Page Code BYTE 1 Page Length BYTE Mode Parameters Figure 72. M O D E Parameter Page Format Each mode page contains a page code, a page length, and a set of mode parameters. When using the M O D E SENSE command, a Parameter Savable (PS) bit of one indicates that the mode page can be saved by the file in the reserved area of the file.

  • Page 103: Vendor Unique Parameters)

    7.9.3 Page 0 (Vendor Unique Parameters) Default BYTE 0 RSVD=0 Page Code = 00h BYTE 1 Page Length = 0Eh BYTE 2 QPE Ignore UAI SCAM level ARHES BYTE 3 RSVD=0 RSVD=0 CMDAC Ignore RSVD = 0 BYTE 4 RSVD = 0 BYTE 5 RSVD=0 Ignore Ignore Ignore Ignore RSVD=0 CAEN Ignore BYTE 6 IGRA AVERP EADM...
  • Page 104 SCAM level, SCAM level control bits, specify the SCAM function level to be supported. (shipping default = 2) Bit 2 Bit 1 SCAM function Disable SCAM level 1 SCAM level 2 ARHES (Automatic Reassign Hard Error Sites) bit of one indicates the drive will automatically reassign an hard read error.
  • Page 105 When there is a command active or in the queue, the LED is high. Command Aging Limit This value is used to control the maximum time a command should wait in the command queue when the CAEN bit is set. Each unit of this timer is 50ms. QPE Read Threshold specifies the error reporting threshold for read operations when the QPE bit is set to one.

  • Page 106: Read/Write Error Recovery Parameters)

    7.9.4 Page 1 (Read/Write Error Recovery Parameters) Default BYTE 0 RSVD=0 Page Code = 01h BYTE 1 Page Length = 0Ah BYTE 2 AWRE ARRE EER=0 BYTE 3 Read Retry Count BYTE 4 Correction Span BYTE 5 Head Offset Count (Not used) BYTE 6 Data Strobe Offset Count (Not used) BYTE 7...
  • Page 107 occurred, then normal D R P could result in considerable recovery action, including proceeding through all levels of DRP. R C set to 0 indicates normal interpretation of PER, DTE, DCR, and TB values. The R C bit setting is used by the Target when reporting errors associated with the transfer of the Initiator's data for the fol- lowing commands: Read(6)
  • Page 108 The following summarizes valid modes of operation. If an illegal mode is set the mode select command will complete successfully but the action of the file when an error occurs is undefined. PER DTE DCR TB DESCRIPTION Retries and Error Correction are attempted. Recovered and/or corrected data (if any) is transferred with no CHECK CONDITION status at the end of the transfer.
  • Page 109 The highest level error is reported at the end of transfer. Retries and error cor- rection are attempted. Recovered and/or corrected data (if any) is transferred with CHECK CONDITION status and RECOVERED E R R O R Sense Key set at the end of the transfer.
  • Page 110 The highest level error is reported at the end of transfer. Retries and error cor- rection are attempted. Recovered and/or corrected data (if any) is transferred with CHECK CONDITION status and RECOVERED E R R O R Sense Key set at the end of the transfer.

  • Page 111: Disconnect/Reconnect Parameters)

    7.9.5 Page 2 (Disconnect/Reconnect Parameters) Default BYTE 0 RSVD=0 Page Code = 02h BYTE 1 Page Length = 0Eh BYTE 2 Read Buffer Full Ratio BYTE 3 Write Buffer Empty Ratio BYTE Reserved = 0 Figure 76. Page 2 The disconnect / reconnect page provides the initiator the means to tune the performance of the SCSI bus. An initiator may use the IDENTIFY message to grant the file the general privilege of disconnecting.

  • Page 112: Format Device Parameters)

    7.9.6 Page 3 (Format Device Parameters) Default 4.5G 9.1G BYTE 0 PS = 0 RSVD=0 Page Code = 03h BYTE 1 Page Length = 16h BYTE 2 (MSB) 14h 28h Tracks per Zone BYTE 3 (LSB) 79h F3h BYTE 4 (MSB) Alternate Sectors per Zone = 0 BYTE 5 (LSB)
  • Page 113 A value of 0 in the following parameters indicate that those are Target specific. Alternate Sectors per Zone Alternate Tracks per Zone Alternate Tracks per Logical Unit Sectors per Track specifies the number of physical sectors within each track. This field is a function of the active notch.

  • Page 114: Rigid Disk Drive Geometry Parameters)

    7.9.7 Page 4 (Rigid Disk Drive Geometry Parameters) Default 4.5G 9.1G BYTE 0 RSVD = 0 Page Code = 04h BYTE 1 Page Length = 16h BYTE 2 (MSB) Number of Cylinders BYTE 4 (LSB) BYTE 5 Number of Heads 05h 0Ah BYTE 6 (MSB) Starting Cylinder-Write Precompensation = 0...

  • Page 115: Verify Error Recovery Parameters)

    7.9.8 Page 7 (Verify Error Recovery Parameters) Default BYTE 0 RSVD=0 Page Code = 07h BYTE 1 Page Length = 0Ah BYTE 2 Reserved = 0 EER=0 PER DTE=0 DCR BYTE 3 Verify Retry Count BYTE 4 Correction Span = 00h BYTE 5 Reserved = 0 BYTE 6...
  • Page 116 Soft errors are reported. ECC is applied to recover the data. Soft errors are not reported. ECC is not used to recover the data. Soft errors are reported. ECC is not used to recover the data. Verify Retry Count sets a limit on the amount of verify recovery procedure(VRP) passes the Target attempts when recovering verify errors.

  • Page 117: Caching Parameters)

    7.9.9 Page 8 (Caching Parameters) Default BYTE 0 RSVD=0 Page Code = 08h BYTE 1 Page Length = 0Ch BYTE 2 RESERVED = 0 BYTE 3 Read Retention Priority=0 Write Retention Priority=0 BYTE Disable Pre fetch Transfer Length BYTE Minimum Pre fetch BYTE Maximum Pre fetch BYTE...
  • Page 118 Minimum Pre-fetch specifies the minimum number of LBA's that the drive should read ahead after each read command. A value of zero indicates that read ahead should be terminated immediately a new command arrives, except in the case when the new command is on the current head and track. Maximum Pre-fetch specifies the maximum number of LBA's to read ahead after a read command.

  • Page 119: Page A (Control Mode

    7.9.10 Page A (Control Mode Page Parameters) Default BYTE 0 RSVD=0 Page Code = 0Ah BYTE 1 Page Length = 6 BYTE 2 RESERVED = 0 RLEC BYTE 3 Queue Algorithm Modifier RESERVED = 0 QErr DQue BYTE 4 EECA RESERVED = 0 RAENP UAAENP EAENP BYTE 5...

  • Page 120: C (Notch Parameters)

    7.9.11 Page 0C (Notch Parameters) Default BYTE 0 RSVD=0 Page Code = 0Ch BYTE 1 Page Length = 16h BYTE 2 ND = 1 LPN = 0 RSVD = 0 BYTE 3 Reserved = 0 BYTE 4 (MSB) Maximum Number of Notches = 8 BYTE 5 (LSB) BYTE 6...
  • Page 121 Write Buffer Empty Ratio Page 3 Alternate Sector per Zone Alternate Track per Zone Alternate Track per Logical Unit Sector per Track Track Skew Factor Cylinder Skew Factor Starting Boundary contains the first physical location of the active notch. The first three bytes are the cyl- inder number and the last byte is the head.

  • Page 122: A (Power Control)

    7.9.12 Page 1A (Power Control) Default BYTE 0 RSVD Page Code = 01Ah BYTE 1 Page Length = 0Ah BYTE 2 Reserved = 0 BYTE 3 Reserved = 0 Idle Standby BYTE 4 (MSB) Idle Condition Timer = 0 BYTE 7 (LSB) BYTE 8 (MSB) Standby Condition Timer...

  • Page 123: C (Informational Exceptions Control)

    7.9.13 Page 1C (Informational Exceptions Control) Default BYTE 0 RSVD=0 Page Code = 1Ch BYTE 1 Page Length = 0Ah BYTE 2 PERF Reserved = 0 DEXCPT TEST RSVD LOGERR BYTE 3 Reserved = 0 Method of Reporting BYTE 4 (MSB) BYTE 5 Interval Timer...
  • Page 124 PERF (Performance) bit is not used. Method of Reporting Informational Exceptions indicates the methods used by the Target to report infor- mational exception conditions. Code Description No reporting of informational exception condition: This method instructs the target to not report informational exception condition.

  • Page 125: Mode Sense (5A)

    7.10 MODE SENSE (5A) Byte Command Code = 5Ah Reserved = 0 Page Code Reserved = 0 Reserved = 0 Reserved = 0 Reserved = 0 (MSB) Allocation Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 85. M O D E SENSE (5A) The M O D E SENSE (5A) command provides a means for the file to report various device parameters to the initiator.

  • Page 126: M O D E Select (15)

    7.11 MODE SELECT (15) Byte Command Code = 15h PF = 1 Reserved = 0 Reserved = 0 Parameter List Length VU = 0 Reserved = 0 FLAG LINK Figure 86. M O D E SELECT (15) The M O D E SELECT (15) command provides a means for the initiator to specify L U N or device parame- ters to the Target.
  • Page 127 CHECK CONDITION status with sense key of ILLEGAL REQUEST. See 7.9, “MODE SENSE (1A)” on page 88. Note: If an initiator sends a M O D E SELECT command that changes any parameters that apply to other initiators, the file shall generate an unit attention condition for all initiators except the one that issued the M O D E SELECT command.

  • Page 128: M O D E Select (55)

    7.12 MODE SELECT (55) Byte Command Code = 55h PF = 1 Reserved = 0 Reserved = 0 (MSB) Parameter List Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 87. M O D E SELECT (55) The M O D E SELECT (55) command provides a means for the initiator to specify L U N or device parame- ters to the Target.

  • Page 129: Pre-Fetch (34)

    7.13 PRE-FETCH (34) Byte Command Code = 34h Reserved = 0 Immed RelAdr (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 88. Pre-Fetch (34) The PRE-FETCH command requests the file to transfer data to the cache. No data is transferred to the initiator.

  • Page 130: Re Ad (08)

    7.14 READ (08) Byte Command Code = 08h (MSB) Logical Block Address (LSB) Transfer Length VU = 0 Reserved = 0 FLAG LINK Figure 89. R E A D (08) The READ command requests the file to transfer the specified number of blocks of data to the initiator starting at the specified logical block address.

  • Page 131: Read Capacity (25)

    7.15 READ CAPACITY (25) Byte Command Code = 25h Reserved = 0 RelAdr (MSB) Logical Block Address (LSB) Reserved = 0 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 90. R E A D CAPACITY (25) The READ CAPACITY command returns information regarding the capacity of the file.
  • Page 132 BYTE 0 (MSB) BYTE 1 Logical Block Address BYTE 2 BYTE 3 (LSB) BYTE 4 (MSB) BYTE 5 Block Length BYTE 6 = 512 BYTE 7 (LSB) Figure 91. Format of R E A D CAPACITY command reply Block Length specifies the length in bytes of the block. It is set to 512. O E M Spec.

  • Page 133: Read Defe C T Data (37)

    7.16 READ DEFECT DATA (37) Byte Command Code = 37h Reserved = 0 Reserved = 0 Plist Glist Defect List Format Reserved = 0 (MSB) Allocation Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 92. Read Defect Data (37) The READ DE FE CT DATA command requests that the Target transfers the medium defect data to the initiator.

  • Page 134: Defect List Header

    Note: The file will terminate the Data In phase when the Allocation Length has been transferred or when all available Defect Data has been transferred to the initiator, whichever is less. The Read Defect Data contains a four byte header, followed by zero or more defect descriptors. 7.16.1 Defect List Header Defect List Header BYTE 0...
  • Page 135 Defect Descriptors BYTE 0 (MSB) BYTE 1 Cylinder Number of Defect BYTE 2 (LSB) BYTE 3 Head Number of Defect BYTE 4 (MSB) BYTE 5 Defective Sector Number BYTE 6 BYTE 7 (LSB) Figure 95. Defect Descriptors of Physical Sector Format The defect list format field specifies the format of the defect list data returned by the target.

  • Page 136: Read Extended (28)

    7.17 READ EXTENDED (28) Byte Command Code = 28h Reserved RelAdr (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 96. Read Extended (28) The READ EXTENDED command requests the file to transfer data to the initiator. The larger Logical Block Address and Transfer Length fields permit greater quantities of data to be requested per command than with the READ command and are required to access the full LBA range of the larger capacity drives.

  • Page 137: Read Buffer (3C)

    7.18 READ BUFFER (3C) Byte Command Code = 3Ch Reserved = 0 Mode Buffer ID = 0 (MSB) Buffer Offset (LSB) (MSB) Allocation Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 97. R E A D B U F F E R (3C) The READ B U F F E R command is used in conjunction with the WRITE B U F F E R command as a diag- nostic function for testing the file's memory and the SCSI bus integrity.

  • Page 138: Read Data (Mode 010B)

    BYTE 0 RSVD = 0 BYTE 1 (MSB) Buffer Capacity BYTE 2 BYTE 3 (LSB) Figure 98. R E A D B U F F E R Header The buffer capacity specifies the total number of data bytes that are available in the file's data buffer. This number is not reduced to reflect the allocation length nor is it reduced to reflect the actual number of bytes written using the WRITE B U F F E R command.
  • Page 139 BYTE 0 Offset Boundary BYTE 1 (MSB) Buffer Capacity BYTE 2 BYTE 3 (LSB) Figure 99. R E A D B U F F E R DESCRIPTOR The value contained in the Buffer Offset field of subsequent WRITE B U F F E R and READ B U F F E R com- mands should be a multiple of two to the power of the offset boundary.

  • Page 140: Read Long (3E)

    7.19 READ LONG (3E) Byte Command Code = 3Eh Reserved = 0 CORT RelAdr (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Byte Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 100. R E A D L O N G (3E) The R EAD LONG command requests the file to transfer one block of data to the initiator.

  • Page 141: Reassign Blocks (07)

    7.20 REASSIGN BLOCKS (07) Byte Command Code = 07h Reserved = 0 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 101. REASSIGN BLOCKS (07) The REASSIGN BLOCKS command requests the file to reassign a logical block to an available spare. The REASSIGN BLOCKS command attempts to allocate spare blocks on a spare track.
  • Page 142 BYTE 0 RSVD = 0 BYTE 1 RSVD = 0 BYTE 2 (MSB) Defect list length = 4/8/12/16 BYTE 3 (LSB) BYTE 4 (MSB) Defective BYTE 5 Logical BYTE 6 Block BYTE 7 Address 1 (LSB) BYTE 8 (MSB) Defective BYTE 9 Logical BYTE 10...

  • Page 143: Receive Diagnostics (1C)

    7.21 RECEIVE DIAGNOSTICS (1C) Byte Command Code = 1Ch Reserved = 0 Reserved = 0 (MSB) Parameter List Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 103. RECEIVE DIAGNOSTIC (1C) The Receive Diagnostic command requests that analysis data requested by a Send Diagnostics command be sent to the initiator.
  • Page 144 Byte Reserved = 0 Supplied Format ALTS ALTT Reserved = Translate Format 6 - 13 Translated Address Supplied Format is the value supplied by the Send Diagnostic command it may be one of the three fol- lowing values 000b Block format 100b Bytes From Index format 101b Physical Sector format It specifies the format in which the address has been supplied.

  • Page 145: Release (17)

    7.22 RELEASE (17) Byte Command Code = 17h 3rdPty 3rd Party ID Ext = 0 Reservation Identification Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 104. RELEASE (17) The RELEASE command is used to release a L U N previously reserved. Note: It is not an error for an initiator to release a L U N that is not currently reserved.

  • Page 146: Release (57)

    7.23 RELEASE (57) Byte Command Code = 57h 3rdPty Reserved Ext = 0 Reservation Identification Third Party Device ID Reserved = 0 Reserved = 0 Reserved = 0 Reserved = 0 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 105.

  • Page 147: Request Sense (03)

    7.24 REQUEST SENSE (03) Byte Command Code = 03h Reserved = 0 Reserved = 0 Allocation Length VU = 0 Reserved = 0 FLAG LINK Figure 106. REQUEST SENSE (03) The REQUEST SENSE command requests the file to transfer sense data. The sense data shall be available when following conditions, The previous command to the specified I_T_L nexus terminated with CHECK CONDITION status.

  • Page 148: Reserve (16)

    7.25 RESERVE (16) Byte Command Code = 16h 3rdPty 3rd Party ID Ext = 0 Reservation Identification (MSB) Extent List Length = 0 (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 107. RESERVE (16) The RESERVE command is used to reserve a L U N for an initiator. This reservation can be either for; 1.

  • Page 149: Reserve (56)

    7.26 RESERVE (56) Byte Command Code = 56h 3rdPty Reserved Ext = 0 Reservation Identification Third Party Device ID Reserved = 0 Reserved = 0 Reserved = 0 (MSB) Extent List Length = 0 (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 108.
  • Page 150 Only the Initiator that issued the Reserve command for a L U N may release the LUN, regardless of the 3rdPty option. This Initiator may also release the L U N by issuing another Reserve command. This super- seding Reserve command releases the previous reservation when the new reservation is granted. Reservation queuing is not supported by the Drive.

  • Page 151: R E Z E R O U N I T (01)

    7.27 REZERO UNIT (01) Byte Command Code = 01h Reserved = 0 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 109. REZERO UNIT (01) The R E Z E R O U N I T command requests that the target seek to logical block address 0. SCSI C O M M A N D SET...

  • Page 152: Seek (0B)

    7.28 SEEK (0B) Byte Command Code = 0Bh (MSB) Logical Block Address (LSB) Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 110. SEEK (0B) The SEEK command requests the file to seek to the specified logical block address. O E M Spec.

  • Page 153: Seek Extended (2B)

    7.29 SEEK EXTENDED (2B) Byte Command Code = 2Bh Reserved = 0 (MSB) Logical Block Address (LSB) Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 111. SEEK E X T E N D E D (2B) The SEEK EXTENDED command requests the file to seek to the specified logical block address.

  • Page 154: Send Diagnostic (1D)

    7.30 SEND DIAGNOSTIC (1D) Byte Command Code = 1Dh RSVD =0 SlfTst DevOfl UntOfl Reserved = 0 (MSB) Parameter List Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 112. SEND DIAGNOSTIC (1D) The SEND DIAGNOSTIC command requests the file to perform its self-diagnostic test, or to perform a function based on a page of information sent in a Data Out phase during the command.

  • Page 155: Send Diagnostic Pages

    Both tests are performed as a result of the SEND DIAGNOSTIC command. The SEND DIAGNOSTICS will fail with CHECK CONDITION status if it is issued while the spindle motor is not turning. (Such as after STOP command has been received.) Note: The self diagnostic is also performed at Power On Reset time.
  • Page 156 terminate with CHECK CONDITION status with a Sense of Illegal Request and Illegal Field in Param- eter List. Address to Translate contains the address to translate. If the logical block format is specified then the first 4 bytes of the field, i.e. bytes 6 to 9, contain the LBA and the remainder must be zero. For the physical format the address must be specified as follows.

  • Page 157: Start/Stop Unit (1B)

    7.31 START/STOP UNIT (1B) Byte Command Code = 1Bh Reserved = 0 Immed Reserved = 0 Reserved = 0 Start VU = 0 Reserved = 0 FLAG LINK Figure 113. START/STOP Unit (1B) The START/STOP UNIT command is used to spin up or stop the spindle motor. Immed bit is to specify Status is to be returned at the end of the operation.

  • Page 158: Synchronize Cache (35)

    7.32 SYNCHRONIZE CACHE (35) Byte Command Code = 35h Reserved = 0 Immed RelAdr (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Number of Blocks (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 114. SYNCHRONIZE CACHE (35) The SYNCHRONIZE CACHE Command ensures that logical blocks in the cache have their most recent data value recorded on the media.

  • Page 159: Test Unit Ready (00)

    7.33 TEST UNIT READY (00) Byte Command Code = 00h Reserved = 0 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 115. TEST UNIT READY (00) The TEST UNIT READY command allows the initiator to check if the file is READY. The SCSI specifi- cation defines READY as the condition where the device will accept a media-access command without returning CHECK CONDITION status.

  • Page 160: Verify (2F)

    7.34 VERIFY (2F) Byte Command Code = 2Fh Reserved = 0 ByteChk (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 116. VERIFY (2F) The VERIFY command requests that the file verify the data written on the media. A verification length of zero indicates that no data will be transferred.

  • Page 161: Write (0A)

    7.35 WRITE (0A) Byte Command Code = 0Ah (MSB) Logical Block Address (LSB) Transfer Length VU = 0 Reserved = 0 FLAG LINK Figure 117. WRITE (0A) The WRITE command requests the file to write the specified number of blocks of data from the initiator to the medium starting at the specified logical block address.

  • Page 162: Write Extended (2A)

    7.36 WRITE EXTENDED (2A) Byte Command Code = 2Ah Reserved RelAdr (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 118. WRITE E X T E N D E D (2A) The WRITE EXTENDED command requests that the file write the data transferred from the initiator.

  • Page 163: Write And Verify (2E)

    7.37 WRITE AND VERIFY (2E) Byte Command Code = 2Eh Reserved ByteChk RelAdr (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 119. WRITE A N D VERIFY (2E) WRITE AND VERIFY command requests that the file writes the data transferred from the initiator to the medium and then verify that the data is correctly written.

  • Page 164: Write Buffer (3B)

    7.38 WRITE BUFFER (3B) Byte Command Code = 3Bh Reserved = 0 Mode Buffer ID (MSB) Buffer Offset (LSB) (MSB) Parameter List Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 120. WRITE B U F F E R (3B) The WRITE B U F F E R command is used in conjunction with the RE AD B U F F E R command as a diag- nostic function for testing the file's memory and the SCSI bus integrity.

  • Page 165: Write Data (Mode 010B)

    Buffer Offset must be zero. If another value is specified, no download function are performed and the command is terminated with CHECK CONDITION status. And File shall set sense key to ILLEGAL REQUEST and additional sense code to ILLEGAL FIELD IN CDB. Parameter List Length specifies the number of bytes that shall be transferred during the DATA O U T phase.

  • Page 166: Download Microcode And Save (Mode 101B)

    00h : Main Microprocessor Code 81h : Reserved Area Data Any other value for the Buffer ID will cause the command to terminate with CHECK CONDITION status. The file shall set sense key to ILLEGAL REQUEST and additional sense code to ILLEGAL FIELD IN CDB.
  • Page 167 Any other value for the Buffer ID will cause the command to terminate with CHECK CONDITION status. The file shall set sense key to ILLEGAL REQUEST and additional sense code to ILLEGAL FIELD IN CDB. 7.38.4.1 Download Microprocessor Microcode and Save (Buffer_ID = 00h) There are 3 types of download function are supported.
  • Page 168 If an invalid value is specified, the command is terminated with CHECK CONDITION status . File shall set sense key to ILLEGAL REQUEST and additional sense code to ILLEGAL FIELD IN CDB. Parameter List Length must be specified for the total byte length of each data set. It may also be set 0000h in which case no code is updated.

  • Page 169: Write Long (3F)

    7.39 WRITE LONG (3F) Byte Command Code = 3Fh Reserved = 0 RelAdr (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Byte Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 122. WRITE L O N G (3F) The WRITE LONG command requests the file to write one block of data transferred from the initiator.

  • Page 170: Write Same (41)

    7.40 WRITE SAME (41) Byte Command Code = 41h Reserved = 0 RelAdr (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Number of Blocks (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 123. WRITE SAME (41) The Write Same command instructs the Target to write a single block of data, transferred to the Target from the Initiator, to a number of sequential logical blocks.

  • Page 171: Scsi Status Byte

    This status indicates that the target's command queue is full. If tagged command queuing feature is enabled and there is no room on the command queue, this status is returned when the initiator sends a command. For this status, sense is not valid. Copyright IBM Corp. 1997...
  • Page 172 O E M Spec. of DDRS-3xxxx...

  • Page 173: Scsi Message System

    If an unsupported message is received, the file will send the MESSAGE REJECT message to the initiator. If at the time the unsupported message is received a valid NEXUS exists then the file will continue with the command. If no valid NEXUS exists then the file will go to Bus Free. Copyright IBM Corp. 1997...

  • Page 174: C O M M A N D Complete (00)

    9.1.1 COMMAND COMPLETE (00) The file sends this message to the initiator to indicate that the execution of a command has terminated and that valid status has been sent to the initiator. After successfully sending this message, the file releases all bus signals and goes to BUS F R E E phase.
  • Page 175 9.1.2.1.1 On LVD receiver mode.: The Tareget responds to each Initiator requested transfer period as shown in the following figure Figure 127 on page 165: Target Maximum Initiator Target Transfer Burst Request Response Period Rate 0 <= Mi <= 09 Mt = 10 ( Asynchronous mode ) 10 <= Mi <= 10...
  • Page 176 9.1.2.2 Synchronous Negotiation Started by the Target If the file recognizes that negotiation is required, the file sends a SDR message to the initiator with minimum transfer period on the current receiver mode. The file interprets the Initiator corresponding transfer period as shown in the following figure Figure 129 on page 166: 9.1.2.2.1 On LVD receiver mode.

  • Page 177: Wide Data Transfer Request (01,02,03H)

    Target Maximum Initiator's Transfer Burst Response Period Rate 0 <= Mi <= 11 Send Message Reject(Async mode) 12 <= Mi <= 12 50 nSec 20.00 MT/s 13 <= Mi <= 18 75 nSec 13.33 MT/s 19 <= Mi <= 25 100 nSec 10.00 MT/s 26 <= Mi <= 31...
  • Page 178 The Transfer Width Exponent (E) is two to the transfer width exponent bytes wide. Valid data transfer widths are 8 bits (E = 00h) and 16 bits (E = 01h). Value of E greater than 01h are reserved. 9.1.3.1 Transfer Width Negotiation Started by the Initiator If the Initiator recognizes that negotiation is required and sends a Wide Data Transfer Request message out, the Target responds by changing to the Message In phase and sending a Wide Data Transfer Request message in to the Initiator prior to transfer any additional message bytes (or any other Information phase...

  • Page 179: Save Data Po I Nt E R (02)

    Note: If the corresponding transfer width exponent received from the Initiator indicates a data transfer width that is greater than 16 bits (E > 01h) the Target sends a Message Reject message to the initiator to indicate 8 bit data transfer mode. If the first message received from the Initiator is either a Message Parity Error or a Message Reject message, the Target goes to 8 bit data transfer mode.

  • Page 180: Initiator Detected E R R O R (05)

    9.1.7 INITIATOR DETECTED ERROR (05) This message is sent from an initiator to inform the file that an error has been detected that does not pre- clude the file from retrying the previous COMMAND, DATA and STATUS phase. The source of the error may be either related to previous activities on the SCSI bus or may be internal to the initiator and unrelated to any previous SCSI bus activity If the initiator intends to send this message, the initiator must assert the ATN signal prior to its release of...

  • Page 181: Message Parity E R R O R (09)

    9.1.11 MESSAGE PARITY ERROR (09) This message is sent from the initiator to inform the file that the last message byte received had a parity error. If the initiator intends to send this message, the initiator must assert the ATN signal prior to its release of ACK for the REQ/ACK handshake of the message byte that has the parity error.

  • Page 182: Ignore Wide Residue (23H)

    Byte Value Description Simple Queue Tag message Head of Queue Tag message Ordered Queue Tag message Queue Tag Figure 134. Queue Tag Messages Queue Tag messages are used to specify an identifier, called a Queue Tag, for an I/O process which establish the I_T_L_Q nexus.

  • Page 183: Identify (80 - Ff)

    Byte Value Description Ignore Wide Residue message Ignore Figure 135. Ignore Wide Residue Message Format The Ignore Wide Residue Message is sent from the target to indicate that the number of valid bytes sent during the last REQ/ACK handshake of a DATA IN phase is less than the negotiated transfer width. The ignore field (always = 01h) indicates that one byte (data bits 8-15) should be ignored.
  • Page 184 Note: The initiator may send the INITIATOR DETECTED E R R O R message as a result of an initiator detected SCSI Bus parity error or an internal error. Retry MESSAGE IN phase The retry will be caused by the receipt of a MESSAGE PARITY E R R O R message immediately following a MESSAGE IN phase.

  • Page 185: Attention Condition

    9.3 Attention Condition The attention condition allows an initiator to inform the file that a MESSAGE O U T phase is desired. initiator may create the attention condition by asserting the ATN signal at any time except during the ARBITRATION or BUS F R E E phases. The initiator must create the attention condition by asserting the ATN signal least two deskew delays before releasing ACK for the last byte transferred in a bus phase to guarantee that the attention condition will be honored before transition to a new bus phase.

  • Page 186: Unexpected Bus Free Phase Error Condition

    9.4.1 Unexpected BUS FREE Phase Error Condition There are several error conditions that will cause the file to immediately change to the BUS F R E E phase, regardless of the state of the ATN signal. The file will not attempt to reconnect to the initiator to complete the operation that was in progress when the error condition was detected.

  • Page 187: Initiator Detected Error Message

    9.4.6 INITIATOR DETECTED ERROR Message An INITIATOR DETECTED E R R O R message is valid after a COMMAND, DATA IN/OUT or STATUS phase has occurred. If another phase has occurred, the message is rejected. The file will, depending on the model, optionally retry the previous phase is it is command or status. If this fails or the previous phase was a data transfer the file will generate a CHECK CONDITION status and a Sense key of ABORTED C O M M A N D with additional sense code of INITIATOR DETECTED E R R O R .
  • Page 188 O E M Spec. of DDRS-3xxxx...

  • Page 189: Additional Information

    Check Condition. 10.1.2 Invalid LUN in Identify Message There are three different circumstances defined within the SCSI protocol when the response to an invalid L U N will occur. Each of these result in a different response. Copyright IBM Corp. 1997...

  • Page 190: Incorrect Initiator Connection

    10.1.2.1 Case 1 - Selection message sequence with Inquiry command The INQUIRY command is a special case in SCSI. It is used to configure the bus when file IDs and LUNs are not known. The proper response is to return the inquiry data with a peripheral drive type of 1Fh which indicates that the specified L U N is not supported.
  • Page 191 Queue Full Status is returned Busy Status is returned If an active I/O process does exist when the Target receives a new command, then the Target determines how the new command should be handled based on the following rules: Check Condition Status is returned with Sense Key set to Aborted Command for an Overlapped Com- mands Attempted error if: See 10.1.3, “Incorrect Initiator Connection”...
  • Page 192 the command would otherwise be queued(according to the rules described above)but disconnection is not allowed for the current I/O process, or If a command is queued, command execution may still be prevented at a later time when the command is dequeued to become an active I/O process.

  • Page 193: Unit Attention Condition

    10.1.5 Unit Attention Condition The file will generate a unit attention condition for each initiator whenever: The file has been reset. This includes Power On Reset, SCSI Bus Reset, SCSI BUS DEVICE RESET message. The mode parameters in effect for this initiator has been changed by another initiator. The microcode has been changed.

  • Page 194: Internal Error Condition

    REQUEST SENSE Executes the command, returns a Sense key of N O T READY and an Additional Sense Code of LOGICAL UNIT N O T READY and returns G O O D STATUS. The Additional Sense Code Qualifier that is returned depends on type of I/O proc- esses that are active: For the START/STOP UNIT and the Auto-start operation, the qualifier returned is LOGICAL UNIT IS IN PROCESS O F BECOMING READY.

  • Page 195: Degraded Mode

    10.1.9 Degraded Mode There are certain errors or conditions which may impair the file's ability to function normally. Rather than fail hard, the file is designed to be as responsive as possible. Also, in most cases, some action on the part of the initiator may be used to restore normal operation.

  • Page 196: Command Processing While Reserved

    Degraded Entry Reason Accepting Description and sense code Mode Request U-code Can not read Same as Spin-up Return U-code Degraded Mode. u-code Degrade Sense code = 4085 (u-code download fail) Reserved All commands. Reserved area sector valid check failed. Defective Area Fail to read sector found in reserved area.

  • Page 197: Priority Commands

    If a Reservation Conflict Status is not reported and the command is permitted, then the Target checks the next highest priority internal condition to determine whether execution is allowed. See 10.1.1, “Priority of SCSI Status Byte Reporting” on page 179 10.2 Priority Commands Certain SCSI commands always execute without returning a Busy Status, Reservation Conflict Status in response to the command.

  • Page 198: Tagged Queuing

    10.3.2 Tagged queuing Commands with a tag message are saved in the command queue. Queued commands will be reordered by the target defined rule. See the section on Reordering 10.4, “Command reordering” on page 189 for details. 10.3.3 Untagged queuing The target supports queuing one I/O process from each initiator.

  • Page 199: Command Reordering

    10.4 Command reordering Command reordering function is supported under tagged command queuing enabled (DQue = 0). The reorder feature reorders Read/Write commands in order to minimize seek time between commands. This function will improve total thruput of the drive. 10.5 Concurrent I/O Process The Concurrent I/O process is that plural I/O processes are active (not queued) on the same logical unit at the same time.

  • Page 200: Power Saving Mode

    10.8 Power Saving Mode Power save function will save power consumption while the drive is idle. The drive automatically transfers its operating mode according to the event and timer. 10.9 Automatic Rewrite/Reallocate The target supports Auto and Recommended Reallocate for READ, WRITE, WRITE VERIFY and VERIFY.
  • Page 201 Write portion of Write and Verify For all other commands the AWRE setting is ignored and the target will not automatically reallocate or recommend reassign. Auto/Recommend Reallocate information is communicated via the sense data returned following a command during which a site was determined to need rewriting or reassignment. The LBA returned in the sense data is the LBA that determined to need rewriting or reassignment.

  • Page 202: Segmented Caching

    10.10 Segmented Caching 10.10.1 Overview Segmented Caching divides the data buffer into several smaller buffers. Each buffer is used as Read/Write/Read-Ahead buffer. 10.10.2 Read Ahead The Read Ahead function consists of reading data that the Initiator has not yet requested to the file buffer. This function is intended to improve performance for an initiator that frequently accesses sequential data with successive SCSI read commands.

  • Page 203: Selection Without Atn

    10.14 Selection without ATN If the target is selected without ATN signal active, no Identify message is received from the initiator. In this case, the L U N is identified from the CDB and disconnect permission is disabled. The target does not perform any phase retries.

  • Page 204: Contingent Allegiance Condition

    10.16 Contingent allegiance Condition The contingent allegiance condition shall exist following the return of Check Condition, except Check Con- dition caused by Invalid LUN. Execution of all queued commands shall be suspended until the contingent allegiance condition is cleared. The contingent allegiance condition can be cleared by the initiator in one of the following ways: By issuing a REQUEST SENSE command to the Target and receiving the sense data.

  • Page 205: Reset

    10.17 Reset The Reset condition is used to clear all SCSI devices from the bus. This condition takes precedence over all other phases and conditions. After a reset condition is detected and the reset actions completed, the target returns to a 'SCSI bus enabled' state that allows the target to accept SCSI commands. This device uses the Hard reset option as defined in the SCSI-2 standard.

  • Page 206: Diagnostics

    10.18 Diagnostics The file will execute a self test at power on or when a Send Diagnostics command is issued with the self test bit set. The diagnostics are to assure the correct operation of the file and to verify that the check circuits detect fault conditions.

  • Page 207: Idle Time Functions

    10.19 Idle Time Functions 10.19.1.1 Automatic Drive Maintenance (ADM) Enable and disable of A D M function is in control of Mode Page 0, and the shipping default is disable. A D M function is equipped to enhance the reliability in continuous usage. A D M function is to perform a CSS automatically after detection of idling time for 1 minute at intervals of 1 week.
  • Page 208 O E M Spec. of DDRS-3xxxx...

  • Page 209: Scam

    C/D signal. If the C/D signal is true, there is a SCAM intiator present and the drive shall enter the ID Assignable state. If the C/D signal is false, no SCAM initiator is present and the drive shall Copyright IBM Corp. 1997...
  • Page 210 enter the SCAM Monitor state. Note that a drive make only one attempt to initiate SCAM protocol after power-on. While in the SCAM Monitor state, a drive shall monitor the SCSI bus for both SCAM selection and normal SCSI selection. If the drive detects the initiation of SCAM protocol, it shall enter the ID Assign- able state.

  • Page 211: Identification String

    11.2 Identification string Following string shall be sent out as the Identification string when the Isolation stage. byte Note DDRS-34560 DDRS-39130 DDRS-34560W DDRS-39130W 0 Type code Default ID 2 vendor identifi- cation 10 Product ID 22 serial number serial number (ASCII) not used Figure 137.

  • Page 212: Function Codes

    11.3 Function codes The following function codes are supported. Function Code Description 00000b Isolate 00001b Isolate and set priority flag 00011b Configuration process complete 01111b Dominant initiator contention 11111b Synchronization others reserved Figure 138. SCAM Identification string Isolate This function code may be used by SCAM initiators to assign ID's to SCAM device. After the function code, SCAM targets with unassigned ID's participate in an isolation stage.

  • Page 213: Action Codes

    11.4 Action codes The following Action codes are supported. First quintet Second quintet Description 11000b ccnnnb Assign ID 00nnnb 10001b ccnnnb Assign ID 01000b 11000b Clear priority flag 10010b Locate on 10100b 01011b Locate off others Reserved others Reserved note. cc is the count of zero bits in nnn. Figure 139.
  • Page 214 O E M Spec. of DDRS-3xxxx...

  • Page 215: Scsi Sense Data

    Vender unique Error information BYTE 24 Product Specific Information BYTE 30 Reserved = 0 Figure 140. Format of Sense Data. Format of the Sense Data returned by the file in response to the REQUEST SENSE command Copyright IBM Corp. 1997...

  • Page 216: Sense Data Description

    12.2 Sense Data Description 12.2.1 Valid (Bit 7 of byte 0) The Information Bytes (byte 3 thru 6) are not defined. The Information Bytes (byte 3 thru 6) contain a valid logical block address. 12.2.2 Error Code (Bit 6 - 0 of byte 0) 70h Current Error.

  • Page 217: Information Bytes (Byte 3 Thru 6)

    nated without altering the medium. If an invalid parameter is found in parameters supplied as data, then the file might have altered the medium. Unit Attention Indicates that the file entered in the 'Unit Attention Condition'. (See 10.1.5, “Unit Atten- tion Condition”...

  • Page 218: Additional Sense Code/Qualifier (Byte 12 And 13)

    12.2.8 Additional Sense Code/Qualifier (Byte 12 and 13) The following table shows the description of the combination of Sense Key / Sense Code / Qualifier. Code Qual Description No error. No sense. Predictive Failure Analysis threshold reached. Recovered write error no index Recovered no seek comp Recovered write error.
  • Page 219 Code Qual Description Diag Fail - R A M Microcode Not Loaded. Medium error. Recommend Reassign. Medium error. ID C R C error. Medium error. Unrecovered read error. Medium error. Record not found. Medium error. Data synchronization mark error. (DAM error) Medium error.
  • Page 220 Code Qual Description Aborted command. Unsupported LUN. The drive supports L U N 0 only. Aborted command. Message reject error. A message reject error occurs when an inappropriate or unexpected message reject is received from the ini- tiator or the initiator rejects a message twice. Aborted command.

  • Page 221: Fru : Field Replaceable Unit (Byte 14)

    12.2.9 FRU : Field Replaceable Unit (Byte 14) The F R U (Field Replaceable Unit) field value will always be zero. 12.2.10 Sense Key Specific (Byte 15 thru 17) The definition of this field is determined by the value of the sense key field. 12.2.10.1 Sense Key Specific - Illegal Request (Sense Key = 5h) Error filed pointer is returned.

  • Page 222: Reserved (Byte 18 Thru 19)

    12.2.10.2 Sense Key Specific - Recovered (Sense Key = 1h) Hardware (Sense Key = 4h) or Medium Error (Sense Key = 3h) Actual Retry Count is reported. BYTE 15 SKSV Reserved BYTE 16 (MSB) Actual Retry Count BYTE 17 (LSB) Figure 142.

  • Page 223: Vender Unique Error Information (Byte 20 Thru 23)

    12.2.12 Vender unique error information (Byte 20 thru 23) This field gives detail information of the error. It contains a unique code which describes where the error was detected and which piece of hardware or microcode detected the error. 12.2.13 Physical Error Record (Byte 24 thru 29) ILI = 1 - This field contains zeros.
  • Page 224 O E M Spec. of DDRS-3xxxx...

  • Page 225: Index

    C O M M A N D COMPLETE BUS DEVICE RESET Command Processing During Execution of Active I/O CLEAR QUEUE T A G process C O M M A N D COMPLETE Command Processing While Reserved DISCONNECT Copyright IBM Corp. 1997...
  • Page 226 MESSAGE SYSTEM (continued) IDENTIFY QUEUE T A G MESSAGES(20h, 21h, 22h) I G N O R E WIDE RESIDUE INITIATOR DETECTED E R R O R L I N K E D C O M M A N D COMPLETE L I N K E D C O M M A N D COMPLETE WITH R E A D F L A G...
  • Page 227 WIDE DATA TRANSFER REQUEST WRITE WRITE A N D VERIFY WRITE B U F F E R Write Cache WRITE E X T E N D E D WRITE L O N G WRITE SAME Index...
  • Page 228 Part Number 00K0097 S00K-0097-03 Published in Japan...

This manual is also suitable for:

Ddrs-34560

Table of Contents