technical content. 10/24/2008 3.3.1 Editorial Changed language and formatting in the technical content. 12/5/2008 3.3.2 Editorial Changed language and formatting in the technical content. 1/16/2009 3.3.3 Editorial Changed language and formatting in the technical content. 2/27/2009 3.3.4 Editorial Changed language and formatting in the technical content. 4/10/2009 3.3.5 Editorial Changed language and formatting in the technical content. 5/22/2009 4.0 Major Updated and revised the technical content. 7/2/2009 4.0.1 Editorial Changed language and formatting in the technical content. 8/14/2009 4.0.2 Editorial Changed language and formatting in the
technical content. 9/25/2009 5.0 Major Updated and revised the technical content. 11/6/2009 5.1 Minor Clarified the meaning of the technical content. 12/18/2009 5.2 Minor Clarified the meaning of the technical content. 1/29/2010 5.3 Minor Clarified the meaning of the technical content. 3/12/2010 6.0 Updated and revised the technical content. 4/23/2010 7.0 Updated and revised the technical content. 6/4/2010 8.0 Major Updated and revised the technical content. 7/16/2010 9.0 Updated and revised the technical content. 8/27/2010 9.0 None No changes to the meaning, language, or formatting of the technical content.
10/8/2010 10.0 Major Updated and revised the technical content. 11/19/2010 10.1 Minor Clarified the meaning of the technical content. 1/7/2011 10.1 None No changes to the meaning, language, or formatting of the technical content. 2/11/2011 10.1 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 10.1 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 10.1 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 10.2 Minor Clarified the meaning of the technical content. 9/23/2011 10.2 None No changes to the meaning, language,
or formatting of the technical content. 12/16/2011 11.0 Major Updated and revised the technical content. 3/30/2012 11.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 11.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 11.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 11.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 12.0 Major Updated and revised the technical content. 11/14/2013 12.0 None No changes to the meaning, language,
Triggered Events Pull Transaction The Pull Transaction event MUST be by the with the following arguments: address. Superior's Transaction Identifier. See section 13 for information on this TIP command. If the Pull Transaction event is signaled, the MUST perform the following actions: If the provided Superior's Transaction Identifier does not have the format: Call the manager's with the following arguments: The provided partner transaction manager address. The provided Superior Transaction Identifier. If HasPartnerTransaction returns TRUE, the Pull has already been completed, so notify the higher-layer business logic that the Pull request was completed successfully and terminate the processing of this event. Otherwise: Create a new object with a new GUID as an identifier. Create a new enlistment object with the following values: The transaction field is set to the created transaction object. The Partner Transaction Manager Address field is set to the provided partner transaction manager address. The Partner Transaction Identifier is set to the provided Superior Transaction Identifier. Signal the Create Superior Enlistment event ( section 3.2.7.12) on the with the following argument: The new enlistment object. Message Processing Events and Sequencing Rules This section describes how each received is processed. Each of these events is signaled with a TIP command object as an input argument. Receiving ABORT TIP Command When the (section ) receives an ABORT TIP command, it MUST perform the following actions: If the Connection Type field of the receiving object is not set to Secondary, the and terminate the processing of this event. If the field of the receiving TIP connection object is not set to either Aborted, Enlisted, or Prepared, signal the Invalid TIP Command event (section 3.3.7.1) and terminate the processing of this event. If the State field of the receiving TIP connection object is set to Aborted:
19 29 29 N 29 10 30 51 36 37 O Overview 21 21 26 27 27 10 10 P 77 73 68 75 67 17 51 37 17 25 57 78 Propagation 71 72 Protocol Details 21 11 20 20 38 49 52 20 20 52 34 20 20 39 Q 53 54 20 20 48 40 R 73 40 30 20 20 54 41 74 10 10 10 17 Rollback Complete ( 61, 68) S Scenarios 76 13 70 26 77 77 77 Sequencing rules 27 50 35 64 76 18 80 10 19 T 24 Timer events 56 41 66 Timers 48 33 64 11 56 24 70 22 22 TIP subordinate transaction manager facet 46 49 49 56 50 46 50 56 48