The Design Tool provides the following types of tracing to aid you in the modeling process:
Host Emulator tracing captures negotiations between entities in your model and captures the data sent to the host at the transport level. When you use the Host Emulator, these .hetrace files are played back to simulate the host environment without having a direct connection to the host. This feature is helpful if you plan to use the Host Emulator as a model testing tool during production and for offsite model development.
To create .hetrace files for the Host Emulator:
Tip: On the Connection menu, point to Host Emulator Recording, and then click Screen Traces Status to check whether or not all operations in your model have been traced.
Datastream tracing interprets 3270 and 5250 datastreams by capturing data transmissions to and from the host during a live connection. Tracing is intended primarily for diagnostic purposes. Use the model debug messages feature for more options on interpreting the datastream.
To create a datastream trace (.hst file):
\<VHI install directory>\etc\tracingfolder.
To play back the datastream trace:
The trace navigation displays on the Terminal window, which enables you to see the sequencing of host writes to the terminal screen to track navigation in offline mode.
Note: Playing back a trace does not redisplay the user's input and does not require a live host connection.
Debug tracing is a more intricate form of configuration tracing that is used to help debug the product. This form of tracing should only be used if the other forms of tracing have failed. Make sure to contact a technical support representative before proceeding with a debug trace.
The following provides some possible reasons to create a debug trace:
Note: A trace configuration file (.cfgtrc file) and an actual trace file (.trace file) results from a debug trace.