Using VTAM Generic Resource Names
If a TP issues an Allocate call specifying the VTAM generic resource name
MVSLU, that call can be directed to any of the LUs in the generic resource
group. Because you cannot always predict which LU will handle the conversation,
you run the risk of not tracing the conversation unless you:
- Specify the generic resource name MVSLU on the ATBTRACE START request, and
- Issue the START request on each system on which an MVSLU group member resides.
For example, suppose you entered a START request specifying TPA and LUC on MVS01, but did not enter the same START request on MVS02. Given the configuration in Figure 1, the Allocate request from TPC is directed to LUD, so you would not get any trace data for TPA's calls for its conversation with TPC.
Figure 1 shows sample ATBTRACE START requests that IBM recommends
for TPs running on MVS LUs in a generic resource group. If your installation
uses a VTAM generic resource name for all the LUs on which TPA might run,
and you want to collect trace data for all of TPA's conversations regardless
of the LU selected to handle the inbound Allocate call, do the following:
- Specify the VTAM generic resource name for the LU keyword value on the START request.
- If the LUs in the generic resource group reside on more than one MVS system:
- Issue the START request on each z/OS system.
- For each START request, specify a different trace data set, because each data set can be in use by only one system at a time.
Figure 1. Using VTAM
Generic Resource Names
z/OS MVS Planning: APPC/MVS Management contains possible security requirements and general information about VTAM generic resource support for APPC/MVS LUs.