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

136 Chapter7

Debugging

Debugging Steps

To minimize the time spent isolating TP problems, follow the procedure

below.

1. Format and analyze the user trace. The user trace is the most useful

point of departure when debugging. If you have not enabled user

tracing, you will have to recreate the problem with user tracing

enabled. See the description of the TPStarted intrinsic, in Chapter

5 , “Intrinsic Descriptions,” for more information on enabling user

tracing.

Scan the user trace for status info values other than 0 (successful

completion). Determine the meaning of any non-zero status info

values.

2. If you cannot ﬁnd any problems with your code, verify that the

remote TP name passed through MCAllocate is the correct name

for the remote TP that will communicate with the local TP.

3. If you do not ﬁnd a problem with the local TP, and you have veriﬁed

that the local TP is communicating with the correct remote TP, talk

with the remote programmer to determine whether the problem lies

with the remote TP. Many problems occur because the local and

remote programs are out of synchronization.