Datasheet

Command Specifications
4-84 C141-C008
• Reserve right and the third party reserve function
Remark
In order to clarify the jurisdiction related to reserve and release, the term
"Reserve Right" is used in this manual.
TARG
#0
INIT
#A
TARG/INIT
#1
FC interface
INIT
#B
Figure 4.2 Reserve right and the third party reserve function
1. If INIT #A issues a RESERVE command which does not specify the third
party reserve function to TARG #0, TARG #0 enters the reserved state from
INIT #A and INIT #A has the reserve right with respect to TARG #0. In this
case,
− INIT #A has an exclusive monopoly over TARG #0.
− Any commands issued to TARG #0 by any other FC device (INIT #B,
TARG/INIT #1) are rejected with a RESERVATION CONFLICT status,
with the exception of an INQUIRY, REQUEST SENSE or RELEASE
command. The RELEASE command is terminated normally, but TARG
#0's reserve state is not influenced by it.
2. If INIT #A issues a RESERVE command which specifies the third party
reserve function ("3rd Pty Dev ID" = TARG/INIT#1), TARG #0 becomes
reserved from TARG/INIT #1, but INIT #A has the reserve right. In this
case,
− TARG/INIT #1 has an exclusive monopoly of TARG #0. However, if
TARG/INIT#1 issues a RESERVE command, that command is rejected
with a RESERVATION CONFLICT status. Also, a RELEASE
command is terminated normally, but it has no influence on the TARG
#0 reserve right.
− INIT #A can issue INQUIRY, REQUEST SENSE, RELEASE and
RESERVE commands to TARG #0, but other commands are rejected
with a RESERVATION CONFLICT status. A RELEASE or RELEASE
EXTENDED command issued by INIT #A releases TARG #0's reserved
state. Also, a RESERVE or RESERVE EXTENDED command changes
the reserve state of TARG #0.