Spectra Logic Spectra 12K, Spectra 20K, Spectra 64K User Manual
Gator Library
Developer Guide
• Spectra® 12K Library
®
• Spectra
• Spectra® 64K Library
20K Library
P.N. 90910850 Revision D
Notices
Notices
Except as expressly stated herein, Spectra Logic Corporation makes available the Gator architecture
(Spectra
without warranty of any kind, either expressed or implied, including but not limited to the implied
warranties of merchantability or fitness for a particular purpose. In no event will Spectra Logic be liable for
any loss of profits, loss of business, loss of use or data, interruption of business, or for indirect, special,
incidental or consequential damages of any kind, even if Spectra Logic has been advised of the possibility of
such damages arising from any defect or error.
Information furnished in this manual is believed to be accurate and reliable. However, no responsibility
is assumed by Spectra Logic for its use. Due to continuing research and development, Spectra Logic may
revise this publication from time to time without notice, and reserves the right to change any product
specification at any time without notice.
Some products or services mentioned in this manual are provided by companies other than Spectra
Logic. Inquiries about one or more of these products or services should be sent directly to the company
in question. This manual refers to the following brand or product names, registered trademarks, and
trademarks that are listed according to their respective owners. These trademarks may be registered in
this country, other countries, or both.
Gator Library Developer Guide
Copyright © 2003 Spectra Logic Corporation. All rights reserved.
®
12K, Spectra 20K, and Spectra 64K) libraries and associated documentation on an “as is” basis,
2
Notices
License Agreement
This program is copyrighted and licensed (not sold). If you are not willing to be bound by the terms of this
License Agreement, you should promptly return the package, and you will receive a refund of your money.
This License Agreement represents the entire agreement concerning the program between you and Spectra
Logic Corporation (referred to as “Licensor”), and it supersedes any prior proposal, representation, or
understanding between the parties.
• License Grant. Licensor hereby grants to you, and you accept, a nonexclusive license to use the
Program Diskettes and the TAOS computer programs contained therein in machine-readable, object
code form only (collectively referred to as the “Software”), and the accompanying User
Documentation, only as authorized in this License Agreement. The Software may be used only in a
local area network or other network. You agree that you will not assign, sublicense, transfer, pledge,
lease, rent, or share your rights under this License Agreement. You agree that you may not reverse
assemble, reverse compile, or otherwise translate the Software.
Upon loading the Software into your computer, you may retain the Program Diskettes for backup
purposes. In addition, you may make one copy of the Software on a second set of diskettes (or on
cassette tape) for the purpose of backup in the event the Program Diskettes are damaged or
destroyed. You may make one copy of the User's Manual for backup purposes. Any such copies of the
Software or the User's Manual will include Licensor's copyright and other proprietary notices. Except
as authorized under this paragraph, no copies of the Program or any portions thereof may be made by
you or any person under your authority or control.
• Licensor’s Rights. You acknowledge and agree that the Software and the User's Manual are proprietary
products of Licensor protected under U.S. copyright law. You further acknowledge and agree that all
right, title, and interest in and to the Program, including associated intellectual property rights, are
and will remain with Licensor. This License Agreement does not convey to you an interest in or to the
Program, but only a limited right of use revocable in accordance with the terms of this License
Agreement.
• License Fees. The license fees paid by you are paid in consideration of the licenses granted under this
License Agreement.
• Term. This License Agreement is effective upon your opening of this package and will continue until
terminated. You may terminate this License Agreement at any time by returning the Program and all
copies thereof and extracts therefrom to Licensor. Licensor may terminate this License Agreement
upon the breach by you of any term hereof. Upon such termination by Licensor, you agree to return to
Licensor the Program and all copies and portions thereof.
• Limited Warranty. Licensor warrants, for your benefit alone, for a period of 90 days from the date of
commencement of this License Agreement (referred to as the “Warranty Period”) that the Program
Diskettes in which the Software is contained are free from defects in material and workmanship.
Licensor further warrants, for your benefit alone, that during the Warranty Period the Program will
operate substantially in accordance with the functional specifications in the User's Manual. If during
the Warranty Period, a defect in the Program appears, you may return the Program to Licensor for
either replacement or, if so elected by Licensor, refund of amounts paid by you under this License
Agreement. You agree that the foregoing constitutes your sole and exclusive remedy for breach by
Licensor of any warranties made under this Agreement. EXCEPT FOR THE WARRANTIES SET FORTH
ABOVE, THE PROGRAM, AND THE SOFTWARE CONTAINED THEREIN, ARE LICENSED “AS IS,” AND
LICENSOR DISCLAIMS ANY AND ALL OTHER WARRANTIES, WHETHER EXPRESS OR IMPLIED,
INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
• Limitation of Liability. Licensor's cumulative liability to you or any other party for any loss or damages
resulting from any claims, demands, or actions arising out of or relating to this Agreement will not
exceed the license fee paid to Licensor for the use of the Program. In no event will Licensor be liable
for any indirect, incidental, consequential, special, or exemplary damages or lost profits, even if
Licensor has been advised of the possibility of such damages. SOME STATES DO NOT ALLOW THE
LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO
THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU.
• Governing Law. This License Agreement will be construed and governed in accordance with the laws of
the State of Colorado.
• Costs of Litigation. If either party brings any action relating to this License Agreement against the
other, the prevailing party will be entitled to recover, in addition to any other relief granted,
reasonable attorney fees and expenses of litigation.
• Severability. Should any court of competent jurisdiction declare any term of this License Agreement
void or unenforceable, such declaration will have no effect on the remaining terms hereof.
3
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
List of Tables 8
Chapter 1. Introduction 16
About Gator® Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 2. SCSI Basics 18
SCSI-2 Interface Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
SCSI Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
SCSI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Chapter 3. Initialize Element Status—07h 31
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Command Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Chapter 4. Initialize Element Status With Range—E7h 33
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4
Conte nts
Chapter 5. Inquiry—12h 34
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Command Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Chapter 6. Mode Select—15h 42
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Chapter 7. Mode Sense—1Ah 45
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Command Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 8. Move Medium—A5h 56
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Chapter 9. Position To Element—2Bh 58
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Chapter 10. Prevent/Allow Medium Removal—1Eh 59
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Chapter 11. Read Element Status—B8h 60
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Command Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Element Descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5
Conte nts
Chapter 12. Receive Diagnostic Results—1Ch 76
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Supported Diagnostics Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Element Status Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Chapter 13. Release—17h 89
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Chapter 14. Request Sense—03h 91
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Command Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Chapter 15. Reserve—16h 94
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Chapter 16. Send Diagnostic—1Dh 97
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Command Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Parameter Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Supported Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
Chapter 17. Test Unit Ready—00h 104
Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Command Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
6
Conte nts
Chapter 18. Error Reporting 105
Sense Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106
Sense Codes and Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
Appendix A. Extended Copy—83h—143r1 Specifications 120
Fibre Channel Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Mode Sense Page for Extended Copy Command . . . . . . . . . . . . . . . . . . . . . . . . . .149
Sense Key Specific Field Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Receive Copy Results Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154
Appendix B. Extended Copy—83h—SPC2 Specifications 159
Fibre Channel Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
Appendix C. Receive Copy Results—84h 196
Fibre Channel Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196
Failed Segment Details Service Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200
Appendix D. Report LUNs—A0 202
Fibre Channel Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202
Index 206
7
List of Tables
Chapter 1. Introduction 16
Chapter 2. SCSI Basics 18
Table 2-1: SCSI Bus Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Table 2-2: Supported Message Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 2-3: Identify Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 2-4: Six-Byte CDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 2-5: 10-Byte CDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 2-6: 12-Byte Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 2-7: 16-Byte Command Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 2-8: Operation Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 2-9: Group Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 2-10: Control Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 2-11: Status Byte Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table 2-12: Status Byte Code Field Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 3. Initialize Element Status—07h 31
Table 3-1: Initialize Element Status Command–07h . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 4. Initialize Element Status With Range—E7h 33
Table 4-1: Initialize Element Status With Range Command–E7h . . . . . . . . . . . . . . . 33
8
List of Tables
Chapter 5. Inquiry—12h 34
Table 5-1: Inquiry Command–12h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 5-2: Inquiry Command Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Table 5-3: Standard Inquiry Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Table 5-4: Standard Inquiry Data Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 5-5: Supported Pages Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Table 5-6: Serial Number Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Table 5-7: Serial Number Page Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Table 5-8: Library Identification Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Table 5-9: Serial Number Page Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Chapter 6. Mode Select—15h 42
Table 6-1: Mode Select Command–15h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 6-2: Mode Select Command Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Chapter 7. Mode Sense—1Ah 45
Table 7-1: Mode Sense Command–1Ah . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Table 7-2: Mode Sense Command Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Table 7-3: Parameter List Header Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Table 7-4: Tape Alert Page Parameters–1Ch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Table 7-5: Tape Alert Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Table 7-6: Element Address Assignments Page–1Dh . . . . . . . . . . . . . . . . . . . . . . . 51
Table 7-7: Transport Geometry Parameter Page–1Eh . . . . . . . . . . . . . . . . . . . . . . . 52
Table 7-8: Device Capabilities Fields Format–1Fh . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 7-9: Vendor-Specific Parameters–00h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Chapter 8. Move Medium—A5h 56
Table 8-1: Move Medium Command–A5h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Table 8-2: Move Medium Command Field Values . . . . . . . . . . . . . . . . . . . . . . . . . 57
9
List of Tables
Chapter 9. Position To Element—2Bh 58
Table 9-1: Position To Element Command–2Bh . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Chapter 10. Prevent/Allow Medium Removal—1Eh 59
Table 10-1: Prevent/Allow Medium Removal Command–1Eh . . . . . . . . . . . . . . . . . 59
Table 10-2: Prevent/Allow Medium Removal Command Values . . . . . . . . . . . . . . . 59
Chapter 11. Read Element Status—B8h 60
Table 11-1: Read Element Status Command–B8h . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Table 11-2: Read Element Status Command Values . . . . . . . . . . . . . . . . . . . . . . . . 61
Table 11-3: Element Status Data Header Format . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Table 11-4: Element Status Data Header Field Values . . . . . . . . . . . . . . . . . . . . . . 63
Table 11-5: Element Status Page Header Format . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Table 11-6: Element Status Page Header Field Values . . . . . . . . . . . . . . . . . . . . . . 65
Table 11-7: Medium Transport Element Descriptor (Tape Picker) . . . . . . . . . . . . . 66
Table 11-8: Medium Transport Element Descriptor Fields . . . . . . . . . . . . . . . . . . . 67
Table 11-9: Storage Element Descriptor (Magazine Slots) . . . . . . . . . . . . . . . . . . . 68
Table 11-10: Storage Element Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Table 11-11: Data Transfer Element Descriptor (Tape Drive) . . . . . . . . . . . . . . . . . 70
Table 11-12: Data Transfer Element Descriptor Fields . . . . . . . . . . . . . . . . . . . . . . 71
Table 11-13: Entry/Exit Element Descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Table 11-14: Entry/Exit Element Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
10
List of Tables
Chapter 12. Receive Diagnostic Results—1Ch 76
Table 12-1: Receive Diagnostic Results Command–1Ch . . . . . . . . . . . . . . . . . . . . . 76
Table 12-2: Receive Diagnostic Results Command Values . . . . . . . . . . . . . . . . . . . 77
Table 12-3: Supported Diagnostics Page Format–00h . . . . . . . . . . . . . . . . . . . . . . 78
Table 12-4: Enclosure Configuration Page Format–01h . . . . . . . . . . . . . . . . . . . . . 79
Table 12-5: Enclosure Configuration Page Field Values . . . . . . . . . . . . . . . . . . . . . 80
Table 12-6: Element Type Descriptor Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Table 12-7: Element Type Descriptor Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Table 12-8: Enclosure Status Page–02h (Spectra 12K and Spectra 20K Libraries) . . 82
Table 12-9: Enclosure Status Page–02h (Spectra 64K Libraries) . . . . . . . . . . . . . . . 83
Table 12-10: Enclosure Status Page Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Table 12-11: Element Status Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Table 12-12: Supported Status Codes for All Element Types . . . . . . . . . . . . . . . . . 86
Table 12-13: Power Supply Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Table 12-14: Power Supply Status Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Table 12-15: Fan Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Table 12-16: Fan Status Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Table 12-17: Temperature Sensor Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Table 12-19: Door Lock Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Table 12-20: Door Lock Status Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Table 12-18: Temperature Sensor Status Values . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Chapter 13. Release—17h 89
Table 13-1: Release Command–17h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Table 13-2: Release Command Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Chapter 14. Request Sense—03h 91
Table 14-1: Request Sense Command–03h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 14-2: Sense Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Table 14-3: Sense Data Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
11
List of Tables
Chapter 15. Reserve—16h 94
Table 15-1: Reserve Command–16h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Table 15-2: Reserve Command Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Table 15-3: Element List Descriptor Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Chapter 16. Send Diagnostic—1Dh 97
Table 16-1: Send Diagnostic Command–1Dh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table 16-2: Send Diagnostic Command Field Values . . . . . . . . . . . . . . . . . . . . . . . 98
Table 16-3: Diagnostics Parameter List Header Format . . . . . . . . . . . . . . . . . . . . . 99
Table 16-4: Diagnostics Parameter List Header Field Values . . . . . . . . . . . . . . . . . 99
Table 16-5: Supported Diagnostic Page Field Values . . . . . . . . . . . . . . . . . . . . . . .100
Table 16-6: Enclosure Services Control Page Format (for Spectra 12K and Spectra 20K
Libraries) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Table 16-7: Enclosure Services Control Page Format (for Spectra 64K Libraries) . . .102
Table 16-8: Enclosure Services Control Page Field Values . . . . . . . . . . . . . . . . . . .103
Chapter 17. Test Unit Ready—00h 104
Table 17-1: Test Unit Ready Command–00h . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Chapter 18. Error Reporting 105
Table 18-1: Sense Key Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106
Table 18-2: Library SCSI Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
12
List of Tables
Appendix A. Extended Copy—83h—143r1 Specifications 120
Table A-1: Extended Copy Command (143r1 Specifications) . . . . . . . . . . . . . . . . .121
Table A-2: Extended Copy Parameter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Table A-3: Extended Copy Descriptor Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Table A-4: Target Descriptor Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Table A-5: Address Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Table A-6: World Wide Name Target Descriptor Format . . . . . . . . . . . . . . . . . . . .128
Table A-7: N_PORT D_ID Target Descriptor Format . . . . . . . . . . . . . . . . . . . . . . .129
Table A-8: World Wide Name Target Descriptor Format . . . . . . . . . . . . . . . . . . . .130
Table A-9: SCSI B_T_L Target Descriptor Format . . . . . . . . . . . . . . . . . . . . . . . . . .132
Table A-10: Device-Specific Field - Device Type 00h . . . . . . . . . . . . . . . . . . . . . . .133
Table A-11: Device-Specific Field - Device Type 01h . . . . . . . . . . . . . . . . . . . . . . .133
Table A-12: Tape Transfer Lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
Table A-13: Segment Descriptor Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
Table A-14: PAD Bit and CAT Bit Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
Table A-15: Segment Descriptor for Codes 00h, 01h, 0Bh, and 0Ch . . . . . . . . . . . .137
Table A-16: Segment Descriptor for Codes 02h and 0Dh . . . . . . . . . . . . . . . . . . . .139
Table A-17: Segment Descriptor for Codes 03h and 0Eh . . . . . . . . . . . . . . . . . . . .140
Table A-18: Segment Descriptor for Code 04h . . . . . . . . . . . . . . . . . . . . . . . . . . . .142
Table A-19: Segment Descriptor for Code 05h . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
Table A-20: Segment Descriptor for Codes 06h and 0Fh . . . . . . . . . . . . . . . . . . . .145
Table A-21: Segment Descriptor for Code 07h . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
Table A-22: Segment Descriptor for Code 10h . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
Table A-23: Segment Descriptor for Code 11h . . . . . . . . . . . . . . . . . . . . . . . . . . . .148
Table A-24: Segment Descriptor for Code 12h . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
Table A-25: Mode Sense Page for Extended Copy Command . . . . . . . . . . . . . . . . .151
Table A-26: Segment Pointer Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Table A-27: Receive Copy Results Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154
Table A-28: Mode Field Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
Table A-29: Return Data Format - Mode 0 (Status) . . . . . . . . . . . . . . . . . . . . . . . . .157
Table A-30: Copy Manager Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
Table A-31: Transfer Count Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158
13
List of Tables
Appendix B. Extended Copy—83h—SPC2 Specifications 159
Table B-2: Extended Copy Parameter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
Table B-3: Extended Copy Descriptor Type Codes . . . . . . . . . . . . . . . . . . . . . . . .165
Table B-4: Target Descriptor Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
Table B-5: Device Type Specific Parameters in Target Descriptors . . . . . . . . . . . . .168
Table B-6: World Wide Name Target Descriptor Format . . . . . . . . . . . . . . . . . . . .168
Table B-7: N_Port Target Descriptor Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
Table B-8: N_Port with World Wide Name Checking Target Descriptor Format . . .170
Table B-9: Parallel Interface T_L Target Descriptor Format . . . . . . . . . . . . . . . . . .171
Table B-10: Identification Descriptor Target Descriptor Format . . . . . . . . . . . . . . .172
Table B-11: Device Type Specific Target Descriptor Parameters for Block Device Types
173
Table B-12: Device Type Specific Target Descriptor Parameters for Stream Device Types
174
Table B-13: Stream Device Transfer Lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
Table B-14: Device Type Specific Target Descriptor Parameters for Processor Device
Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
Table B-15: Segment Descriptor Header Format . . . . . . . . . . . . . . . . . . . . . . . . . .176
Table B-16: Descriptor Type Code Dependent Copy Manager Processing . . . . . . .177
Table B-17: PAD and CAT Bit Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179
Table B-18: Block Device To or From Stream Device Segment Descriptor . . . . . . .180
Table B-19: Block Device to Block Device Segment Descriptor . . . . . . . . . . . . . . .183
Table B-20: Stream Device to Stream Device Segment Descriptor . . . . . . . . . . . . .185
Table B-21: Inline Data to Stream Device Segment Descriptor . . . . . . . . . . . . . . . .186
Table B-22: Embedded Data to Stream Device Segment Descriptor . . . . . . . . . . . .188
Table B-23: Stream Device to Discard Segment Descriptor . . . . . . . . . . . . . . . . . .190
Table B-24: Verify Device Operation Segment Descriptor . . . . . . . . . . . . . . . . . . .191
Table B-25: Write Filemarks Operation Segment Descriptor . . . . . . . . . . . . . . . . .192
Table B-26: Space Operation Segment Descriptor . . . . . . . . . . . . . . . . . . . . . . . . .193
Table B-27: Locate Operation Segment Descriptor . . . . . . . . . . . . . . . . . . . . . . . .194
14
List of Tables
Appendix C. Receive Copy Results—84h 196
Table C-2: Receive Copy Results Service Action Codes . . . . . . . . . . . . . . . . . . . . .197
Table C-3: Parameter Data for the Copy Status Service Action . . . . . . . . . . . . . . . .198
Table C-4: Copy Status Status Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
Table C-5: Copy Status Transfer Count Units Values . . . . . . . . . . . . . . . . . . . . . . .199
Table C-6: Parameter Data for the Failed Segment Details Service Action . . . . . . . .200
Appendix D. Report LUNs—A0 202
Table D-2: Example Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204
Table D-3: Report LUNs Parameter Data Format . . . . . . . . . . . . . . . . . . . . . . . . . .204
15
1 Introduction
About Gator® Architecture
The Spectra 12K, Spectra 20K, and Spectra 64K libraries use the Gator architecture for
robotic tape libraries developed by Spectra Logic. Gator architecture in the Spectra 12K
library can be configured with up to 120 cartridges and eight tape drives. Gator
architecture in the Spectra 20K library can be configured with up to 200 cartridges and
eight tape drives. Gator architecture in the Spectra 64K can be configured with up to
640 cartridges and 32 tape drives. Gator architecture is based on hot-swappable
controller boards (S-QIP for HVD SCSI, L-QIP for LVD SCSI, F-QIP for Fibre Channel,
and G2 E-QIP for Gigabit Ethernet). The heart of Gator architecture is a
counterbalanced rack-and-pinion picker mechanism that can perform more than 600
tape handling operations per hour. Gator architecture includes Shared Library
Services™ (SLS) that allows users to allocate the library’s resources across various
platforms, software applications, and tape drives. These libraries can be configured as
one or more logical libraries; the Spectra 12K and 20K libraries have a maximum of
four logical libraries, and the Spectra 64K library has a maximum of 16 logical libraries.
Gator architecture also offers a color touchscreen user interface that provides access to
status information, configuration parameters, and diagnostics.
About This Guide
This Developer Guide describes the SCSI communications and commands supported
by Gator libraries. The SCSI communication is the same to each logical library within a
specific product.
Note: The appendices in this guide contain additional information on
select commands that are useful in Gator libraries with Fibre
Channel capabilities.
16
Chapter 1. Introduction
Related Publications
The following publications are also available from Spectra Logic:
• Spectra 12K Library User Guide (P.N. 90910889) describes the installation and
operation of the Spectra 12K library.
• Spectra 20K Library User Guide (P.N. 90920001) describes the installation and
operation of the Spectra 20K library.
• Spectra 64K Library User Guide (P.N. 90910851) describes the installation and
operation of the Spectra 64K library.
• Release Notes: Spectra 12K Library, Spectra 20K Library, Spectra 64K Library
(P.N. 90910852) provides last minute information about all of the gator architecture
libraries.
• Server Preparation Document for Spectra Logic Libraries provides specific operating
system information necessary for configuration. This document is available on
Spectra Logic’s Web site at http://www.spectralogic.com/support/index.cfm/
fuseaction/displaySupportDocs/.
Glossary
The following terms are defined for SCSI communication:
CDB Command descriptor block.
In Means coming from the target to the initiator, such as Data In.
Initiator Any device which initiates an exchange on the SCSI bus.
Library Refers to a logical library.
LUN Refers to a logical unit number.
Numbering A number followed by a lower case h is a hexadecimal number.
Out Means going from the initiator to the target, such as Message Out.
Target Any device that is the target of an exchange on the SCSI bus.
17
2 SCSI Basics
SCSI-2 Interface Basics
SCSI Bus Communications
Bus Phases The SCSI interface can be in any one of eight states or phases while
communications are occurring. The SCSI bus can only be in one phase at a time. The
SCSI bus phases and a brief description of each phase are listed in Table 2-1.
Table 2-1: SCSI Bus Phases
SCSI Bus Phase Description
Bus Free The SCSI bus is idle.
Arbitration One or more devices are requesting control of the bus.
Selection A target is selected and awaits communication from the initiator.
Reselection A target attempts to reconnect to an initiator, after having disconnected from the bus.
Command The device is waiting for or acting upon a command.
Data In/Out A data transfer is occurring.
Status The device returns its status information. The status is one of four possible conditions:
GOOD, CHECK CONDITION, BUSY, or RESERVATION CONFLICT.
Message In/Out Either the target or the initiator is sending a SCSI message to the other.
18
Chapter 2. SCSI Basics
Medium Changer Device Model
Gator libraries belong to the medium changer device model defined in the SCSI-2
standard. The function of a medium changer device is to automatically move units of
media (tapes) between storage locations (where media wait while not in use) and tape
drives (where data is written to or read from media). The medium changer device
model uses the term “element” to identify any place where a unit of media can reside,
such as in storage slots or a drive. Each element has a unique numerical address.
The four types of elements defined in the SCSI standard (and how they apply to Gator
libraries) are as follows:
• Medium transport element—robotic picker
• Storage element—cartridge slot
• Import/export element—the magazine that allows the user to insert or remove
tapes from the library
• Data transfer element—tape drive
Tracking Media Gator libraries use sensors continually to monitor whether their elements
are full or empty. On start-up, and whenever its door is opened and shut, the unit
takes a full inventory of its elements. The library always has an accurate inventory
available.
A volume tag may also be attached to the media for identification purposes. The
volume tag is typically a bar code label. The bar code scanner in the library reads the
bar code label on each media cartridge detected.
19
Chapter 2. SCSI Basics
SCSI Messages
The SCSI-2 messaging system defines the communication protocol for exchanges
between an initiator and a target. Table 2-2 on page 21 lists supported message codes
for Gator libraries configured with S-QIPs and L-QIPs.
Note: SCSI-2 requires devices to support the IDENTIFY message.
The following steps complete the transfer of data between the host computer (initiator)
and the library (target):
1. The initiator indicates that it is able to accommodate more than the COMMAND
COMPLETE message by asserting the following signals in this order: during the
selection phase, the initiator asserts the attention (ATN ) signal, then it asserts
select (SEL) and negates busy (BSY). This designates an ATTENTION condition and
completes the selection phase.
2. The target responds to the ATTENTION condition with the message MSG OUT PHASE,
indicating that the library can accommodate more messages.
3. If the initiator supports messages other than COMMAND COMPLETE, the first message
sent by the initiator after the selection phase is IDENTIFY.
4. If the disconnect privilege is enabled, and the target receives a valid command,
the target sends the DISCONNECT message to the initiator. After accepting most
commands, the target will disconnect; TEST UNIT READY, INQUIRY and REQUEST SENSE are
the exceptions.
Note: Gator libraries configured with S-QIP and L-QIP only work with a
host system that supports SCSI disconnects.
5. After completing a command, the target enters the RESELECTION phase. During this
phase, the target has both BSY and SEL signals asserted, and the data bus value is
the logical OR of the library’s SCSI ID bit and the initiator’s SCSI ID bit.
6. Following the RESELECTION phase, the target sends an IDENTIFY message followed by
the data transfer, if applicable, then a status byte and a COMMAND COMPLETE message
to the initiator.
7. The target enters the BUS FREE phase and awaits subsequent initiator selection.
20
Chapter 2. SCSI Basics
SCSI-2 Message Codes
Table 2-2 lists messages supported by Gator libraries configured for S-QIP and L-QIP.
Note: Gator libraries do not support any extended message, such as a
wide data transfer request, nor any vendor-specific messages. This
does not affect which messages the installed tape drives will
support, as those messages are transmitted directly to the drives.
The library will return the MESSAGE REJECT message in response to
unsupported messages.
Table 2-2: Supported Message Codes
Hex Values Description Direction
00h COMMAND COMPLETE Target to Initiator
04h DISCONNECT Bidirectional
06h ABORT Initiator to Target
07h MESSAGE REJECT Bidirectional
0Ch BUS DEVICE RESET Initiator to Target
80h to FFh IDENTIFY Bidirectional
Message Definitions
Abort The library terminates command execution, releases the SCSI bus, and returns to
the bus free phase.
Bus Device Reset After the initiator issues a DEVICE RESET message (0Ch) to the library, the
library resets its processing.
Reselection Phase Time-Out If a time-out is detected while the library is waiting for the
response from the initiator in the selection phase, the library immediately retries the
reselection. This retry operation continues until the reconnection request is honored or
the initiator issues a BUS DEVICE RESET command.
Command Complete (00h) The COMMAND COMPLETE message is sent from the library to an
initiator. This message indicates that the process is complete and a valid status has
been sent to the initiator. After successfully sending this message, the command
process is finished and the library goes to the bus free phase.
21
Chapter 2. SCSI Basics
Disconnect (04h) The library sends the DISCONNECT message to an initiator to request a pause
in the present I/O connection; the library releases the BSY signal and disconnects from
the SCSI bus. The disconnect implies that the library will later reconnect to the initiator
to complete the paused I/O process. The DISCONNECT message does not cause the initiator
to save the data pointers. The library is now in the bus free phase.
Abort Message (06h) The ABORT message is sent from an initiator to the library to stop the
current process. The ABORT message causes the library to terminate the current process
and enter the bus free phase.
Message Reject (07h) MESSAGE REJECT is sent from the initiator or the library to indicate that the
last message received was inappropriate, has not been implemented, or cannot be
honored at this time.
Bus Device Reset (0Ch) The BUS DEVICE RESET message is sent from the initiator to a library to
clear all I/O processes. This message forces the library to execute a soft reset. The
library releases the SCSI bus and creates a unit attention signal for all initiators.
Identify (80h-FFh) The IDENTIFY message is sent by either the initiator or the library to
establish the transfer parameters between two SCSI devices.
Table 2-3: Identify Message Format
Bits
Byte
Identify (bit 7) This bit is set to 1 to indicate an IDENTIFY message.
DiscPriv (bit 6) This bit is set to 1 to indicate that the initiator gives the library the
DISCONNECT privilege. If this bit is 0, the library is not allowed to disconnect during
transfers.
765 43210
identify DiscPriv LUNTAR reserved reserved LUNTRN
Note: For proper operation, the host computer must allow the library to
disconnect (DiscPriv=1). If the library is not allowed to disconnect
during an operation, it responds with a CHECK CONDITION status to any
command except TEST UNIT READY, INQUIRY, and REQUEST SENSE.
LUNTAR (bit 5) The logical unit target bit must be set to 0.
LUNTRN (bit 2-0) The library has one logical unit, which is 0. These bits must be set to 0.
22
Chapter 2. SCSI Basics
SCSI Commands
This section describes fundamental concepts and terms common to most SCSI
commands. It describes the SCSI command formats, command field definitions, and
command status bytes.
Descriptions of individual commands and instructions on how to use them with Gator
libraries are contained in their own chapters in this guide.
SCSI Command Formats
Here are the formats for 6-, 10-, 12-, and 16-byte SCSI command descriptor blocks
(CDBs) followed by the operation code format and the typical format for the control
byte. These commands are defined and implemented according to the ANSI SCSI-2
standard:
Note: These commands are only for the library. The SCSI commands
supported by the tape drives installed in the library are described
in the tape drive manual.
Table 2-4: Six-Byte CDB
Bits
Byte
00 Operation Code
01 Reserved (LUN) (MSB)
02
03 (LSB)
04
05 CONTROL
7 65432 1 0
LOGICAL BLOCK ADDRESS (if required)
TRANSFER LENGTH (if required)
PARAMETER LIST LENGTH (if required)
ALLOCATION LENGTH (if required)
23
Table 2-5: 10-Byte CDB
Bits
Chapter 2. SCSI Basics
Byte
00 Operation Code
01 Reserved (LUN) Service Action
02 (MSB)
03
04
05 (LSB)
06 Reserved
07 (MSB) TRANSFER LENGTH (if required)
09 CONTRO L
76543210
LOGICAL BLOCK ADDRESS (if required)
PARAMETER LIST LENGTH (if required)
ALLOCATION LENGTH (if required)08
(LSB)
Table 2-6: 12-Byte Command Format
Bits
Byte
00 Operation Code
01 Reserved SERVICE ACTION (if required)
02 (MSB)
03
04
05 (LSB)
06
07
08
09 (LSB)
10 Reserved
11 CONTRO L
76543210
LOGICAL BLOCK ADDRESS (if required)
(MSB)
TRANSFER LENGTH (if required)
PARAMETER LIST LENGTH (if required)
ALLOCATION LENGTH (if required)
24
Table 2-7: 16-Byte Command Format
Bits
Chapter 2. SCSI Basics
Byte
00 Operation Code
01 Reserved SERVICE ACTION (if required)
02 (MSB)
03
04
05 (LSB)
06 (MSB)
07
08
09 (LSB)
10
11
12
13 (LSB)
76543210
LOGICAL BLOCK ADDRESS (if required)
Additional CDB Data (if required)
(MSB)
TRANSFER LENGTH (if required)
PARAMETER LIST LENGTH (if required)
ALLOCATION LENGTH (if required)
14 Reserved
15 CONTRO L
Command Field Definitions
Operation Code (byte 00, bits 7-0) The operation code for the command descriptor block is a
group code field and a command code field. The three-bit group code field provides
for eight groups of command codes. The operation group codes supported by the
library are defined below.
Table 2-8: Operation Code
Bits
Byte
00 Group Code Command Code
76543210
25
Chapter 2. SCSI Basics
Table 2-9: Group Codes
Group Code Description
0h 6-byte commands
1h-2h 10-byte commands
5h 12-byte commands
6h-7h Vendor-Specific
The five-bit command code field provides for 32 command codes in each group. A total
of 256 possible operation codes exist. Specific operation codes are described in detail
in the sections for the individual SCSI commands.
Logical Unit Number (Byte 1, Bits 7-5) The logical unit number (LUN) for the library will usually
be 0, particularly over the SCSI interface. This field is approved for SCSI-2 devices, and
support for SCSI-2 is standard. Over the Fibre Channel interface, the LUN for a library
can be 0 or 3 (logically, these are different libraries inside one physical library). The
robotics controller is a single device target and does not support multiple logical
devices from the SCSI interface. The Fibre Channel interface does support multiple
logical devices.
Reserved Bits (varies, see specific command) The reserved fields are set aside for future
standardization. The use and interpretation of these fields may be specified by future
extensions to the SCSI-2 or SCSI-3 standard. All reserved bits, fields, or bytes will be set
to 0, or as specified later in any future extension to the SCSI-2 standard. If the library
receives a reserved bit, field, or byte that is not 0, or receives a reserved code value, it
terminates the command with a CHECK CONDITION status and the sense key is set to ILLEGAL
REQUEST.
Logical Block Address Parameters (varies, see specific command) The command descriptor block
(CDB) parameters contain fields which are defined in specific commands. These are
used mainly for element addressing and parameter selection.
Transfer Length, Parameter List Length, or Allocation Length (varies, see specific command) The transfer
length specifies the amount of data to be transferred or received by the command. The
parameter list length is used to specify the number of bytes sent to the target during
the data out phase, or how many bytes will be returned. A 0 parameter length indicates
that no data will be transferred. This condition is not considered an error.
Logical Block Address This is not used for media changer devices.
26
Chapter 2. SCSI Basics
Control Byte (varies, see specific command) The control field is the last byte of every CDB. The
control field is defined below.
Table 2-10: Control Byte
Bits
Byte
Final Byte of Command Vendor-Unique Reserved Flag Link
Vendor Unique The Vendor-Unique fields, if used, are defined for each specific
command. The user does not need to support the vendor-unique definitions to
obtain specified performance.
Flag The Flag bit specifies which message that the target returns to the initiator if the
link bit is 1 and the command completes without error. The library does not
support linked commands and returns a CHECK CONDITION if this bit is set. This bit must
be set to 0.
Link The Link bit is used to continue the I/O process across multiple commands.
None of the Gator libraries support linked commands. The library will return a CHECK
CONDITION if this bit is set. This bit must be set to 0.
76543210
SCSI Command Status
The library sends one status byte to the initiator during the status phase. The following
events cause the command to be terminated without entering the status phase:
•An ABORT message
•A BUS DEVICE RESET message
•A HARD RESET condition
•An UNEXPECTED DISCONNECT
The status phase normally occurs at the end of each command; however, it may occur
before transferring the command descriptor block.
27
Chapter 2. SCSI Basics
Status Byte Codes
The table below describes the Gator library status byte format:
Table 2-11: Status Byte Format
Bits
Byte
00 Reserved Status Byte Code Reserved
76543210
Status Byte Field Descriptions
Reserved The reserved fields are reserved for future use.
Status Byte Code See Table 2-12 for Status Byte Code field descriptions.
Table 2-12: Status Byte Code Field Descriptions
76543210Meaning
0 x 0 RR00000R
0 x 2 RR00001R
0 x 8 RR00100R
GOOD. Indicates that the library successfully completed the
command.
CHECK CONDITION. Indicates that sense information is set,
caused by any error, exception or abnormal condition.
BUSY. Indicates that the library is unable to accept a
command from an initiator.
0 x 18 RR01100R
GOOD (00h) The GOOD status indicates that the operation specified by the command has
completed correctly. For commands that support the immediate return of status, GOOD
status indicates that the library has accepted the command and attempts to perform the
operation specified by the CDB. If the specified operation does not complete correctly,
the library returns a CHECK CONDITION status after receiving the next command from the
initiator.
CHECK CONDITION (02h) The library returns a CHECK CONDITION status if an error occurs while it is
executing a command. The reporting of a CHECK CONDITION status generally occurs
immediately after or upon receipt of a command.
RESERVATION CONFLICT. Indicates that the elements
identified in the command are reserved by another initiator.
28
Chapter 2. SCSI Basics
The CHECK CONDITION status is reported immediately after a command is completed unless
the library is disconnected from the SCSI bus. If the library is disconnected, CHECK
CONDITION status is reported to the initiator immediately following the reconnect process.
CHECK CONDITION status is reported upon receipt of a command in the following cases:
• A SCSI error (bus parity error or format check) in the CDB.
• The command is the first received by the library after a UNIT ATTENTION condition has
been generated (i.e., it was reset by a BUS RESET condition, a BUS DEVICE RESET message, a
power-on reset, or if media is moved in the library). The sense key is set to UNIT
ATTENTION (06h).
• A motion command is received after a hardware error (robotics error) occurred or
when the unit has a pending CHECK CONDITION that has not been cleared.
Note: For specific situations that return CHECK CONDITION status, refer to the
command descriptions described a the start of each chapter.
BUSY (08h) This status indicates that the library is busy. The library disconnects from the
SCSI bus when performing any lengthy operation (e.g., a move operation). If any other
initiator attempts to send a command while the library is disconnected, it receives a
BUSY status from the library.
RESERVATION CONFLICT (18h) This status indicates that the elements requested for access are
currently reserved by another initiator. This status is reported until the initiator, which
reserved the elements in conflict, issues a RELEASE command. Also, a reset or power-on
condition will clear all reservations.
Sense Keys
See Chapter 18. Error Reporting for lists of sense keys, additional sense codes,
additional sense code qualifiers and their meanings.
NO SENSE (00h) This is returned to the initiator when there is no specific sense key
information.
NOT READY (02h) This is returned to the initiator when the library is not accessible such as
in the following situations:
•Initialization
•Off-line
• Library front door is open
29
Chapter 2. SCSI Basics
HARDWARE ERROR (04h) This is returned to the initiator when the library detects a nonrecoverable hardware failure while performing a command or during a self-test.
ILLEGAL REQUEST (05h) An ILLEGAL REQUEST sense key is returned to the initiator when the
library detects an illegal parameter in the command descriptor block or in the
additional parameters supplied as data. If the target detects an invalid parameter in the
command descriptor block, it terminates the command without altering the medium. If
the target detects an invalid parameter in the additional parameters supplied as data,
the target may have already altered the medium.
UNIT ATTENTION (06h) The library returns a UNIT ATTENTION sense key to the initiator in the
following situations:
•After a BUS DEVICE RESET message, SCSI bus reset or power-on reset
• After the library front door has been opened and closed (this action indicates that
data cartridges may have been removed or replaced)
• Anytime the library inventory might have been changed by another initiator or is
invalid
• When mode parameters have been changed by another initiator through a MODE
SELECT command
Note: If mode parameters are changed, the initiator should issue a MODE
SENSE (1Ah) command to request the new mode parameters.
VENDOR UNIQUE (09h) The library may return a VENDOR UNIQUE sense key to the initiator when
it detects certain robotics command errors or SCSI initiator command errors.
COPY ABORTED (Ah) The library may return a COPY ABORTED sense key to the initiator to indicate
that a COPY, COMPARE, COPY AND VERIFY, or EXTENDED COPY command was aborted due to an error
condition on the source device, the destination device, or both.
30
Loading...