SCSI Primary Commands - 2.pdf

18 July 2001 T10/1236-D Revision 20Table 53 defines the relationships between the ADDR16 and WBUS16 bits.Table 53 — Maximum logical device configuration tableADDR16 WBUS16 Description0 0 8 bit wide data path on a single cable with8 SCSI IDs supported0 1 16 bit wide data path on a single cablewith 8 SCSI IDs supported1 1 16 bit wide data path on a single cablewith 16 SCSI IDs supportedThe CLOCKING field shall not apply to asynchronous transfers and is defined in table 54.Table 54 — CLOCKING fieldCode00b01b10b11bDescriptionIndicates the device server supports only STIndicates the device server supports only DTReservedIndicates the device server supports ST and DTA quick arbitration and selection supported (QAS) bit of one indicates that the device server supports quickarbitration and selection. A value of zero indicates that the device server does not support quick arbitration andselection.An information units supported (IUS) bit of one indicates that the device server supports information unit transfers.A value of zero indicates that the device server does not support information unit transfers.NOTE 14 The acronyms ST and DT and the terms 'quick arbitration and selection' and 'information units' aredefined in SPI-3, SPI-4, and possibly later revisions of the SCSI parallel interface standard.7.3.4 Vital product dataThe application client requests the vital product data information by setting the EVPD bit to one and specifying thepage code of the desired vital product data. See 8.4 for details about vital product data. The information returnedconsists of configuration data (e.g., vendor identification, product identification, model, serial number), manufacturingdata (e.g., plant and date of manufacture), field replaceable unit data and other vendor specific or devicespecific data. If the device server does not implement the requested page it shall return CHECK CONDITIONstatus. The a sense key shall be set to ILLEGAL REQUEST and the additional sense code shall be set to INVALIDFIELD IN CDB.NOTES15 The device server should have the ability to process the INQUIRY command even when an error occurs thatprohibits normal command completion. In such a case, CHECK CONDITION status should be returned forcommands other than INQUIRY or REQUEST SENSE. The sense data returned may contain the fieldreplaceable unit code. The vital product data may be obtained for the failing device using the INQUIRYcommand.16 This standard defines a format that allows device-independent application client software to display the vitalproduct data returned by the INQUIRY command. The contents of the data may be vendor specific, and maybe unusable without detailed information about the device.17 This standard does not define the location or method of storing the vital product data. The retrieval of the datamay require completion of initialization operations within the device, that may induce delays before the data isdpANS SCSI Primary Commands - 2 (SPC-2) 91