SCSI Primary Commands - 2.pdf

More documents

Recommendations

Info

T10/1236-D Revision 20 18 July 2001A page format (PF) bit of one specifies that the SEND DIAGNOSTIC parameters and any parameters returned by afollowing RECEIVE DIAGNOSTIC RESULTS command shall conform to the page structure as specified in thisstandard. See 8.1 for the definition of diagnostic pages.A PF bit of zero indicates that all SEND DIAGNOSTIC parameters are vendor specific. If the content of thePARAMETER LIST LENGTH field is zero and the SEND DIAGNOSTIC command will not be followed by a correspondingRECEIVE DIAGNOSTIC RESULTS command then the PF bit shall be zero. The implementation of the PFbit is optional.A self-test (SELFTEST) bit of one directs the device server to complete the target’s default self-test. If the self-testsuccessfully passes, the command shall be terminated with GOOD status; otherwise, the command shall be terminatedwith CHECK CONDITION status and the sense key shall be set to HARDWARE ERROR.A SELFTEST bit of zero requests that the device server perform the diagnostic operation specified by the SELF-TESTCODE field or in the parameter list. The diagnostic operation might or might not require the device server to returnparameter data that contains diagnostic results. If the return of parameter data is not required, the return of GOODstatus indicates successful completion of the diagnostic operation. If the return of parameter data is required, thedevice server shall either:a) perform the requested diagnostic operation, prepare the parameter data to be returned and indicatecompletion by returning GOOD status. The application client issues a RECEIVE DIAGNOSTIC RESULTScommand to recover the parameter data; orb) accept the parameter list, and if no errors are detected in the parameter list, return GOOD status. Therequested diagnostic operation and the preparation of the parameter data to be returned are performedupon receipt of a RECEIVE DIAGNOSTIC RESULTS command.A UNITOFFL bit of one grants permission to the device server to perform diagnostic operations that may affect theuser accessible medium on the logical unit (e.g., write operations to the user accessible medium, or repositioningof the medium on sequential access devices). The implementation of the UNITOFFL bit is optional. A UNITOFFL bitof zero prohibits any diagnostic operations that may be detected by subsequent tasks. When the SELFTEST bit iszero, the UNITOFFL bit shall be ignored.A DEVOFFL bit of one grants permission to the device server to perform diagnostic operations that may affect all thelogical units on a target (e.g., alteration of reservations, log parameters, or sense data). The implementation of theDEVOFFL bit is optional. A DEVOFFL bit of zero prohibits diagnostic operations that may be detected by subsequenttasks. When the SELFTEST bit is zero, the DEVOFFL bit shall be ignored.The PARAMETER LIST LENGTH field specifies the length in bytes of the parameter list that shall be transferred from theapplication client to the device server. A parameter list length of zero indicates that no data shall be transferred.This condition shall not be considered an error. If the specified parameter list length results in the truncation of oneor more pages (PF bit set to one) the device server shall return CHECK CONDITION status with a sense key ofILLEGAL REQUEST and an additional sense code of INVALID FIELD IN CDB.NOTE 36 To ensure that the diagnostic command information is not destroyed by a command sent from anotherinitiator, either the SEND DIAGNOSTIC command should be linked to the RECEIVE DIAGNOSTIC RESULTScommand or the logical unit should be reserved.160 dpANS SCSI Primary Commands - 2 (SPC-2)
18 July 2001 T10/1236-D Revision 207.24 SET DEVICE IDENTIFIER commandThe SET DEVICE IDENTIFIER command (see table 114) requests that the device identifier information in thelogical unit be set to the value received in the SET DEVICE IDENTIFIER parameter list. As defined in the SCC-2standard, the SET DEVICE IDENTIFIER command is the SET PERIPHERAL DEVICE/COMPONENT DEVICEIDENTIFIER service action of the MAINTENANCE OUT command. Additional MAINTENANCE IN and MAINTE-NANCE OUT service actions are defined in SCC-2 and in this standard.The MAINTENANCE OUT service actions defined only in SCC-2 shall apply only to SCSI devices that return adevice type of 0Ch or the SCCS bit equal to one in their standard INQUIRY data. When a SCSI devices returns adevice type of 0Ch or the SCCS bit equal to one in its standard INQUIRY data, the implementation requirements forthe SCC-2 MAINTENANCE OUT service actions shall be as specified in SCC-2. Otherwise the MAINTENANCEOUT service action definitions and implementation requirements stated in this standard shall apply.On successful completion of a SET DEVICE IDENTIFIER command a unit attention shall be generated for all initiatorsexcept the one that issued the service action. When reporting the unit attention condition the additional sensecode shall be set to DEVICE IDENTIFIER CHANGED.Table 114 — SET DEVICE IDENTIFIER commandBitByte7 6 5 4 3 2 1 00 OPERATION CODE (A4h)1 Reserved SERVICE ACTION (06h)2 Reserved3 Reserved45Restricted6 (MSB)78PARAMETER LIST LENGTH9 (LSB)10 Reserved Restricted Reserved11 CONTROLSCC-2 defines specific usages for bytes 4 and 5, and bit 1 in byte 10, however these fields are reserved for theSET DEVICE IDENTIFIER command defined by this standard.The PARAMETER LIST LENGTH field specifies the length in bytes of the identifier that shall be transferred from theapplication client to the device server. The maximum value for this field shall be 512 bytes. A parameter list lengthof zero indicates that no data shall be transferred, and that subsequent REPORT DEVICE IDENTIFIER commandsshall return an Identifier length of zero. Logical units that implement this command shall be capable of accepting aparameter list length of 64 bytes or less. If the parameter list length exceeds 64 bytes and the logical unit is notcapable of storing the requested number of bytes, then the device server shall return CHECK CONDITION statuswith the sense key set to ILLEGAL REQUEST and an additional sense code of INVALID FIELD IN CDB.dpANS SCSI Primary Commands - 2 (SPC-2) 161
Page 1 and 2:
dpANSProjectT10/1236-DRevision 2018
Page 3:
DraftANSI (r)NCITS.351:200xAmerican
Page 6 and 7:
T10/1236-D Revision 20 18 July 2001
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129: T10/1236-D Revision 20 18 July 2001
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
show all

SCSI Primary Commands - 2.pdf

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?