If it does not matter on which system an invokable TP runs, use the same name for multiple invokable TPs and do not specify an LU alias in the registry or environment variables for the TPs. In this situation, there are no associated LU aliases in the list of available invokable TP names on an SNA server. Thus, a request received from an invoking TP cannot cause a mismatch on the LU alias, and will match according to the TP name.
In this situation, if you set the DloadMatchLocalFirst registry entry to NO, as described in the Microsoft SNA Server Reference, SNA Server randomly routes the request to one of the available TPs. This spreads the processing load among multiple systems and provides hot backup (the ability to take systems online and offline without disrupting service).