2.2.5.1.3.2 TXUSER_TIPPROXYGATEWAY_MTAG_PULL2

  The TXUSER_TIPPROXYGATEWAY_MTAG_PULL2 message is used by a TIP application to initiate a TIP pull propagation.  


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

MsgHeader (24 bytes)

...

...

fAsync

cbTipTmId

tipTmId (variable)

...

tipTxId (variable)

...

MsgHeader (24 bytes): This field MUST contain a MESSAGE_PACKET structure.

  • The dwUserMsgType field MUST be 0x00005108.

  • The dwcbVarLenData field MUST be equal to the sum of the values of the cbHostName and cbPath fields in the tipTmId structure, rounded to a multiple of 4; plus the value of the cbTipTxId field in the tipTxId structure, rounded to a multiple of 4; plus 32.

fAsync (4 bytes): A 4-byte value that indicates whether a synchronous or an asynchronous pull is required.

This value MUST be one of the following values:

Meaning

0x00000000

A synchronous pull propagation is required.

0x00000001

An asynchronous pull propagation is required.

cbTipTmId (4 bytes): A reserved 4-byte field. Implementers MUST not use this field.

tipTmId (variable): This field identifies the TIP transaction manager against which the TIP pull propagation was requested. This field MUST contain an OLETX_TIP_TM_ID structure and MUST be aligned on a 4-byte boundary by padding with arbitrary values.

tipTxId (variable): This field identifies the transaction for which the TIP pull propagation was requested. This field MUST contain an OLETX_TIP_TX_ID structure and MUST be aligned on a 4-byte boundary by padding with arbitrary values.