User guide

152 DC 900-1333Q
Freeway User Guide
MSGMUX trace is accessible through the Freeway interactive menu. To turn tracing on,
login to the Freeway and select:
"4) Trace Functions (Trace Disabled)", then
"2) Turn MSGMUX Trace On"
Then start your client program and run your test. While the test is running, trace data
is stored in a buffer in Freeway memory. The trace uses a circular buffer, and new data
coming in will eventually overwrite the oldest data. Therefore you can test as long as you
want and not have to worry about the trace buffer filling up. As soon as the item of
interest has occurred (data sent, data received, an error message received, etc.), go back
to the interactive menu and in the Trace Functions menu select:
"4) Process Trace Data"
You will be prompted for a trace file name in which case you can type in a filename such
as "trace1.txt". Then you will be asked to select between TSI and DLI trace level. Always
select "2" for DLI trace level because you get more information for debugging. The trace
file will be generated in the /tmp/ subdirectory on the Freeway (or if your Freeway is
configured to boot from the network, the trace file will be in the directory where the
Freeway booted from). The trace file is in text format. You should be able to use FTP
(ASCII transfer) to retrieve it from the Freeway, or you can just go into the BSD shell
and use the vi editor to view the file in the /tmp/ directory.
The trace file contains a list of events separated by dashed lines. The latest event is
always the last event in the file. A sample trace event is shown below: