HP-UX SNAplus2 Diagnostics Guide

Using snapfilter and snaptrcfmt
Formatting Internal Binary Trace Output into Text Files
Appendix A118
X.25 interface (NLI)
In addition to grouping components together, you can also suppress the
column for a particular component or group. Any messages flowing to or
from this component are shown as flowing to or from the “unknown”
column, which is marked ?? (as shown in the “Message Flow Drawing
Example”).
Each line in the drawing ends with a number prefixed with a $ character,
followed by a timestamp. The number indicates the line number at which
the message is listed in the corresponding message data dump file, and
the timestamp shows the time the message was generated.
The following example shows the format of the message flow drawing:
Example A-1 Message Flow Drawing Example
File: sna1.trc Page 16 Trace started: Tue Apr 4 10:56:41.250 GMT 1995
+++++++++++++++-+
|US||SI||CP||PS HS RM SM||OL||SC PC D BM||DL||?? |
+++++++++++++++-+
. . .ASSIGN_LFSID | . . . . . . .||| $013795 10:45:48.120
. . o<-++ . . . . . . . . . .||| $013795 10:45:48.120
. . |ASSIGN_LFSID_RSP . . . . . . .||| $013815 10:45:48.120
. . ++->o . . . . . . . . . .||| $013815 10:45:48.120
. . . . |.CREATE | . . . . . . .||| $013835 10:45:48.120
. . . . |o<------+ . . . . . . .||| $013835 10:45:48.120
. . .MU(MU_BIND_RQ_SEND)RQD1. . . . . .||| $013845 10:45:48.120
. . o<-----+--------+ . . . . . . .||| $013845 10:45:48.120
. . |MU(MU_BIND_RQ_SEND)RQD1,PI . . . . .||| $013900 10:45:48.310
. . +------+------------------->o . . . .||| $013900 10:45:48.310
. . . . |. . . . . |DLC_MU . . .||| $014010 10:45:48.310
. . . . |. . . . . +-->o . . .||| $014010 10:45:48.310
. . . . |. . . . . . |DLC_MU . .||| $014065 10:45:48.310
. . . . |. . . . . . +------>o .||| $014065 10:45:48.310
Message Data Dump
The first few lines of the message data dump file contain identification
and field alignment information about the running system. This
information is used only by SNAplus2 support personnel.
For each message, the file includes header information about the source,
destination, and type of the message, followedby a hexadecimal listing of
the message data. You have the choice of three levels of detail for the
message data: