Figure 1 shows how TP profile and side information files are used by TPs on two different systems. TP1 on the peer system allocates a conversation across the network to TP2, using symbolic destination name TP2sym. The side information translates TP2sym into the necessary information to send the allocate request to the correct LU on z/OS and to the correct TP profile. The TP profile schedules TP2 to run so it can accept the allocate request with a Get_Conversation call. TP2 then allocates a different conversation across the network to TP3 using symbolic destination name TP3sym, and the process repeats itself going from z/OS to the peer system.

Figure 1. Using TP Profiles and Side Information to Find a Partner TP