Fujitsu MAN3735 Manuale Utente
C141-E124-01EN
3 - 65
3.1.19
PERSISTENT RESERVE OUT (5F)
Bit
Byte
Byte
7
6
5
4
3
2
1
0
0
X'5F'
1
0
0
0
Service Action
2
Scope
Type
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
Parameter List Length (MSB)
8
Parameter List Length (LSB)
9
0
0
0
0
0
0
Flag
Link
This command is used to request service actions that reserve a logical unit or element for the
exclusive or shared use of a particular initiator. The command uses other service actions to manage
and remove such reservations. The command shall be used in conjunction with the PERSISTENT
RESERVE IN command and shall not be used with the RESERVE and RELEASE commands.
exclusive or shared use of a particular initiator. The command uses other service actions to manage
and remove such reservations. The command shall be used in conjunction with the PERSISTENT
RESERVE IN command and shall not be used with the RESERVE and RELEASE commands.
Initiators performing PERSISTENT RESERVE OUT service actions are identified by a
reservation key provided by the application client. An application client may use the
PERSISTENT RESERVE IN command to identify which initiators are holding a persistent
reservation and use the PERSISTENT RESERVE OUT command to preempt that reservation if
required.
reservation key provided by the application client. An application client may use the
PERSISTENT RESERVE IN command to identify which initiators are holding a persistent
reservation and use the PERSISTENT RESERVE OUT command to preempt that reservation if
required.
If a PERSISTENT RESERVE OUT command is attempted, but there are insufficient device server
resources to complete the operation, the device server shall return a CHECK CONDITION status
(ILLEGAL REQUEST [=5] / Insufficient registration resources [=55-04]).
resources to complete the operation, the device server shall return a CHECK CONDITION status
(ILLEGAL REQUEST [=5] / Insufficient registration resources [=55-04]).
The PERSISTENT RESERVE OUT command contains fields that specify a persistent reservation
service action, the intended scope of the persistent reservation, and the restrictions caused by the
persistent reservation. The "Type" and "Scope" fields are defined in 3.1.18.3.1 and 3.1.18.3.2. If a
"Scope" field specifies a scope that is not implemented, the device server shall return a CHECK
CONDITION status (ILLEGAL REQUEST [=5] / Invalid field in CDB).
service action, the intended scope of the persistent reservation, and the restrictions caused by the
persistent reservation. The "Type" and "Scope" fields are defined in 3.1.18.3.1 and 3.1.18.3.2. If a
"Scope" field specifies a scope that is not implemented, the device server shall return a CHECK
CONDITION status (ILLEGAL REQUEST [=5] / Invalid field in CDB).
Fields contained in the PERSISTENT RESERVE OUT parameter list specify the information
required to perform a particular persistent reservation Service action.
required to perform a particular persistent reservation Service action.
The parameter list shall be 24 bytes in length and the "Parameter List Length" field shall contain
24 (18h). If the parameter list length is not 24, the device server shall return a CHECK
CONDITION status (ILLEGAL REQUEST [=5] / Parameter list length error [=1A-00]).
24 (18h). If the parameter list length is not 24, the device server shall return a CHECK
CONDITION status (ILLEGAL REQUEST [=5] / Parameter list length error [=1A-00]).