SCSI Primary Commands - 2.pdf

More documents

Recommendations

Info

T10/1236-D Revision 20 18 July 2001A task aborted status (TAS) bit of zero specifies that aborted tasks shall be terminated by the device server withoutany response to the initiator. A TAS bit of one specifies that tasks aborted by the actions of another initiator shall beterminated with a TASK ABORTED status (see SAM-2).A software write protect (SWP) bit of one specifies that the logical unit shall inhibit writing to the medium after writingall cached or buffered write data, if any. When SWP is one, all commands requiring writes to the medium shallreturn CHECK CONDITION status and shall set the sense key to DATA PROTECT and the additional sense codeto WRITE PROTECTED. When SWP is one and the device model defines a write protect (WP) bit in theDEVICE-SPECIFIC PARAMETER field in the mode parameter header, the WP bit shall be set to one for subsequentMODE SENSE commands. A SWP bit of zero specifies that the logical unit may allow writing to the medium,depending on other write inhibit mechanisms implemented by the logical unit. When the SWP bit is zero, the valueof the WP bit, if defined, is device model specific. For a list of commands affected by the SWP bit and details of theWP bit see the command standard (see 3.1.12) for the specific device type.The RAERP, UAAERP, and EAERP bits enable specific events to be reported via the asynchronous event reportingprotocol. When all three bits are zero, the target shall not use asynchronous event reporting. AER is defined inSAM-2.A ready AER permission (RAERP) bit of one specifies that the device server may issue an asynchronous eventreport upon completing its initialization sequence instead of generating a unit attention condition. A RAERP bit ofzero specifies that the device server shall not issue an asynchronous event report upon completing its initializationsequence.NOTE 49 If the device server’s default value for the RAERP bit is one and it does not implement saved parameters orinclude a hardware switch, then it may be impossible to disable the initialization sequence asynchronous eventreporting.A unit attention AER permission (UAAERP) bit of one specifies that the device server may issue an asynchronousevent report instead of creating a unit attention condition upon detecting a unit attention condition event, other thanupon completing an initialization sequence. A UAAERP bit of zero specifies that the device server shall not issue anasynchronous event reporting instead of creating a unit attention condition.An error AER permission (EAERP) bit of one specifies that the device server may issue an asynchronous eventreport upon detecting a deferred error condition instead of waiting to report the deferred error on the nextcommand. An EAERP bit of zero specifies that the device server shall not report deferred error conditions via anasynchronous event reporting.The AUTOLOAD MODE field specifies the action to be taken by a removable medium device server when a medium isinserted. For devices other than removable medium devices, this field is reserved. Table 158 shows the usage ofthe AUTOLOAD MODE field.Table 158 — AUTOLOAD MODE fieldValue000b001b010b011b - 111bDefinitionMedium shall be loaded for full access.Medium shall be loaded for medium auxiliary memory access only.Medium shall not be loaded.ReservedThe READY AER HOLDOFF PERIOD field specifies the minimum time in milliseconds after the target starts its initializationsequence that it shall delay before attempting to issue an asynchronous event report. This value may berounded up as defined in 5.3.198 dpANS SCSI Primary Commands - 2 (SPC-2)
18 July 2001 T10/1236-D Revision 20The BUSY TIMEOUT PERIOD field specifies the maximum time, in 100 milliseconds increments, that the initiator allowsfor the target to remain busy for unanticipated conditions that are not a routine part of commands from the initiator.This value may be rounded down as defined in 5.3. A 0000h value in this field is undefined by this standard. AnFFFFh value in this field is defined as an unlimited period.The EXTENDED SELF-TEST COMPLETION TIME field contains advisory data that an application client may use todetermine the time in seconds that the device server requires to complete an extended self-test when the deviceserver is not interrupted by subsequent commands and no errors occur during execution of the self-test. The applicationclient should expect this time to increase significantly if other commands are sent to the logical unit while aself-test is in progress or if errors occur during execution of the self-test. Device servers supporting SELF-TESTCODE field values other than 000b for the SEND DIAGNOSTIC command (see 7.23), shall support the EXTENDEDSELF-TEST COMPLETION TIME field.8.3.7 Disconnect-reconnect pageThe disconnect-reconnect page (see table 159) provides the application client the means to tune the performanceof the service delivery subsystem. The name for this mode page, disconnect-reconnect, comes from the SCSIparallel bus. A SCSI device based on any of the protocols may use appropriate parameters in thedisconnect-reconnect mode page. The parameters appropriate to each protocol and their interpretation for thatprotocol may be specified in the individual protocol documents.Table 159 — Disconnect-reconnect pageBitByte7 6 5 4 3 2 1 00 PS Reserved PAGE CODE (02h)1 PAGE LENGTH (0Eh)2 BUFFER FULL RATIO3 BUFFER EMPTY RATIO4 (MSB)BUS INACTIVITY LIMIT5 (LSB)6 (MSB)DISCONNECT TIME LIMIT7 (LSB)8 (MSB)CONNECT TIME LIMIT9 (LSB)10 (MSB)MAXIMUM BURST SIZE11 (LSB)12 EMDP FAIR ARBITRATION DIMM DTDC13 Reserved14 (MSB)FIRST BURST SIZE15 (LSB)The device server communicates the parameter values in this mode page to the service delivery subsystem.Similarly the application client may also communicate parameter values to the service delivery subsystem. Thiscommunication is internal to the initiator or target device and is outside the scope of SCSI.dpANS SCSI Primary Commands - 2 (SPC-2) 199
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:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167: T10/1236-D Revision 20 18 July 2001
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

Create successful ePaper yourself

Delete template?

Save as template?