Because an event trace captures all communications activity, a trace report can grow to many pages. The best way to create an event trace is to narrow down the events to only those that reproduce the problem.
For example, if you're having a problem with a specific host application, it's usually not necessary to capture everything from your initial host login. Instead, start tracing just before you start the host application. After the problem has been demonstrated, stop tracing.
To create an event trace:
-
On the Help menu, click Trace and then click Start Trace. The Save Trace Events dialog box opens.
-
Enter an event trace report file name. The default is trace.evt.
-
Click Save. If a file by that name already exists, Reflection asks if you want to overwrite the file.
-
Perform the required actions to demonstrate the problem. While event tracing is on, a bug icon appears in the status box for the session window.
-
If available for this session type, the technical support team may ask you to annotate the trace file to help them focus on the steps at which the problem occurs. Click Annotate on the Trace menu. The Get Mark Name dialog box opens. Enter a brief description of the event in the box, click OK, and continue tracing.
- As soon as the problem has been demonstrated, click Stop Trace on the Trace menu.