2.2.1.1.1 Version-Specific Aspects of Connection Types Relevant to an Application
The following table shows version-specific aspects for connection types that are relevant to applications. This table includes connection types and messages that are supported on certain versions as well as messages whose size is version specific. If a connection type or message that is relevant to applications is omitted from this table, it is not version specific and MUST be supported on all versions.
|
Version-specific aspect |
V1 |
V2 |
V4 |
V5 |
V6 |
|---|---|---|---|---|---|
|
Version supports connection type CONNTYPE_TXUSER_BEGIN2 (section 2.2.8.1.2) |
No |
Yes |
Yes |
Yes |
Yes |
|
Version supports connection type CONNTYPE_TXUSER_EXTENDEDWHEREABOUTS (section 2.2.8.2.2.1)<3> |
No |
No |
No |
Optional
|
Optional
|
|
Version supports connection type CONNTYPE_TXUSER_GETSECURITYFLAGS (section 2.2.8.4.1) |
No |
No |
Yes |
Yes |
Yes |
|
Version supports connection type CONNTYPE_TXUSER_IMPORT2 (section 2.2.8.2.2.5) |
No |
Yes |
Yes |
Yes |
Yes |
|
Version supports connection type |
No |
No |
No |
Optional
|
Optional
|
|
Version supports connection type |
No |
Optional
|
No |
No |
No |
|
Version supports connection type |
No |
No |
Optional |
Optional |
Optional |
|
Version supports connection type CONNTYPE_TXUSER_TRACE (section 2.2.8.3.5) |
No |
No |
Yes |
Yes |
Yes |
|
Version supports messages TXUSER_EXPORT_MTAG_CREATE2 (section 2.2.8.2.2.2.2) and TXUSER_EXPORT_MTAG_CREATE_NET_TX_DISABLED (section 2.2.8.2.2.2.4) |
No |
No |
Yes |
Yes |
Yes |
|
Version supports message TXUSER_RESOLVE_MTAG_ACCESSDENIED (section 2.2.8.3.2.1)<7> |
No |
No |
Optional
|
Yes |
Yes |
|
The SourceTmAddress field is described by the structure NAMEOBJECTBLOB (section 2.2.5.3) in message TXUSER_ASSOCIATE_MTAG_ASSOCIATE (section 2.2.8.2.1.1.1) |
Yes |
No |
No |
No |
No |
|
The SourceTmAddress field is described by the structure OLETX_TM_ADDR (section 2.2.4.2) in message TXUSER_ASSOCIATE_MTAG_ASSOCIATE (section 2.2.8.2.1.1.1) |
No |
Yes |
Yes |
Yes |
Yes |
|
The SourceTmAddress field is described by the structure NAMEOBJECTBLOB (section 2.2.5.3) in message TXUSER_EXPORT_MTAG CREATE (section 2.2.8.2.2.2.1) |
Yes |
No |
No |
No |
No |
|
The SourceTmAddress field is described by the structure OLETX_TM_ADDR (section 2.2.4.2) in message TXUSER_EXPORT_MTAG_CREATE (section 2.2.8.2.2.2.1) |
No |
Yes |
Yes |
Yes |
Yes |
|
The grfNetworkDtcAcess field of the TXUSER_GETSECURITYFLAGS_MTAG_FETCHED message supports (uses) the following DTCADVCONFIG bits: DTCADVCONFIG_NETWORKDTCACCESS_ENABLE DTCADVCONFIG_NETWORKDTCACCESS_ADMIN DTCADVCONFIG_NETWORKDTCACCESS_TX DTCADVCONFIG_NETWORKDTCACCESS_CLIENTS DTCADVCONFIG_NETWORKDTCACCESS_TIP |
No |
No |
Yes |
Yes |
Yes |
|
The grfNetworkDtcAcess field of the TXUSER_GETSECURITYFLAGS_MTAG_FETCHED message supports (uses) the following DTCADVCONFIG bits: DTCADVCONFIG_INBOUNDNETWORK_TX DTCADVCONFIG_OUTBOUNDNETWORK_TX DTCADVCONFIG_SECURITYLEVEL_NOSECURITY DTCADVCONFIG_SECURITYLEVEL_AUTHENTICATEDONLY DTCADVCONFIG_SECURITYLEVEL_MUTUALAUTH |
No |
No |
No |
Yes |
Yes |
|
The grfOptions field of the TXUSER_GETSECURITYFLAGS_MTAG_FETCHED message supports (uses) the following DTCADVCONFIG_OPTIONS bit: DTCADVCONFIG_OPTIONS_LUTRANSACTIONS_DISABLE |
No |
No |
No |
No |
Yes |
|
The guidSignature field in the STxInfo structure present in propagation-related messages uses a reserved GUID with the binary value representation of {2adb4463-bd41-11d0-b12e-00c04fc2f3ef}. A GUID in this protocol is a 16-byte packet structure that is a unique identifier for an object ([MS-DTYP] section 2.3.4.2). |
No |
Yes |
Yes |
Yes |
Yes |
|
The STxInfo structure supports versioning based on its guidSignature field. |
No |
Yes |
Yes |
Yes |
Yes |
|
Version supports connection type |
No |
No |
No |
No |
Yes |
|
Version supports message |
No |
No |
No |
No |
Yes |