Fujitsu MBC2073RC Manual Do Utilizador
Command Specifications
194
C141-C013
CHAPTER 4
Command Specifications
4.1 Control/Sense Commands
4.1.17 PERSISTENT RESERVE IN (5E)
Bit
Byte
7
6
5
4
3
2
1
0
0
X'5E'
1
0
0
0
Service Action
2
0
0
0
0
0
0
0
0
3
0
0
0
0
0
0
0
0
4
0
0
0
0
0
0
0
0
5
0
0
0
0
0
0
0
0
6
0
0
0
0
0
0
0
0
7
Allocation Length (MSB)
8
Allocation Length (LSB)
9
0
0
0
0
0
0
0
0
The PERSISTENT RESERVE IN command is used to obtain information on the
reserve conditions that are valid within a target and information concerning a
Reservation Key. This command is used in combination with the PERSISTENT
RESERVE OUT command (see Section 4.1.18).
reserve conditions that are valid within a target and information concerning a
Reservation Key. This command is used in combination with the PERSISTENT
RESERVE OUT command (see Section 4.1.18).
If the reserved state implemented with the RESERVE command is valid in a
target when the target receives this command, the command is rejected with the
report of the RESERVATION CONFLICT status.
target when the target receives this command, the command is rejected with the
report of the RESERVATION CONFLICT status.
When the reserved state implemented with the PERSISTENT RESERVATION
command is valid, this command is always executed normally.
command is valid, this command is always executed normally.
The length of the PERSISTENT RESERVE IN parameter data that can be
reported with this command is indicated in the parameter data. When a byte count
that is too small to transfer an entire parameter list is specified in the "Allocation
Length" field of the CDB, the data bytes starting at byte 0 of the parameter data
and numbering as many as the specified byte count are transferred (this is not
considered to be an error). If it is necessary to read the rest of the parameter data,
an INIT should reissue the PERSISTENT RESERVE IN command by specifying
a byte count that is long enough to cover the entire list in the "Allocation Length"
field.
reported with this command is indicated in the parameter data. When a byte count
that is too small to transfer an entire parameter list is specified in the "Allocation
Length" field of the CDB, the data bytes starting at byte 0 of the parameter data
and numbering as many as the specified byte count are transferred (this is not
considered to be an error). If it is necessary to read the rest of the parameter data,
an INIT should reissue the PERSISTENT RESERVE IN command by specifying
a byte count that is long enough to cover the entire list in the "Allocation Length"
field.