LU 6.2 API Application Programmer's Reference Guide (30294-90008)

Chapter 7 143
Debugging
The User Trace
Field Descriptions
Figure 7-1 is an example of a trace of a two-way conversation. This
section explains the meaning of each field in the user trace.
Intrinsic name
The name of each LU 6.2 API intrinsic the local TP
calls appears on the left side of the display.
RetCode
(Return Code) This is the status info value returned in
the
Status parameter of the intrinsic. The status info
is the most useful piece of diagnostic information in the
user trace. It directs you to areas of investigation that
help you identify problems with your TP. Chapter 5 ,
“Intrinsic Descriptions,” lists the values that each
intrinsic can return, and Appendix A , “Status Info,”
lists the causes and recommended actions for all status
info values.
Rsrc
(Resource ID) This is the conversation identifier
returned by MCAllocate or MCGetAllocate. It
identifies the conversation for which each intrinsic was
called. In the example, only one conversation (with
Resource ID of 15) was allocated, so all intrinsics were
called for that conversation. If more than one
conversation had been allocated (that is, if MCAllocate
had been called more than once by the TP), the
different Resource IDs would tell you which intrinsic
calls belonged to which conversations.
ConvState
This is the conversation state of the local TP after the
intrinsic has executed.
Intrinsic parameters
The rest of the fields in the trace are the parameters
specific to each intrinsic. Different parameters are
traced for different intrinsics. The parameters are
listed here by intrinsic. See Chapter 5 , “Intrinsic
Descriptions,” for more information on intrinsics and
their parameters.
TPStarted:
TPID Transaction program identifier
TPName Name of transaction program
TraceSize Trace file size in records