If you are troubleshooting problems with a printer session, technical support may request that you obtain one or more traces.
To create a trace file for a printer session
Open a printer session.
If you are connected to the host, disconnect (> ).
From themenu, chose > .
Select the trace file type.
Trace File Type
Host-data trace (*.hst)
Captures information passed between a terminal or printer session and the host. This type of trace is useful when a host connection is working, but the terminal or printer session does not behave as expected.
Host traces are not useful when a connection to the host cannot be established.
Command trace (*.cmd)
Captures actions within Reflection. Each action, such as clicking a button or entering text, represents an individual command. Command traces are useful in determining whether commands are correct in a script, macro, or program using OLE automation. Command traces can also be used to determine which command to use when writing a script.
Use a text editor to view the command trace, and to determine which commands are needed to accomplish the task.
Specify a name for the trace file.
NOTE:If you have spoken with a support technician, use your call ID number as the name of your trace file.
A bug symbol appears in the status bar, indicating that the trace is active.
Connect to the host.
Perform the actions that reproduce the problem you want recorded in the trace.
To end the trace, go to> > .
Upload the trace file as a binary file to http://upload.attachmate.com. If the problem relates to a service request you are currently working on with a technician, include the Micro Focus service request number with the trace and let the technician know when the file is uploaded.