The application client should issue a RECEIVE COPY RESULTS command with FAILED SEGMENT
DETAILS service action immediately following failure of the EXTENDED COPY command to
insure that the information is not discarded by the copy manager. The copy manager
will discard the failed segment details:
1. After all failed segment details held for a specific EXTENDED COPY command have
been successfully transferred to the application client;
2. When a RECEIVE COPY RESULTS command with FAILED SEGMENT DETAILS service action has
been received from the same initiator with a matching list identifier, with the
Allocation Length field set to 0;
3. When another EXTENDED COPY command is received from the same initiator using
the same list identifier;
4. When the copy manager detects a hard reset condition; or
5. When the copy manager requires the resources used to preserve the data.
The Available Data field will contain the number of bytes of failed segment details
available for delivery to the application client. If the amount of failed segment details
data sent to the application client is reduced due to insufficient allocation length, the
Available Data field will not be altered and the failed segment details will not be
discarded. If no failed segment details data is available for the specified list identifier
then the Available Data field will be set to zero and no data beyond the Available Data
field will be returned.
The Copy Command Status field contains the SCSI status value that was returned for
the EXTENDED COPY command identified by the List Identifier field in the CDB.
The Sense Data Length field indicates how many bytes of sense data are present in the
Sense Data field.
The Sense Data field contains a copy of the sense data that the copy manager prepared
as part of terminating the EXTENDED COPY command identified by the list identifier with a
CHECK CONDITION status.
Note:
Specific uses of the reserved bytes 4 to 55 are under discussion for
SPC-3. Possible uses include indicating the number of successful,
failed, and indeterminate transfer operations to source and
destination copy targets device. The fields still being discussed are
not good candidates for inclusion in a separate service action
because they need to be created and discarded under the same
circumstances as the fields already defined. The inclusion of an
indefinite length sense data field is a step of significant value.
Appendix C. Receive Copy Results—84h
201
Need help?
Do you have a question about the Spectra 12K and is the answer not in the manual?