dwConnectionId (4 bytes): A 4-byte integer value that MUST contain the unique identifier for the associated . dwUserMsgType (4 bytes): This field contains the message type identifier. Each MTAG that is defined in this section MUST specify a distinct value for this field for a specified . dwcbVarLenData (4 bytes): An unsigned 4-byte integer value that MUST contain the size, in bytes, of the message buffer that contains the MESSAGE_HEADER structure, minus the size, in bytes, of the MESSAGE_HEADER structure itself. dwReserved1 (4 bytes): Reserved. This value MUST be set to an implementation-specific value and MUST be ignored on receipt. XA_BQUAL_1 The XA_BQUAL_1 structure is used to represent the portion of an . 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 XATMGUID (16 bytes) ... ... RMGUID (16 bytes) ... ... BranchGUID (16 bytes, optional) ... ... XATMGUID (16 bytes): This field MUST contain a GUID that specifies the for the instance. RMGUID (16 bytes): This field MUST contain a GUID that specifies the Resource Manager Identifier for the XA Transaction Manager instance. BranchGUID (16 bytes): This field MAY contain a GUID initialized by the AP that specifies the for this . Whether the AP specifies this or not is implementation-specific. The BranchGUID is not used by DTC; however, the bqualLength field in the XA_XID structure MUST be specified accordingly as in section . XA_XID The XA_XID structure is used to represent an . This structure follows the format specified by the technical standard, "Distributed Transaction Processing: The XA Specification", as specified in . The particular format of the XA_XID structure is used when MSDTC creates the , which occurs only in the scenario described in section . When MSDTC is the as in the scenario described in section , the XID is provided by the superior XA Transaction Manager, and the format of the XID can vary.
dwConnectionId (4 bytes): A 4-byte integer value that MUST contain the unique identifier for the associated . dwUserMsgType (4 bytes): This field contains the message type identifier. Each MTAG that is defined in this section MUST specify a distinct value for this field for a specified . dwcbVarLenData (4 bytes): An unsigned 4-byte integer value that MUST contain the size, in bytes, of the message buffer that contains the MESSAGE_HEADER structure, minus the size, in bytes, of the MESSAGE_HEADER structure itself. dwReserved1 (4 bytes): Reserved. This value MUST be set to an implementation-specific value and MUST be ignored on receipt. XA_BQUAL_1 The XA_BQUAL_1 structure is used to represent the portion of an . 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 XATMGUID (16 bytes) ... ... RMGUID (16 bytes) ... ... BranchGUID (16 bytes, optional) ... ... XATMGUID (16 bytes): This field MUST contain a GUID that specifies the for the instance. RMGUID (16 bytes): This field MUST contain a GUID that specifies the Resource Manager Identifier for the XA Transaction Manager instance. BranchGUID (16 bytes): This field MAY contain a GUID initialized by the AP that specifies the for this . Whether the AP specifies this or not is implementation-specific. The BranchGUID is not used by DTC; however, the bqualLength field in the XA_XID structure MUST be specified accordingly as in section . XA_XID The XA_XID structure is used to represent an . This structure follows the format specified by the technical standard, "Distributed Transaction Processing: The XA Specification", as specified in . The particular format of the XA_XID structure is used when MSDTC creates the , which occurs only in the scenario described in section . When MSDTC is the as in the scenario described in section , the XID is provided by the superior XA Transaction Manager, and the format of the XID can vary.