|
|
|
|
The snatrcfmt command-line utility enables you to format binary trace output into one or two text files. It can be used either for line tracing or for internal tracing, with slightly different options in each case.
For line tracing, you can format the binary trace output into only one text file, a message data dump file.
For internal tracing, you can format the binary trace output into either a message data dump file (see Message Data Dump) or a message flow diagram (see Message Flow Drawing), or both. The message flow diagram is a summary drawing that shows the message flows between components.
If your binary trace file contains both line tracing and internal tracing, both trace types are included in the output file.
The syntax of the command to run the trace format utility for line tracing is:
snatrcfmt [-f filename ] [-o output_file_base] [ -S | -D] [-m] [ -l] [-M]
Specify the following options and parameters:
Use this option to specify the name of the input binary trace file. If you do not use this option, snatrcfmt uses sna1.trc as the default.
The base name to be used for the output file. SNAP-IX adds the extension .dmp for the message data dump file. If you do not use this option, SNAP-IX uses the files snatrc.dmp as the output file.
Produce a summary trace file, with only one line of tracing for each message. If the trace file includes detailed SDLC tracing, this suppresses Information fields and includes only address and control fields.
Produce a more detailed report of each message.
For each message, show the time interval since the last message instead of the absolute time. If you do not select this option, each message shows the time and date at which it was written to the file.
Suppress detailed SDLC tracing if it is included in the trace file (but include standard SDLC line trace). If you do not select this option, any detailed SDLC tracing from the trace file is included in the output.
If detailed SDLC tracing is included in the file, decode the frames in Modulo 128 format. If you do not select this option, detailed SDLC tracing is decoded in Modulo 8 format.
The syntax of the command to run the trace format utility for internal tracing is:
snatrcfmt -i [-m] [ -f filename] [-o output_file_base] [options]
Specify the following options and parameters:
Use this option to indicate that snatrcfmt is being used to format internal tracing.
For each message, show the time interval since the last message instead of the absolute time. If you do not select this option, each message shows the time and date at which it was written to the file.
Use this option to specify the name of the input binary trace file. If you do not use this option, snatrcfmt uses sna1.trc as the default.
The base name to be used for the output files. SNAP-IX adds the extension .drw for the message flow drawing and .dmp for the message data dump. If you do not use this option, SNAP-IX uses the files snatrc.drw and snatrc.dmp as the output files.
The options indicated above by options are as follows:
Only create the message data dump file.
The following options are used only for the message data dump file. Do not specify any of these options with the option.
Include a listing of each message as it is sent by one component and received by another. If you do not specify this option, SNAP-IX includes only sent messages.
Include only raw hexadecimal data for each message; do not attempt to interpret the message data.
Include verbose formatting for each message. SNAP-IX lists the data in three columns: hexadecimal, interpreted as EBCDIC, and interpreted as ASCII (so that a text string in the message data appears as readable characters either in the EBCDIC or in the ASCII column, according to its character set). In addition, SNAP-IX interprets many of the fields in the message data and prints out the interpretation as readable text.
As for , but with a detailed listing of the fields in the RH and TH of each message.
Do not specify more than one of the options , , and . If you do not specify any of these options, SNAP-IX includes the hexadecimal, EBCDIC, and ASCII listing but interprets only a limited number of message fields.
Only create the message flow drawing.
The following options are used only for the message flow drawing file. Do not specify any of the following options with the option.
Compress a group of components into one column so that messages between these components do not appear in the drawing. Specify one or more of the following separated by commas:
Compress control point into one column.
Compress LU 6.2 components (CPI-C and APPC) into one column.
Compress LU 0-3 components into one column.
Compress all components in the APPN protocol code [including the CP, LU, and Old LU (OL) groups] into one column so that internal messages within the node are not shown.
No compression. Do not specify any other component options if you select this option.
Compress all 3270 emulation program and RJE workstation program and API components into one column.
Compress all internal components (except DLCs) outside the APPN protocol code into one column.
Compress all DLC components into one column.
If you do not use this option, the default is USER,NODE. If you use both of the options and , you must specify before .
Do not display a column in the drawing for one or more individual components.
Any messages flowing to or from these components are shown in the
unknown
column, so you can view detailed information without having
to display all the components in a group. For example, you can view the PS
and HS components but suppress the RM component.
Specify each component by using the two-character component identifiers as listed in Message Flow Drawing. To specify multiple components, separate them with commas.
Note that you specify component groups with the option, but individual components with the option.
If you use both of the options and , you must specify before .
Use a page length of nn lines for the message flow drawing (nn is a decimal number). SNAP-IX separates pages with a page break character and includes the column headers at the top of each page.
Do not specify both of the options and . If you do not use either option, the default is
Produce output as a single page (no page breaks and column headers only at the start of the data).
Do not specify both of the options and . If you do not use either option, the default is
The snatrcfmt utility generates text output in either or both of the following formats:
A drawing showing the messages flowing between different SNAP-IX components (this format does not apply to line tracing).
A listing of the data in each trace message.
Each column in the message flow drawing corresponds to a particular SNAP-IX component or to a group of components. The heading of each column shows a one-character or two-character abbreviation for the name of the component or group. Each line in the file corresponds to a particular message flowing between SNAP-IX components.
The default options group all 3270 emulation program, RJE workstation program, and API components into one column, and all components in the APPN protocol code into another column. The only messages shown are those flowing between the 3270 emulation program and the RJE workstation program and API components and the node, and those flowing between the node and DLC components. The drawing also includes an individual column for each of the DLC components. If required, you can break these groups down into individual components to show a more detailed drawing; the additional detail is provided mainly for use by SNAP-IX support personnel.
Formatted output varies depending upon the options you select. Because support personnel sometimes use different options, always provide them with the original binary trace files.
Node line tracing is not shown in message flow drawings because the data being traced is flowing between SNAP-IX and a remote component (which is not shown in the diagram) rather than between two SNAP-IX components.
The component groups shown in the message flow drawing are as follows:
US
The following 3270 emulation program and RJE workstation program and API components:
AL
APPC library
CL
CPI-C library
CV
CSV library
FL
FM library (used by 3270, RJE, and LU0)
RL
RUI (LUA) library
ML
MS library
NL
NOF library
CD
Config daemon
LD
Log daemon
SD
SNA daemon
RD
RCF daemon
RS
Remote system (client-server messages)
SIX
The following internal components (except DLCs) outside APPN protocol code:
PM
Path manager
SV
Service manager
AP, TP
APPC internal components
LO
Log internal component
M
MS internal component
N
NOF internal component
L1, L2
LUA internal components
FM
FM internal component
CP
Control point, which consists of:
CM
Session connector manager
NF
NOF node component
AM, AS
Address space manager
CS
Configuration services
DS
Directory services
MD
Multiple Domain Support (MDS) component of management services
MS
Management services
SS
Session services
TR
Topology and routing services
DR, ES
Dependent LU Requester (DLUR)
LU
LU 6.2, which consists of:
PS
Presentation services
HS
Half-session
RM
Resources manager
SM
Session manager
OL
Old LU (LU 0-3), which consists of:
RU
RUI (LUA)
CH
Conventional half-session
LM
LU manager
PU
PU manager
PX
PU concentration
NO
The following node components (components of APPN protocol code):
BM
Buffer manager
D
DLC component within a node
PC
Path control
SC
Session connector
HP, RT
High Performance Routing
DL
DLC components, which consist of:
L, LL, MT, M1
LLC2 driver
SL
SDLC driver
S2
SDLC device driver
HM
SDLC hardware interface
QL
QLLC driver
X2
X.25 interface (NLI)
IP
Enterprise Extender (HPR/IP)
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
??.
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:
File: sna1.trc Page 16 Trace started: Tue Apr 4 10:56:41.250 GMT 2000 +--++--++--------------++--++--------------++--+ |US||CP||PS HS RM SM||OL||SC PC D BM||GG| +--++--++--------------++--++--------------++--+ . .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
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 SNAP-IX support personnel.
For each message, the file includes header information about the source, destination, and type of the message, followed by a hexadecimal listing of the message data. You have the choice of three levels of detail for the message data:
Uninterpreted hexadecimal data
Hexadecimal data interpreted as EBCDIC and as ASCII
Hexadecimal data interpreted as EBCDIC and as ASCII, with text interpretations of many of the message fields
If the message data dump is from a trace file containing line trace and including detailed SDLC tracing, the following additional information is included for an SDLC frame:
TX
or RX
, indicating whether
the frame is being transmitted or received by SNAP-IX
Decoded versions of the address and control fields (and Information fields if they are present).
The following examples show the format of the message data dump for line tracing:
------------------------------------------------ 16:54:33.950 BST 20 Apr 1999
SND>> CNCT_OUT REQ ETHER0.ETSAP0.ETHL0
------------------------------------------------ 16:54:33.950 BST 20 Apr 1999
SND>> CNCT_OUT REQ TOKEN0.TRSAP0.TRL0
------------------------------------------------ 16:54:33.950 BST 20 Apr 1999
<<RCV CNCT_OUT RSP OK ETHER0.ETSAP0.ETHL0
------------------------------------------------ 16:54:33.950 BST 20 Apr 1999
SND>> XID (NULL) ETHER0.ETSAP0.ETHL0
------------------------------------------------ 16:54:33.960 BST 20 Apr 1999
<<RCV CNCT_OUT RSP OK TOKEN0.TRSAP0.TRL0
------------------------------------------------ 16:54:33.960 BST 20 Apr 1999
SND>> XID (NULL) TOKEN0.TRSAP0.TRL0
------------------------------------------------ 16:54:33.960 BST 20 Apr 1999
<<RCV XID (NULL) ETHER0.ETSAP0.ETHL0
------------------------------------------------ 16:54:33.960 BST 20 Apr 1999
SND>> XID FMT:3 ID:01100002 ESI:PRE_NEG LR:SEC ETHER0.ETSAP0.ETHL0
XID 32540110 00020000 000AD100 00000000 ..........J..... 2T..............
00010B41 00040900 00000007 000E0AF4 ...............4 ...A............
C1D7D7D5 4BD4D6D6 D5102900 28110C08 APPN.MOON....... ....K.....).(...
04F0F6F0 F0F0F609 06E2D5C1 E2E3C1D9 .060006..SNASTAR .............`..
03084011 0FE2D5C1 E2E3C1D9 40D3C9D4 .. ..SNASTAR LIM ..@.........@...
C9E3C5C4 ITED ....
------------------------------------------------ 16:54:33.970 BST 20 Apr 1999
<<RCV XID (NULL) TOKEN0.TRSAP0.TRL0
------------------------------------------------ 16:54:33.950 BST 20 Apr 1999
SND>> CNCT_OUT REQ ETHER0.ETSAP0.ETHL0
IPS: 00000000 4554484C 30202020 010000EE .......<........ ....ETHL0 ....
01000008 00000007 000629EA BC670400 ................ ..........)..g..
00000000 00000000 00000000 00000000 ................ ................
00000000 00000000 040900FF 8100009C ...........@a... ................
FFFFFFFF 00020040 00060000 00000000 @@@@... ........ .......@........
00000000 00000000 00000000 00000000 ................ ................
00000000 00000000 00000000 00000000 ................ ................
0000000A 0005000A 00051388 13880064 ...........h.h.. ...............d
000A001E 001E0003 ........ ........
------------------------------------------------ 16:54:33.950 BST 20 Apr 1999
SND>> CNCT_OUT REQ TOKEN0.TRSAP0.TRL0
IPS: 00000000 54524C30 20202020 010000F0 ......<........0 ....TRL0 ....
50182F10 00000007 08005AFD 90B30400 &.........!..... P./.......Z.....
00000000 00000000 00000000 00000000 ................ ................
00000000 00000000 1009000D 810000A5 ............a..v ................
000E0007 00020040 00050000 00000000 ....... ........ .......@........
00000000 00000000 00000000 00000000 ................ ................
00000000 00000000 00000000 00000000 ................ ................
0000000A 0005000A 00051388 13880064 ...........h.h.. ...............d
000A001E 001E0003 ........ ........
------------------------------------------------ 16:54:33.950 BST 20 Apr 1999
<<RCV CNCT_OUT RSP OK ETHER0.ETSAP0.ETHL0
IPS: 00000001 4554484C 30202020 010000EE .......<........ ....ETHL0 ....
410000EF 00000007 000629EA BC670400 ................ A.........)..g..
00000000 00000000 00000000 00000000 ................ ................
00000000 00000000 040900FF 0100011E ...........@.... ................
FFFFFFFF 00020040 00060000 00000000 @@@@... ........ .......@........
00000000 00000000 00000000 00000000 ................ ................
00000000 00000000 00000000 00000000 ................ ................
0000000A 0005000A 00051388 13880064 ...........h.h.. ...............d
000A001E 001E0003 ........ ........
------------------------------------------------ 16:54:33.950 BST 20 Apr 1999
SND>> XID (NULL) ETHER0.ETSAP0.ETHL0
IPS: 410000EF 00020000 ........ A.......
------------------------------------------------ 16:54:33.960 BST 20 Apr 1999
<<RCV CNCT_OUT RSP OK TOKEN0.TRSAP0.TRL0
IPS: 00000001 54524C30 20202020 010000F0 ......<........0 ....TRL0 ....
410000F1 00000007 08005AFD 90B30400 ...1......!..... A.........Z.....
00000000 00000000 00000000 00000000 ................ ................
00000000 00000000 1009000D 0100012D ................ ...............-
000E0007 00020040 00050000 00000000 ....... ........ .......@........
00000000 00000000 00000000 00000000 ................ ................
00000000 00000000 00000000 00000000 ................ ................
0000000A 0005000A 00051388 13880064 ...........h.h.. ...............d
000A001E 001E0003 ........ ........
------------------------------------------------ 16:54:33.960 BST 20 Apr 1999
SND>> XID (NULL) TOKEN0.TRSAP0.TRL0
IPS: 410000F1 00020019 ...1.... A.......
------------------------------------------------ 16:54:33.960 BST 20 Apr 1999
<<RCV XID (NULL) ETHER0.ETSAP0.ETHL0
IPS: 010000EE 80370070 ........ .....7.p
------------------------------------------------ 16:54:33.960 BST 20 Apr 1999
SND>> XID FMT:3 ID:01100002 ESI:PRE_NEG LR:SEC ETHER0.ETSAP0.ETHL0
IPS: 410000EF 00025400 ........ A.....T.
XID decode:
XID format type = 03
Node type = 02
XID length = 54
block/ID number = 01100002
. . @ .
. . . .
Bytes 8-9 = 000A
Init self may be sent to the XID sender
XID sender supports independent-PLU session partners
This node can generate BIND PIU segments
This node can receive BIND PIU segments
ACTPU for an SSCP-PU session requested
The XID sender is not a network node
CP services not requested or supported
CP-CP sessions not supported on this TG
Secondary initiated non-activation exchange supported
XID sender does not supported CP name change
Prenegotiation exchange
Byte 10 = D1
Adaptive BIND pacing as a BIND sender supported
Adaptive BIND pacing as a BIND receiver supported
This TG is operative
XID sender supports receipt of ACTPU containing PU cap cv
XID sender is not a peripheral border node
Adaptive pacing on both, negotiable
Byte 15 = 00
XID sender does NOT support parallel TGs
TG number = 00
DLC type = 01
DLC type is SDLC
DLC data length = 0B
Byte 19 = 41
XID sender can be an ABM combined station
XID sender not already using short-hold mode
Short-hold mode not supported
Sender is secondary link station (non-negotatiable)
Link-station transmit-receive capability: two-way simultaneous
Byte 20 = 00
XID sender is not the sender of a nonactivation XID
Maximum BTU length = 409
Byte 23 = 00
SNA link profile
Byte 24 = 00
SIM and RIM not supported
I-frame number = 07
XID 32540110 00020000 000AD100 00000000 ..........J..... 2T..............
00010B41 00040900 00000007 000E0AF4 ...............4 ...A............
C1D7D7D5 4BD4D6D6 D5102900 28110C08 APPN.MOON....... ....K.....).(...
04F0F6F0 F0F0F609 06E2D5C1 E2E3C1D9 .060006..SNASTAR .............`..
03084011 0FE2D5C1 E2E3C1D9 40D3C9D4 .. ..SNASTAR LIM ..@.........@...
C9E3C5C4 ITED ....
------------------------------------------------ 16:54:33.970 BST 20 Apr 1999
<<RCV XID (NULL) TOKEN0.TRSAP0.TRL0
IPS: 010000F0 5A000000 ...0!... ....Z...
|
|
|
 |
|