Operating instructions
SEPTEMBER 2005 MAGNUM 1X7 LTO AUTOLOADER
20-5
COMMAND STATUS
Byte 03 – Third Party Device ID
This field indicates the SCSI ID of the device for which the initiator is making
the third-party reservation. The autoloader ignores this field if the initiator is
not requesting a third-party reservation (the 3rdPty bit is set to 0).
Parameter List Length – Byte 07 and 08
Long ID and element reservation are not supported for this command, so
value for this field must always be zero.
20.3 COMMAND STATUS
The autoloader returns a status byte after processing the RESERVE command.
This section describes when each type of status byte might be returned.
Good
The autoloader returns Good status when it is able to process the command
without errors.
Busy
The autoloader returns Busy status when it is processing a command for a
different initiator or when it is in the process of aborting a motion command.
Reservation Conflict
The autoloader returns Reservation Conflict status when:
The autoloader is reserved by a different initiator.
An initiator attempts to reserve an element that is reserved by a different
initiator.
An initiator attempts to reserve an element it has already reserved under a
different Reservation Identification.
If an element address has already been reserved by another initiator, none of
the requested elements is reserved, Reservation Conflict (18h) status is
returned to the initiator, and the sense key is set to No Sense (0h).
Check Condition
The autoloader returns Check Condition status for the following reasons:
The message system is enabled and a message error occurs while the
autoloader is processing the command.
The autoloader detects an unrecoverable parity error while receiving either
the CDB or the element descriptor data.
The command is issued to an invalid LUN.
A Unit Attention condition is pending for the initiator.