EM3270 Manual

Tandem EM3270 Manual—110332 5-1

Problem Solving

This section provides guidelines for solving problems that may occur in the EM3270

emulator environment.

Solving Common Problems

In general, most problems you might encounter during initial system configuration can

be traced back to an SCF error or the SYSGEN process. Before continuing with the

troubleshooting procedures, ask the computer system manager to recheck the SCF

procedures.

Using the Log

Use the log file that you defined at the beginning of the emulator session as a major

source of troubleshooting data; error messages issued during the emulator session are

recorded in it. By examining the contents of the log file and looking up the

interpretation of the messages it contains, you can quickly locate the source of the

problem. The messages are described in Appendix J.

Writing a Trace File

Problems can occur that you will not be able to solve using only error messages and

their interpretations. In those cases, you should create a trace file that you can examine

or send to support personnel for analysis.

The EM3270 emulator has a trace capability that writes a file containing the data stream

between the terminal or printer and the IBM host or the Tandem application it

communicates with; the trace is done for that specific task only.

Using EMCOM to enable the trace, type in the following command:

TRACE {file-name | task-number}, ON -- Turn trace on

Executing the TRACE command starts tracing the data stream for the device identified

by file-name or task-number. The trace file is created on the default volume and

subvolume using file name EMTRACnn (nn is the task number of the device task). The

command opens the file and displays:

STATUS *1124* TRACE STARTED ON FILE:

\AUSTIN.$SERVE.HT3270.EMTRAC01

The default trace file name can be overridden by using the SET command:

SET TRACFILE file-name

When the trace operation has been active long enough to write enough data to identify

the problem, type in the following command:

TRACE {file-name | task-number}, OFF -- Turn trace off