Operation
TDI_ACTION is a request message a client issues to indicate an action request.
Note TdiBuildAction is the macro a client uses to fill in the IRP.
When a client makes an action request, it asks the TDI driver to make special or proprietary extensions (or both) applicable only to it, and not to any other TDI clients or drivers. The client makes an action request for extensions related to an address, a connection, or the control channel. It includes in the IRP a parameter block containing all information concerning the requested action. This block’s header uses a standard format containing a transport identifier and an action code. For more information about the parameter block header and action code, see Part II, Chapter 11. The internal driver action function uses the transport identifier to validate the action request. The action code identifies the action and determines the contents of the remainder of the parameter block.
Along with the request message, the TDI client must provide input and output buffers for the IRP, as well as a status block structure the driver uses to write information about the request. These items are described below. For more information about the members of the IRP related to an action request, see TdiBuildAction.
Input
None
Output
None
I/O Status Block
The driver fills in the Status member of the IRP with one of the following TDI status codes:
STATUS_INSUFFICIENT_RESOURCES
STATUS_INVALID_CONNECTION
STATUS_NOT_IMPLEMENTED
STATUS_PENDING
STATUS_SUCCESS
For more information about status codes, see Part II, Chapter 10.
The Information member of the IRP contains the number of data bytes that the internal driver action function writes.
See Also