Triggered Events Pull Transaction The Pull Transaction event MUST be by the with the following arguments: address. See section 13 for information on this TIP command. Superior's Transaction Identifier. 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:
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:
%5BMS-TIPP%5D-170601.docx