|
|
|
How to Perform an Event Trace in Reflection
Technical Note 1374
Last Reviewed 26-May-2005
Applies To
Reflection for HP version 10.0 or higher
Reflection for UNIX and OpenVMS version 10.0 or higher
Reflection for ReGIS Graphics version 10.0 or higher
Summary
Technical Note 1374
Last Reviewed 26-May-2005
Applies To
Reflection for HP version 10.0 or higher
Reflection for UNIX and OpenVMS version 10.0 or higher
Reflection for ReGIS Graphics version 10.0 or higher
Summary
This technical note describes how to generate a Reflection event trace to use for your own troubleshooting purposes or when working with a support technician. An event trace captures communications activity between the PC and the host including keystrokes, commands, and menu and dialog box selections.
Generating an Event Trace
When generating an event trace file, it is best to start one or two screens before your problem occurs. Additionally, it may be helpful to record your login results.
To keep your user name and password secure, start the trace just after you enter the password, but right before you press Enter to log on. Login results will be recorded, but your user name and password will not.
To capture events to a file:
- Start the trace. Click Connection > Trace > Start Trace.
- In the Save Trace Events dialog box, specify a name for the event file.
Tip: If you already have spoken with a support technician, use your Service Request number as the name of your event trace file.
- Click Save. A bug icon appears in the Reflection status bar.
- Perform the actions that illustrate the problem you want recorded in the event file.
Note: You can use the Annotate feature to add comments to your trace file while taking a trace. Inserting comments into the trace file makes it easier to locate the problem when reading the trace file. To insert an annotation, follow the steps below:
- When the problem you are tracing occurs, immediately click Connection, point to Trace, and then Click Annotate.
- In the "Add the following comment to a trace or recorded macro" field, type your comment. If you are working with Technical Support on this issue, please enter a description of the symptoms and the expected behavior.
The maximum character limit for this field is 80 characters. If you need more space, please use multiple Annotate entries.
- Click OK.
- Stop the trace. Click Connection > Trace > Stop Trace.
Creating an Event Trace Report
Once you have captured the events leading up to a problem, you can print a report of the event trace to either a printer or a disk. You then can study this report and perhaps resolve the problem yourself.
If you are unable to resolve the problem yourself, proceed to the next section for instructions on sending the event trace report to Technical Support.
To create an event trace report:
- Start the trace. Click Connection > Trace > Process Trace.
- In the Process Event Trace dialog box, select Generate report. Verify that Traditional is selected as the String syntax. Click OK.
- In the Open Events dialog box, select the event trace file you want to associate with the report. Click Open.
- Specify a name for the event trace report file, and then click Save.
By default, the report is saved with a .txt file extension.
The event trace report is saved to the User folder in your Reflection program folder. To view the event trace report, open it in a text editor, such as WordPad.
Note: If you used the Annotation feature, the annotation comments are preceded by the notation: keyboard: <Annotate key>.
Sending an Event Trace to Attachmate
If you are already working Technical Support, upload the .rev and .txt event trace files to http://upload.attachmate.com and notify the technical support engineer.
