This topic describes what happens as each of the three systems are set up to take work requests. The steps are described sequentially. However, you should realize that these events do not necessarily happen sequentially. Once a member issues IXCJOIN, any of its user routines can get control in any order, and can even get control prior to completion of the IXCJOIN service. The example shows the operator starting the tasks on system 1, then system 2, then system 3. However, it is possible, for example, that member 2 might finish initialization prior to member 1 and be the first member in the table. This is one reason why each member issues IXCQUERY to determine which other members are already active.