1.3.2.2 Pulling a Transaction
In this scenario, application A sends a request to application B to pull a local transaction that it creates with its TIP transaction manager A, and do some work as part of the pulled transaction. The following figure illustrates the scenario (TIP protocol messages are illustrated with dashed arrows).

Figure 3: Pulling a transaction
Application A requests the TIP transaction manager communicating with an application facet (section 3.4.1.1) of TIP transaction manager A to create a transaction by sending the BEGIN TIP command.
TIP transaction manager communicating with an application facet replies with a BEGUN TIP command, passing in the identifier of the transaction (tidA) created by TIP transaction manager A.
Application A does some local work in the transaction.
Application A requests application B to do some work within the same transaction.
Application B requests TIP transaction manager B to pull this transaction.
The TIP subordinate transaction manager facet (section 1.3.1.2.2) of TIP transaction manager B sends a PULL TIP command to the TIP superior transaction manager facet (section 1.3.1.2.1) of TIP transaction manager A, passing in parameters tidA and tidB (its local identifier for the transaction).
TIP transaction manager A agrees by responding with the PULLED TIP command. At this point, TIP transaction manager B has an enlistment in the transaction, and the transaction is bound to the TIP connection.
TIP transaction manager B returns to application B.
Application B does the requested work using the pulled transaction.