|
|
|
Performing a Trace in Reflection for IBM 2008 or 2007
Technical Note 2228
Last Reviewed 13-Nov-2008
Applies To
Reflection Standard Suite 2008
Reflection for IBM 2008
Reflection for IBM 2007
Summary
Technical Note 2228
Last Reviewed 13-Nov-2008
Applies To
Reflection Standard Suite 2008
Reflection for IBM 2008
Reflection for IBM 2007
Summary
While troubleshooting a Reflection for IBM 2008 or 2007 problem, technical support may request that you obtain one or more traces. This technical note describes how to generate the following Reflection for IBM 2008 or 2007 traces: Host Data, Command, and HLLAPPI.
This note is organized into the following sections:
Generating a Host-Data (*.HST) or Command (*.CMD) Trace
A host-data trace captures information passed between a terminal, or printer, and the host during a 3270 or 5250 session. This type of trace is useful when a host connection is working, but the terminal or printer session does not behave as expected. For instance, a host-data trace would be useful when troubleshooting problems with colors, cursor movements, print job formatting, or IND$FILE transfer problems (for 3270 sessions). Host traces are not useful when a connection to the host cannot be established.
Note: HST traces capture both *.HST and *.RIT data.
Command traces capture actions within Reflection for IBM 2008 or 2007. An action taken, such as clicking a button or entering text, each represents an individual command. Command traces are useful in determining if commands are correct in a script, macro, or program using OLE automation.
Command traces also can be used to determine which command to use when writing a script. Use a text editor to view the command trace and determine which commands are needed to accomplish the task.
Follow the steps below to generate a host-data or command trace.
- In the Reflection Workspace, open or create a new session document.
- On the Tools ribbon, from the Tracing group, click Start Trace.
- Specify a name for the trace file. Save as type:
- Host Data (*.HST)
- Commands (*.CMD)
Note: If you have spoken with a support technician about this issue, you can use your call ID number as the name of your trace file.
- Click Save. "Tracing started…" will display in the Reflection status bar, indicating the trace is active.
- Perform the actions that reproduce the problem you want recorded in the trace.
- To end the trace, click Stop Trace from the Tracing group.
To upload the file to Technical Support, see http://upload.attachmate.com.
Generating a HLLAPI Trace (.TMP)
HLLAPI is an API specified by IBM for automating terminal tasks. HLLAPI traces are available in Reflection for IBM 2008 or 2007. A HLLAPI trace will enable you to see the HLLAPI calls the application is making, including return codes.
Follow the steps below to generate a HLLAPI trace.
- Click Start. In the Start Search box, type win.ini and press Enter. This will open your Win.ini file in Notepad.
- Add the following two lines to the end of the Win.ini file:
[Reflection HLLAPI]ExtTraceOn=1- Save the Win.ini file (click File > Save).
- In the Reflection Workspace, open or create a session document to connect to your IBM host, and start the HLLAPI application. Perform the actions that you want recorded in the trace.
- Close the HLLAPI application.
- The trace file is automatically named Hll*.TMP. The * is a randomly generated hex number. The file is located in the PC's TEMP directory, if a TEMP directory has been defined in the System Environmental settings. Otherwise, it is located in the root Windows directory.
- Re-open the Win.ini file (see step one) and set the ExtTraceOn setting to zero:
[Reflection HLLAPI]ExtTraceOn=0To upload the file to Technical Support, see http://upload.attachmate.com.
