Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Timing: When Tracing Starts z/OS MVS Programming: Writing Transaction Programs for APPC/MVS SA23-1397-00 |
|
In Figure 1, if TPB allocates a conversation with its partner TPA (1a) before you issue the START request (2), APPC/MVS does not provide any trace data for that conversation, even though the LU and TP values match. APPC/MVS provides trace data only for conversations that are established after it finishes processing a START request. Generally speaking, a conversation is established when a program issues an Allocate call or, in the case of APPC/MVS servers, a Register_for_Allocates call. When the ATBTRACE START request is issued before the conversation is established, trace data begins with a trace entry for the Allocate or Register_for_Allocates call. For APPC/MVS TPs that issue CPI-C verbs, however, a conversation is established
when either:
Figure 1. Timing the
Start of API Tracing Activity
APPC/MVS does not start tracing activity at all for the LU/TP combination, if the call to establish the conversation contains partner LU name or TP name values that do not match the LU/TP combination specified through the ATBTRACE START request. |
Copyright IBM Corporation 1990, 2014
|