SNAX/APC Configuration and Management Manual

Trace Analysis Program
SNAX/APC Configuration and Management Manual—138787
5-16
An Example Session with APCTAP
BIN and BOUT Entries
BIU entries are similar to DATA entries. However, instead of showing the IPC and
verbs, formatted BIU entries display the BIU that was transmitted to or received from
SNAX/XF, SNAX/APN, or SNAX/CDF. The following example illustrates a BOUT
entry:
The SNAX header (SH). A header that appears before the RH in all SNAX/XF,
SNAX/APN, and SNAX/CDF messages.
The request/response header (RH). Technically part of the SNAX /XF, SNAX/APN,
or SNAX/CDF Header but is useful to view separately.
The RH in expanded form. Shows the meanings of the set and cleared bits in the
RH.
The MU (message unit). Can contain SNA or user data.
In the example above, the RH shows a data flow control (DFC) request of 04.
(SNAX/APC is making a bid here for the local TP to begin the conversation.)
An Example Session with APCTAP
This example is intended to show you how to interpret trace output and therefore give
you some ideas on how to track down problems. The session given here shows the
information flow from a conversation between two TPs, from the point of view of both
TPs (both were traced). Two versions of the conversation were traced.
In the first version (NORMAL), shown in a condensed log format only, everything
completes as expected—the reply codes are all 0.
In the second version (ERROR), a protocol error is deliberately introduced, and the
conversation abends. The second version is shown in both the logged and full trace
information formats.
<BOUT> @mucb 849786 seq: 122 05/13/92 11:40:02.59
mucb:
OCB ID: %H0008
LU ID: %H0002; SESSION ID: %H0007
TPI ID: %H0071; CONV ID: %H0045
000CF77A 000CF77A 00540001 00020007 00450071
00070000 0008000C F41A0000 00100102 20000000
80000000 00000000 00000005
biu: SRPL SEND
SRPL=001B 0000 0000014E 00000000 00000000 0000 0000 0000 000E
RH=4B8280 REQ DFC FI BCI ECI DR1 QRI BBI
04000600 00 [.....]
1
2 3
4
1
2
3
4