Launch the appropriate BlueZone Display or Printer emulator. Disconnect your session if necessary. You should always start your trace with your session disconnected.
On the BlueZone MenuBar, choose Session:Configure:Configure, then click the Trace Tab.
In Trace Options, verify that only the Trace Sockets Interface and Trace RUI Interface boxes are checked.
NOTE Only
check the Trace SSL Connection
box if you are troubleshooting an SSL related issue.
In the Trace File edit box, make sure that there is a valid path and trace file name for the trace data to be written to. You can use any file name you wish. The file extension should be .trc.
CAUTION! This
must be a valid path or the trace feature will not work.
In the Trace Viewer edit box, make sure that you have a valid path to a program that will read your trace file. Notepad or Wordpad will work fine.
Click the Start Trace button, then click OK and OK.
Connect your host session and perform any steps necessary to reproduce the problem or perform the particular function that you are tracing. Once this is accomplished, proceed to the next step.
On the BlueZone MenuBar, go to Session:Configure:Configure, click the Trace Tab and click the Stop Trace button.
View the trace file that you just created by clicking the View Trace button. Trace files can be viewed in Notepad or Wordpad. This step helps insure that you have indeed created a valid trace file. If the trace file is extremely short or does not appear to contain any valid data, try running another trace and compare the results.
NOTE When
Emailing trace files for evaluation, please send them in their native
format. Do
not embed them in Word documents or change the file into any other format.
Changing
them will make it impossible for us to evaluate them properly.
TIP If
the trace files are very large, it’s okay to zip them up using a standard
zipping utility like WinZip.