The PASSPORT trace feature is designed to assist in the diagnosis of problems that can occur during communications and terminal emulation. Information captured in a trace file can be analyzed by the Rocket technical support and programming staff to assist with problem resolution.
PASSPORT supports four types of tracing:
Data Stream Trace - This type of trace is helpful in resolving problems involving the SNA BIND attributes, IND$FILE file transfer, host printing, HLLAPI and other problems involving the TN3270, TN5250, VT, SCO ANSI or Wyse data stream.
Low Level Trace - This type of trace is helpful in resolving problems involving the establishment of a connection or problems that deal with the actual communication device driver.
HLLAPI Trace - This type of trace is helpful in resolving problems with HLLAPI applications.
FTP Trace - This type of trace is helpful in resolving problems using the Transfer>Send/Receive menu commands and FTP is selected as the file transfer method.
In addition to these four types of the trace files, the PASSPORT FTP Client also has its own tracing facility.
To run one or more traces:
Log off your host session.
Close the session using the Communication>Disconnect menu command.
Enable the traces you want to run using the Communication>Diagnostics dialog box.
Reestablish the session using the Communication>Connect menu command.
Log on to your mainframe and perform your terminal emulation activities.
Once you reach the point of failure, log off and exit PASSPORT.
Copy the trace files to another folder or rename them. All traces are located in the My Documents/Zephyr/Traces folder.
Note: Your trace files will be overwritten if you restart your PASSPORT session.
Your trace files will be found in the following folders:
The Data Stream Trace file is called TRACE_xx.log (where xx is equal to the ASCII value of the HLLAPI short name for the session) and is located in the My Documents/Zephyr/Traces folder. For example, the data stream trace for session A would be called TRACE_41.log.
The Low Level Trace file is called TRACELL_xx.log (where xx is equal to the ASCII value of the HLLAPI short name for the session) and is located in the My Documents/Zephyr/Traces folder. For example, the low level trace for session B would be called TRACE_42.log.
The HLLAPI Trace file is called EHTRACE.log and is located in the My Documents/Zephyr/Traces folder.
The FTP trace file is called FTPTRACE_xx.log and is located in the My Documents/Zephyr/Traces folder. For example, the FTP trace for session C would be called FTPTRACE_43.log.
Note: The session letter is the HLLAPI short name and is displayed in the upper left part of the Window title bar of the PASSPORT session.
To view the trace files:
All of the trace files are ASCII text data and may be viewed with Notepad, WordPad, or some other text-based editor.
To send your trace files to Rocket Technical Support:
First, submit an issue to Rocket technical support at http://www.rocketsoftware.com/support. This ensures that we can track your problem and route it to the correct support technician.
Next, email the trace file or files along with a detailed description of the problem to support@rocketsoftware.com. Also, email any screen shots or other helpful information.