| BLOCK_DEVICE_RANGE_DESCRIPTOR | The BLOCK_DEVICE_RANGE_DESCRIPTOR structure describes a range of logical blocks associated with various fragments of a file for an offload copy operation. |
| BLOCK_DEVICE_TOKEN_DESCRIPTOR | BLOCK_DEVICE_TOKEN_DESCRIPTOR contains the token returned from a the POPULATE TOKEN command for an offload read data operation. |
| CURRENT_INTERNAL_STATUS_PARAMETER_DATA |
| ERROR_HISTORY_DIRECTORY |
| ERROR_HISTORY_DIRECTORY_ENTRY |
| INQUIRYDATA | The INQUIRYDATA structure is used in conjunction with the TapeMiniExtensionInit and TapeMiniVerifyInquiry routines to report SCSI inquiry data associated with a tape device. |
| PHYSICAL_ELEMENT_STATUS_DATA_DESCRIPTOR | The PHYSICAL_ELEMENT_STATUS_DATA_DESCRIPTOR structure contains status information for a physical element. |
| PHYSICAL_ELEMENT_STATUS_PARAMETER_DATA | The PHYSICAL_ELEMENT_STATUS_PARAMETER_DATA structure contains the parameter data for a physical element. |
| POPULATE_TOKEN_HEADER | A populate token parameter list starts with a POPULATE_TOKEN_HEADER structure. This is the header for the parameters in a command data block (CDB) of the POPULATE TOKEN command. |
| PRI_REGISTRATION_LIST | The PRI_REGISTRATION_LIST structure is returned in response to a Persistent Reserve In command with ServiceAction = RESERVATION_ACTION_READ_KEYS. |
| PRI_RESERVATION_DESCRIPTOR | The PRI_RESERVATION_DESCRIPTOR structure is used to construct the PRI_RESERVATION_LIST structure that is returned in response to a Persistent Reserve In command with ServiceAction = RESERVATION_ACTION_READ_RESERVATIONS. |
| PRI_RESERVATION_LIST | The PRI_RESERVATION_LIST structure is returned in response to a Persistent Reserve In command with ServiceAction = RESERVATION_ACTION_READ_RESERVATIONS. |
| PRO_PARAMETER_LIST | The PRO_PARAMETER_LIST structure is sent in a Persistent Reserve Out command to a device server. |
| RECEIVE_TOKEN_INFORMATION_HEADER | The RECEIVE_TOKEN_INFORMATION_HEADER structure contains information returned as status from an offload data transfer operation. |
| RECEIVE_TOKEN_INFORMATION_RESPONSE_HEADER | A token, created as a representation of data (ROD), for an offload read data operation is returned in a RECEIVE_TOKEN_INFORMATION_RESPONSE_HEADER structure. |
| REPORT_ZONES_DATA | Note This structure is for internal use only and should not be called from your code. . |
| RT_PARAMETER_DATA | The RT_PARAMETER_DATA structure contains the parameter data for the report timestamp command. |
| SAVED_INTERNAL_STATUS_PARAMETER_DATA |
| SES_CONFIGURATION_DIAGNOSTIC_PAGE |
| SES_DOWNLOAD_MICROCODE_CONTROL_DIAGNOSTIC_PAGE | The SES_DOWNLOAD_MICROCODE_CONTROL_DIAGNOSTIC_PAGE structure contains a vendor specific microcode (i.e., firmware) image for use by the enclosure services process. |
| SES_DOWNLOAD_MICROCODE_STATUS_DESCRIPTOR | The SES_DOWNLOAD_MICROCODE_STATUS_DESCRIPTOR structure specifies the status and additional status of a download microcode. |
| SES_DOWNLOAD_MICROCODE_STATUS_DIAGNOSTIC_PAGE | The Download Microcode Status diagnostic page includes information about the status of one or more download microcode operations. |
| ST_PARAMETER_DATA | The ST_PARAMETER_DATA structure contains the parameter list for the set timestamp command. |
| STOR_ADDR_BTL8 | The STOR_ADDR_BTL8 address structure contains the addressing information for an 8-bit Bus-Target-LUN (BTL8) address. |
| STOR_ADDRESS | A general structure for holding a storage device address. |
| TRACK_INFORMATION2 | The TRACK_INFORMATION2 structure is used to report track information. |
| VPD_EXTENDED_INQUIRY_DATA_PAGE |
| VPD_THIRD_PARTY_COPY_PAGE | The VPD_THIRD_PARTY_COPY_PAGE structure defines the vital product data (VPD) page for offload data transfer operations. |
| VPD_ZONED_BLOCK_DEVICE_CHARACTERISTICS_PAGE | Note This structure is for internal use only and should not be called from your code. . |
| WINDOWS_BLOCK_DEVICE_TOKEN_LIMITS_DESCRIPTOR | The WINDOWS_BLOCK_DEVICE_TOKEN_LIMITS_DESCRIPTOR structure is the third party copy descriptor for Windows systems. |
| WRITE_USING_TOKEN_HEADER | The WRITE_USING_TOKEN_HEADER structure describes the destination data locations for an offload write data operation. |
| ZONE_DESCRIPTIOR | Note This structure is for internal use only and should not be called from your code. . |
