Exchange/SNA Manual

Exchange/SNA Trace Server Messages
Exchange/SNA Messages
104700 Tandem Computers Incorporated A–13
SNCI53E FILE filename IS NOT A TRACE FILE.
Problem. You have entered a DUMP command in which the specified file is not a trace
file.
Solution. Enter the DUMP command again, and specify a trace file.
SNCI54E TRACE FILE filename IS EMPTY.
Problem. The specified trace file is empty. Either no communications occurred over the
line, or the TRACE STOP command has not been executed and all trace records are
still in the trace server's buffers.
Solution. Use the TRACE STOP command, and stop the trace server. Try the DUMP
command again.
SNCI55E TRACE FILE filename FORMAT IS BAD configuration-record
/ trace-information-block .
Problem. The DUMP command is unable to display the trace file. This may be due to
the trace server being stopped in some way other than the TRACE STOP command.
This message can also occur if the trace file was created on a system running a
different version of Exchange/SNA from the system on which you are trying to read
the trace file.
Solution. Perform the trace operation again, and be sure to end it by using the TRACE
STOP command. Also, try reading the trace file on the same system on which you
created the file.
SNCI56 trace-header.
Comment. This message is the heading for the output produced by the dump
command