SNAX/APC Configuration and Management Manual

Trace Analysis Program

SNAX/APC Configuration and Management Manual—138787

5-21

Error Version (Trace Format)

The remote TP issues DEALLOCATE (LOCAL). This will release the local

conversation resources such as the RCBs. The TP finally issues a TP-END to end

the TP instance and the TCBs.

Error Version (Trace Format)

The same conversation takes place, but now an error has been inserted. The example

uses the trace program to locate the source of the error.

The discussion of the trace includes an interpretation of the SNA request/response

headers (RH) so that you will be able to follow the logic flow more closely—this will

assist you in reading traces in the future.

Some of the details assume that you know how to convert RH formats from hexadecimal

to binary, or at least read RH information, and that you can look up the meanings of

SNA sense data codes. This knowledge is not absolutely vital to reading the trace, but it

helps.

The Local TP

First, the conversation is shown from the local TP’s point of view. The trace is centered

around data flows and BIUs in and out of SNAX/APC itself.

It may be helpful to remind yourself of the meanings of DIN/DOUT and BIN/BOUT

(see Figure 5-1

) before continuing with this example.

FMT> display all

==============================================================================

<OPENER> seq: 5 05/13/92 11:40:01.76

type: OPEN

ocb id: %H0008; protocol: APPL

opener name: \ABCD2.$Y660

5C534E41 58322E24 59363630