Successful Completion: The HACB completed without error, but the HAM was told to freeze the queue upon completion of the current HACB by the CDM. The CDM indicated this to the HAM by setting the Freeze_Queue_Flag in the HACB's controlInfo field prior to issuing (executing) the HACB.

Check Condition: If the HAM does not support Auto Request Sense, the CDM must issue a Request Sense command to retrieve the actual cause of the check condition.

Reservation Conflict: The device has been reserved by some other initiator. The HAM returns this Status code to the CDM level, which then deactivates the device.

Timeout Error: HAM timeout processing was enabled because the CDM placed a non-zero value in the timeoutAmount field of the HACB. Then, when the HAM's timeout thread (HAM_Timeout) became active, it determined that the HACB request currently being executed by the device exceeded the time allotment specified in the HACB's timeoutAmount field. The timeout countdown begins after the HACB is processed and sent to the device by the HAM. The CDM can spawn an error handling thread to attempt to diagnose and remedy the problem by issuing priority HACBs. However, if the timeout error persists after a few remedy attempts, the CDM should complete this HACB with Device Error (0x00000012) as the npaCompletionCode.

Data Overrun - No Transfer Count Available: The HAM detects an overrun condition reported by the adapter, meaning that the buffer size allocated for the request was smaller than needed to physically transfer the data. When the CDM detects this error, it can either request sense to find out the residual byte count and recover, or it can complete the corresponding message with Parameter Error (0x00000016) as the npaCompletionCode.

Data Overrun - Actual Transfer Count Available: The HAM detects an overrun condition reported by the adapter, meaning that the buffer size allocated for the request was smaller than needed to physically transfer the data. However, the HAM can provide the actual number of data bytes that were transferred. The HAM places this value in the HACB's controlInfo field before completing the HACB. When the CDM detects this error, it should complete the corresponding message with Parameter Error (0x00000016) as the npaCompletionCode and the transfer count in the HACB's controlInfo field as the AppReturnCode.

Bad Command Length: Indicates an illegal, interface-specific command length.

Bad Direction Bit: Indicates that the data direction flag in the HACB's controlInfo field, set by the CDM, is not consistent with the I/O request. The CDM should correct the problem and resend the message, or return a Parameter Error (0x00000016) as the npaCompletionCode.

Bad Auto Error Sense Buffer: Indicates either a bad pointer to an auto error sense buffer or that a buffer wasn’t provided when one was required. The CDM should correct the problem and resend the message, or return a Parameter Error (0x00000016) as the npaCompletionCode.

Unspecific Malformed HACB: The HAM has detected a command protocol that it does not recognize, and the problem is not significant enough for the HAM to freeze the device queue. The CDM should correct the problem and resend the message, or return a Parameter Error (0x00000016) as the npaCompletionCode.

Bad Device Info Buffer: The buffer passed to the HAM's HACB Type Zero function, HAM_Return_Device_Info (Function 0x02), is too small. The CDM should correct the problem and resend the message, or return a Parameter Error (0x00000016) as the npaCompletionCode.

Unsupported Interface Type: The HAM detected that the adapter interface type specified in the HACB's hacbType field does not match the interface type supported by the HAM. When the CDM detects this error, it should complete the corresponding message with Parameter Error (0x00000016) as the npaCompletionCode.

Bad deviceHandle: The device handle contained in the HACBs deviceHandle field does not map to any device being supported by the HAM. The CDM should correct the problem and resend the message, or return a Parameter Error (0x00000016) as the npaCompletionCode.

Abort Completed: the HAM was issued an abort on this HACB, and now the HAM is posting completion of the abort.

Unknown: Errors that do not fit into any of the other categories are mapped to this error value. HAMs post this error value to indicate that some type of error occurred that prevented processing of the HACB. When the CDM detects this error, it should complete the corresponding message with Unknown Completion (0x00000024) as the npaCompletionCode.

Transport Protocol Error at Adapter: The HAM posts this completion code if it detects a protocol error originating at the adapter. When the CDM detects this error, it should complete the corresponding message with Adapter Error (0x00000013) as the npaCompletionCode.

General Media Error: The HAM posts this completion code when it detects a problem in completing a request, but the problem is not due to a device error or an adapter error. When the CDM detects this error, it should reissue the request at least once to see if the problem gets corrected. If the request is a scatter/gather request, the CDM might want to break up the scatter/gather list into individual requests, although this action is not required of the CDM. If the problem persists, the CDM should complete the corresponding CDM message with Media Error (0x00000011) as the npaCompletionCode.

Device Not Active: This error is posted to the HACB if a device goes inactive during the course of issuing requests to it. For example, the device might time out while the adapter is trying to select it. When this error is detected, the CDM should complete the corresponding message with I/O error (0x00000012) as the npaCompletionCode.

AEN HACB: The aborted HACB was an asynchronous event notification HACB.