User Manual

SCSI Commands Reference Manual, Rev. J 205
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4)
INC_512 (512 Increment)
0 0An INC_512 bit set to zero specifies that the ALLOCATION LENGTH field (see 2.2.6) expresses the number of bytes to be transferred.
1 1A 512 increment (INC_512) bit set to one specifies that the ALLOCATION LENGTH field (see 2.2.6) expresses the maximum number of
bytes available to receive data in increments of 512 bytes (e.g., a value of one means 512 bytes, two means 1,024 bytes, etc.). Pad bytes
may or may not be appended to meet this length. Pad bytes shall have a value of 00h.
Indications of data overrun or underrun and the mechanism, if any, for processing retries depend on the protocol specified by
the SECURITY PROTOCOL field (see table 174).
Any association between a previous SECURITY PROTOCOL OUT command and the data transferred by a SECURITY PROTOCOL IN
command depends on the protocol specified by the SECURITY PROTOCOL field (see table 175). If the device server has no data to
transfer (e.g., the results for any previous SECURITY PROTOCOL OUT commands are not yet available), the device server may
transfer data indicating it has no other data to transfer.
The format of the data transferred depends on the protocol specified by the SECURITY PROTOCOL field (see table 174).
The device server shall retain data resulting from a SECURITY PROTOCOL OUT command, if any, until one of the following events
is processed:
a) Transfer of the data via a SECURITY PROTOCOL IN command from the same I_T_L nexus as defined by the protocol specified by the
SECURITY PROTOCOL field;
b) Logical unit reset (See SAM-5); or
c) I_T nexus loss (See SAM-5) associated with the I_T nexus that sent the SECURITY PROTOCOL OUT command.
If the data is lost due to one of these events the application client may send a new SECURITY PROTOCOL OUT command to retry
the operation.