z/OS MVS Programming: Writing Transaction Programs for APPC/MVS
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Collecting Trace Data for TPs with Multiple Levels

z/OS MVS Programming: Writing Transaction Programs for APPC/MVS
SA23-1397-00

In Figure 1, notice that TPA is defined in more than one TP profile file, with different TP levels. Because APPC/MVS does not provide the ability to identify which level of TP you want to trace, APPC/MVS traces all conversations established for the LUA/TPA combination, regardless of the TP level. For example, TPB allocates to a user-level instance of TPA (2 and 2a), whereas TPC allocates to a system-level instance of TPA (3 and 3a).

Figure 1. Collecting API Trace Data for TPs with Multiple Levels
ieac3tlv

The trace data set contains API trace data for both levels, which might make interpreting the trace data more difficult, especially if TPA's processing varies by level. See Determining the Level of TP Traced for advice on distinguishing trace data for different levels of the TP.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014