7.0 HACB Type Zero Functions

For convenience, the following table lists the HACB functions in alphabetical order. However, in the remainder of this document, they are presented in numerical order.

HACB type zero functions are called for HACB requests where the hacbType field has a value of zero. NWPA requires a HAM to implement as many of these functions as are applicable to its adapter type. hacbType = 0 requests ask for information about the HAM, the host adapter, attached devices, sets a device's queue state, or monitors asynchronous hardware events. The HAM receives requests of this type through the union to Host command block of the HACB. Currently, there are eight HACB type zero functions that HAMs are required to implement; however, Novell has reserved up to 256 of these functions for the future. For HAMs to determine which of the functions to execute along with any applicable input parameters, the Host command block of the HACB provides the following information:

All data transfers must be handled as any other HACB request. This means that data is either placed in or retrieved from the data buffer fields of the HACB (vDataBufferPtr or pDataBufferPtr). Also, the buffer's size (in bytes) is specified in the HACB's dataBufferLen field by the process transferring the data. The functional descriptions in the following sections detail how the above information should be interpreted by the HAM in order to complete the hacbType = 0 request. The functions are listed alphabetically.

If a particular hacbType = 0 function is not supported, the function must return the HACB with a NPA_MALFORMED_HACB (or NPA_MALFORMED_HACB_QUEUE_FROZEN) value in the upper word of the hacbCompletion field and NPA_UNSUPPORTED_HACB_TYPE_0_FUNCTION value in the lower word of the same field (0x00030043 or 0x80030043).