EM3270 Manual

Installation and Configuration Guidelines
1-16 110332—Tandem EM3270 Manual
Product Components and Operation
Installation and Configuration Guidelines
The following is a list of installation and configuration guidelines. As guidelines, these
procedures are not required but do help to prevent complications.
•
Install the EM3270 emulator package by copying the object modules and the file
EMMSGS to the $SYSTEM.SYSTEM volume.
•
Use EMCOM commands to configure the emulator and terminals. When you use the
EM3270 emulator with Pathway, assign a priority for the EM3270 emulator higher
than that of the TCPs (terminal control processes) that will be accessing the
EM3270 emulator process.
•
Configure Pathway, TR3271, SNAX/XF, SNAX/CDF, SNAX/APN, and the spooler
using their respective command interfaces as described in their manuals.
The SET TCP TERMBUF value for Pathway must be less than or equal to 4000
because the emulator reads no more than 4000 characters from the Tandem
application. Include the following command when you configure Pathway:
SET TCP TERMBUF 4000
The RSIZE (record size) modifier that you specify in the SYSGEN process for
TR3271 determines the size of the largest block that you can receive from the IBM
host. It is usually set to 1920 because the screen displays 1920 characters. However,
some applications consist of many fields that require field attribute information to be
sent from the IBM host along with the data. These applications require that you
specify a value greater than 1920 but no more than 4096.
•
Optionally, install the emulator keycap labels on the terminal keyboard.
•
Optionally, install the EM3270 emulator template on a terminal during an emulator
session. Section 2, “Keyboard Mapping,” describes terminal keyboard use with the
emulator.
Columns 2-5: A four-digit hexadecimal number identifying the particular message
Column 6: Blank
Column 8: Blank, and the message text begins in column 9. The text in event (K)
records is for clarity only.
Note. The EMMSGS file is considered part of the EM3270 product. Future releases of
EM3270 might invalidate existing copies of EMMSGS. Therefore if modifications are
introduced into EMMSGS, a new product release might require their re-introduction.