SCSI Primary Commands - 2.pdf

More documents

Recommendations

Info

T10/1236-D Revision 20 18 July 20017.14.3 RECEIVE DATA service actionIf the copy manager supports those segment descriptors require data to be held for transfer to the applicationclient, then the RECEIVE DATA service action causes the copy manager to return the held data using the formatshown in table 90. If a copy manager supports any of the segment descriptor type codes that require data to beheld for the application client (see 7.2.5), then it shall also support the RECEIVE COPY RESULTS command withRECEIVE DATA service action.If the LIST IDENTIFIER field of a RECEIVE COPY RESULTS CDB identifies an EXTENDED COPY command that stillis being processed by the copy manager, the command shall be terminated with a CHECK CONDITION status.The sense key shall be set to ILLEGAL REQUEST and the additional sense code shall be set to INVALID FIELD INCDB.Table 90 — Parameter data for the RECEIVE DATA service actionBitByte7 6 5 4 3 2 1 00 (MSB)AVAILABLE DATA (n-4)3 (LSB)4HELD DATAnFollowing completion of an EXTENDED COPY command, the copy manager shall preserve all data returned by aRECIEVE DATA service action for a vendor specific period of time. The application client should issue a RECEIVECOPY RESULTS command with RECEIVE DATA service action as soon as practical following completion of theEXTENDED COPY command to insure that the data is not discarded by the copy manager. The copy managershall discard the buffered inline data:a) after all data held for a specific EXTENDED COPY command has been successfully transferred to theapplication client;b) when a RECIEVE COPY RESULTS command with RECEIVE DATA service action has been received fromthe same initiator with a matching list identifier, with the ALLOCATION LENGTH field set to zero;c) when another EXTENDED COPY command is received from the same initiator and the list identifiermatches the list identifier associated with the data preserved for RECEIVE DATA service action;d) when the copy manager detects a hard reset condition; ore) when the copy manager requires the resources used to preserve the data.The AVAILABLE DATA field shall contain the number of bytes of held data available for delivery to the applicationclient. If the amount of held data sent to the application client is reduced due to insufficient allocation length, theAVAILABLE DATA field shall not be altered and the held data shall not be discarded.The HELD DATA field contains the data held by the copy manager for delivery to the application client as prescribedby several segment descriptor type codes. Unless the copy manager’s held data limit (see 7.14.4) is exceeded, thefirst byte held in response to the first segment descriptor in the EXTENDED COPY parameter list prescribing theholding of data (called the oldest byte held) is returned in byte 4. The last byte held in response to the last segmentdescriptor in the EXTENDED COPY parameter list prescribing the holding of data (called the newest byte held) isreturned in byte n.122 dpANS SCSI Primary Commands - 2 (SPC-2)
18 July 2001 T10/1236-D Revision 207.14.4 OPERATING PARAMETERS service actionIn response to the OPERATING PARAMETERS service action, the copy manager shall return its operatingparameter information in the format shown in table 91. If a device server supports the EXTENDED COPYcommand (see 7.2), then it shall also support the RECEIVE COPY RESULTS command with OPERATINGPARAMETERS service action.Table 91 — Parameter data for the OPERATING PARAMETERS service actionBitByte7 6 5 4 3 2 1 00 (MSB)AVAILABLE DATA (n-4)3 (LSB)4Reserved78 (MSB)MAXIMUM TARGET DESCRIPTOR COUNT9 (LSB)10 (MSB)MAXIMUM SEGMENT DESCRIPTOR COUNT11 (LSB)12 (MSB)MAXIMUM DESCRIPTOR LIST LENGTH15 (LSB)16 (MSB)MAXIMUM SEGMENT LENGTH19 (LSB)20 (MSB)MAXIMUM INLINE DATA LENGTH23 (LSB)24 (MSB)HELD DATA LIMIT27 (LSB)28 (MSB)MAXIMUM STREAM DEVICE TRANSFER SIZE31 (LSB)32Reserved3536 MAXIMUM CONCURRENT COPIES37 DATA SEGMENT GRANULARITY (log 2)38 INLINE DATA GRANULARITY (log 2)39 HELD DATA GRANULARITY (log 2)4042Reserved43 IMPLEMENTED DESCRIPTOR LIST LENGTH (n-43)44nList of implemented descriptor type codes (ordered)dpANS SCSI Primary Commands - 2 (SPC-2) 123
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: T10/1236-D Revision 20 18 July 2001
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
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?