Using Symbolic Destination Names
In Figure 1, if TPC issues an Allocate call specifying a symbolic destination name, NYC35TH, that resolves to LUA and TPA, APPC/MVS provides trace data for that conversation. Even though you specified the LU and TP keywords, instead of the SYMDEST keyword, on the START request, APPC/MVS provides trace data for the conversation because the LU and TP values match. If you know that TPA's partners allocate their conversations using a symbolic destination name, however, IBM recommends that you use the SYMDEST keyword and value on the ATBTRACE START request.
Figure 1. Using Symbolic
Destination Names