IBM IC35L036UWDY10 Hard Drive Specifications - Page 209

addl information, 1 SCSI Protocol

Get IBM IC35L036UWDY10 - Ultrastar 36.7 GB Hard Drive PDF manuals and user guides
UPC - 000004119524
View all IBM IC35L036UWDY10 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 209 highlights

11.0 Additional information This chapter provides additional information or descriptions of various functions, features, or operating models supported by the Target that are not fully described in previous chapters. 11.1 SCSI Protocol There are various operating conditions that prevent the Target from executing a SCSI command. This section describes each of these operating conditions and their relative priority. 11.1.1 Priority of SCSI Status Byte Reporting After establishing the I_T_L nexus or I_T_L_Q nexus the Target must first determine whether command execution is allowed. Execution is deferred until a later time if the command must be added to the command queue. Execution may also be prevented by an internal Target condition that requires the reporting of a CHECK CONDITION, QUEUE FULL, BUSY or RESERVATION CONFLICT Status. There are several different internal conditions to be active at the same time. The order in which the Target checks for each of these conditions determines their priority (highest priority first) as follows: 1. CHECK CONDITION status for invalid Logical Unit Number. See Section 11.1.2 , "Invalid LUN in Identify Message" on page 194. 2. CHECK CONDITION status for Incorrect Initiator Connection. See Section 11.1.3 , "Incorrect Initiator Connection" on page 194. 3. BUSY Status or QUEUE FULL Status. See Section 11.1.4 "Command processing during execution of active I/O process" on page 194. 4. CHECK CONDITION status for UNIT ATTENTION condition. See Section 11.1.5 "Unit Attention Condition" on page 196. 5. CHECK CONDITION status during Startup and Format operations. See Section 11.1.6 "Command processing during startup and format operations" on page 197. 6. CHECK CONDITION status for Deferred Error Condition. See Section 11.1.7 , "Deferred Error" on page 197. 7. RESERVATION CONFLICT status. See Section 11.1.9 , "Command processing while reserved" on page 203. 8. CHECK CONDITION status for invalid command opcode 9. CHECK CONDITION status for invalid command descriptor block The highest priority internal condition that prevents command execution is reported by theTarget if there is no bus error. For all CHECK CONDITION Sense data is built by the drive provided a valid LUN address is known. Sense data is cleared by the Target upon receipt of any subsequent command to the LUN from the initiator receiving the CHECK CONDITION. Ultrastar 146Z10 hard disk drive specifications 193

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
11.0 Additional information
This chapter provides additional information or descriptions of various functions, features, or operating
models supported by the Target that are not fully described in previous chapters.
11.1 SCSI Protocol
There are various operating conditions that prevent the Target from executing a SCSI command. This
section describes each of these operating conditions and their relative priority.
11.1.1 Priority of SCSI Status Byte Reporting
After establishing the I_T_L nexus or I_T_L_Q nexus the Target must first determine whether command
execution is allowed. Execution is deferred until a later time if the command must be added to the com-
mand queue. Execution may also be prevented by an internal Target condition that requires the reporting
of a CHECK CONDITION, QUEUE FULL, BUSY or RESERVATION CONFLICT Status. There are several
different internal conditions to be active at the same time. The order in which the Target checks for each of
these conditions determines their priority (highest priority first) as follows:
1.
CHECK CONDITION status for invalid Logical Unit Number. See Section 11.1.2 , “Invalid LUN in
Identify Message” on page 194.
2.
CHECK CONDITION status for Incorrect Initiator Connection.
See Section 11.1.3 , “Incorrect Initiator
Connection” on page 194.
3.
BUSY Status or QUEUE FULL Status.
See Section 11.1.4 “Command processing during execution
of active I/O process” on page 194.
4.
CHECK CONDITION status for UNIT ATTENTION condition.
See Section 11.1.5
“Unit Attention
Condition” on page 196.
5.
CHECK CONDITION status during Startup and Format operations.
See Section 11.1.6 “Command
processing during startup and format operations” on page 197.
6.
CHECK CONDITION status for Deferred Error Condition.
See Section 11.1.7 , “Deferred Error” on
page 197.
7.
RESERVATION CONFLICT status.
See Section 11.1.9 , “Command processing while reserved” on
page 203.
8.
CHECK CONDITION status for invalid command opcode
9.
CHECK CONDITION status for invalid command descriptor block
The highest priority internal condition that prevents command execution is reported by theTarget if there is
no bus error.
For all CHECK CONDITION Sense data is built by the drive provided a valid LUN address is known.
Sense data is cleared by the Target upon receipt of any subsequent command to the LUN from the
initiator receiving the CHECK CONDITION.
Ultrastar 146Z10 hard disk drive specifications
193