SCSI Primary Commands - 2.pdf

More documents

Recommendations

Info

T10/1236-D Revision 20 18 July 2001The pseudocode in A.5.1 through A.5.3 assumes that ACA is implemented and requested in the CDB control byte.If this is not the case, the implementation may be based on the SCSI-2 TIB 1 or other applicable standards.A.5.1 Pseudocode 1IF the threshold condition as defined by the TMC field is met:1) IF there is an active task1) Complete the active task2) If an ACA condition exists wait for it to be clearedEND2) Issue a unit attention condition to all initiators that have set the RLEC bit to one3) IF the unit attention condition is ignored1) Continue normal operations until the threshold condition is met againENDA.5.2 Pseudocode 2IF a log counter reaches its maximum value:1) Set DU to 12) IF there is no active task1) Wait until there is an active taskEND3) Complete the active task4) IF no ACA condition exists1) Create an ACA condition with a sense key of RECOVERED ERROR and additional sense code ofLOG EXCEPTION, COUNT AT MAXIMUMEND5) Wait for the ACA condition to be cleared6) IF the cause of the counter reaching maximum is not cleared by the application client1) Do not create an ACA condition and do not increment the counterENDENDA.5.3 Pseudocode 3IF the log of parameters is full:1) Place the new log parameter code value into the lowest parameter code value position (wrap-around theparameter codes)2) IF there is no active task1) Wait until there is an active taskEND3) Complete the active task4) IF no ACA condition exists1) Create an ACA condition with a sense key of RECOVERED ERROR and additional sense code ofLOG EXCEPTION, LIST CODES EXHAUSTEDEND5) Wait for the ACA condition to be cleared6) IF the cause of the log of parameters filling is not cleared by the application client1) Create an ACA condition every time an entry is placed into the log of parametersENDEND1. TIB for IT - Procedures for Logging Operations (X3-131-1994/TIB-1).228 dpANS SCSI Primary Commands - 2 (SPC-2)
18 July 2001 T10/1236-D Revision 20B.1 SBC commandsAnnex B(Informative)Commands allowed in the presence of various reservationsThis subclause should be placed into the model clause of the next version of the SBC standard when, and if, a newversion of that standard is published. It should replace all the individual command descriptions of how reservationswork.Reservation restrictions are placed on commands as a result of access qualifiers associated with the type of reservation.The details of which commands are allowed under what types of reservations are described in table B.1,table B.2 and table B.3. For the reservation restrictions placed on commands for the reserve/release managementmethod see table B.1, table B.2 and table B.3 column [A]. For the reservation restrictions placed on commands forthe persistent reservations management method, see the columns under [B] in table B.1, table B.2 and table B.3.In table B.1, table B.2 and table B.3 the following key words are used:allowed: Commands issued by initiators not holding the reservation or by initiators not registered when a registrantsonly persistent reservation is present should complete normally.conflict: Commands issued by initiators not holding the reservation or by initiators not registered when a registrantsonly persistent reservation is present shall not be performed and the device server shall terminate thecommand with a RESERVATION CONFLICT status.Commands from initiators holding a reservation should complete normally. The behavior of commands from registeredinitiators when a registrants only persistent reservation is present is specified in table B.1, table B.2 and tableB.3.A command that does not explicitly write the medium shall be checked for reservation conflicts before thecommand enters the current task state for the first time. Once the command has entered the current task state, itshall not be terminated with a RESERVATION CONFLICT due to a subsequent reservation.A command that explicitly writes the medium shall be checked for reservation conflicts before the device servermodifies the medium or cache as a result of the command. Once the command has modified the medium, it shallnot be terminated with a RESERVATION CONFLICT due to a subsequent reservation.For each command, this standard, SPC-2, or a related command standard defines the conditions that result inRESERVATION CONFLICT. Depending on the particular command standard the conditions are defined in thatstandard’s device model clause or in the subclauses that define the specific commands. An annex in SPC-2contains the RESERVATION CONFLICT information for some of the command sets.dpANS SCSI Primary Commands - 2 (SPC-2) 229
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:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197: T10/1236-D Revision 20 18 July 2001
show all

SCSI Primary Commands - 2.pdf

Create successful ePaper yourself

Delete template?

Save as template?