|
|
IBM 3270 display terminals are among the computing community's most widely implemented and emulated environments for host-based computing. This chapter will help you understand the TN3270 terminal emulation environment and how to use and create files that will allow terminals connected to the protocol translators to be used for TN3270 operation. For a complete description of the commands in this chapter, refer to the chapter "TN3270 Configuration Commands" later in this publication. For information about establishing TN3270 connections, refer to the Cisco Access Connection Guide.
The TN3270 terminal emulation software is based on software developed at the University of California, Berkeley. This software allows any terminal to be used as an IBM 3270-type terminal. Users with non-3270 terminals can take advantage of the emulation capabilities to perform the functions of an IBM 3270-type terminal. Specifically, Cisco's implementation supports emulation of an IBM 3278-2 terminal providing an 80 by 24 display.
True IBM 3270-type terminals use a character format referred to as extended binary-coded decimal interchange code (EBCDIC). EBCDIC consists of 8-bit coded characters and was originally developed by IBM. Emulation is made possible by termcap and curses functions developed by Berkeley UNIX system developers. These functions translate the keyboard and terminal characteristics for ASCII-type terminals into those expected by an IBM host. ASCII characters are listed in the appendix "ASCII Character Set" later in this publication.
Formally, a termcap is a two-part terminal-handling mechanism. It consists of a database and a subroutine library. The database describes the capabilities of each terminal to be supported; the subroutine library allows programs to query the database and to make use of the values it contains. For more information about defining termcaps, refer to the document termcap & terminfo, by Jim Strang, Tim O'Reilly, and Linda Mui.
Protocol translators include a default termcap entry for Digital VT100 terminal emulation. More samples are available directly from Cisco on the ftp.cisco.com directory using the FTP file transfer utility.
TN3270 emulation capability allows users to access an IBM host without using a special IBM server or a UNIX host acting as a server (see Figure 3-1). The IBM host must directly support TCP/IP, or have a front-end processor that supports TCP/IP.
Connection to IBM hosts from LAT, TCP, and X.25/PAD environments is accomplished using the two-step translation method. This method is discussed in the chapter "Configuring Protocol Translation" in this publication and in the Cisco Access Connection Guide. In general, TN3270 support for protocol translators allows outgoing TN3270 connections only. In other words, LAT, TCP, and X.25/PAD users must first establish a connection with the protocol translator, then use the TN3270 facility from the protocol translator to make a connection to the IBM host.
Figure 3-2 shows how the keymapping and ttycap functionality on the protocol translator helps IBM hosts and non-IBM terminals communicate.
Keymaps and ttycaps have the following functionality:
At system startup, the protocol translator uses the following decision sequence when selecting a terminal emulation file, also called a ttycap:
Figure 3-3 illustrates the decision process used by the protocol translator to choose a ttycap for a specific TN3270 session.
At system startup, the protocol translator uses the following decision sequence when selecting a keyboard map file, also called a keymap:
The protocol translator uses the following criteria to determine which file to use:
Figure 3-4 illustrates the decision process used by the protocol translator to choose a keymap for a specific TN3270 session. When one of the first four priority checks fail (that is, the name specified does not match any name in the configuration file), the same rules listed for the terminal emulation file apply.
You can perform the tasks described in the following sections when making connections to an IBM host:
See the end of this chapter for examples of custom terminal and keyboard emulation files.
By default, an ASCII terminal and keyboard connected to the protocol translator emulate a Digital VT100 terminal type.
Enter the tn3270 EXEC command at the EXEC prompt to connect to an IBM host. This command makes the connection using the terminal emulation file selected and using the startup sequence priorities outlined in the section "Startup Sequence Priorities" earlier in this chapter
If the default file does not work for your terminal and keyboard type or the host that you connect to, you might be able to find a file that will work from the growing list of sample terminal emulation files created by Cisco engineers and customers. Obtain the tn3270.examples file in the ftp.cisco.com directory at Cisco Systems. Numerous emulation files are listed in tn3270.examples that allow various terminal types to emulate an IBM 3270-type terminal.
The following steps describe how to obtain a sample configuration file from the tn3270.examples file available from the Cisco ftp.cisco.com directory. These steps assume that the system configuration file is stored on a host.
Step 1 Use the FTP utility to connect to address ftp.cisco.com and log in using the anonymous FTP convention.
Step 2 Get the tn3270.examples file.
Step 3 Use a text editor or word processing application to copy the sample terminal emulation file into the configuration file.
Step 4 Load the configuration file onto the host or network. (Refer to the chapter about loading system images, microcode images, and configuration files in the Router Products Configuration Guide for more information on loading configuration files.)
These steps add new terminal emulation capability to the configuration file. Each time the system is started up, or booted, the settings in the file will be used as the default for terminal emulation.
To use a custom emulation file, you must load the emulation settings into the system configuration file. This establishes the settings in the file as the terminal and keyboard defaults and provides several ways in which the emulation settings can be used within the system, as follows:
To create a custom terminal emulation file or a custom keyboard emulation file, perform the applicable global configuration task as follows:
| Task | Command |
|---|---|
| Define a new terminal emulation file, or ttycap. | ttycap ttycap-name termcap-entry |
| Define a new keyboard emulation file, or keymap. | keymap keymap-name keymap-entry |
If you intend to use an alternate ttycap and keymap, you must assign the following two characteristics:
This information is used by the protocol translator when negotiating connections with hosts.
To assign ttycap and keymap line characters, perform one or more of the following line configuration tasks:
| Task | Command |
|---|---|
| Specify the type of terminal connected to the line. | terminal-type terminal-name |
| Specify the keyboard map for a terminal connected to the line. | keymap-type keymap-name |
To display a list of ttycap and keymap files available for use, perform the following tasks in EXEC mode:
| Task | Command |
|---|---|
| List the ttycap files available. | show ttycap [ttycap-name | all] |
| List the keymap files available. | show keymap [keymap-name | all] |
You can control the mapping of extended binary coded decimal interface code (EBCDIC) and American Standard Code for Information Interchange (ASCII) characters by performing the tasks described in the following sections:
You can create character mappings by configuring a two-way binding between EBCDIC and ASCII characters. To set character mappings, perform the following global configuration task:
| Task | Command |
|---|---|
| Create a two-way binding between EBCDIC and ASCII characters. | tn3270 character-map ebcdic-in-hex ascii-in-hex |
To return character mappings to their default settings, perform the following global configuration task:
| Task | Command |
|---|---|
| Reset character mappings to defaults. | no tn3270 character-map {all | ebcdic-in-hex} [ascii-in-hex] |
To display character mappings, perform the following task in EXEC mode:
| Task | Command |
|---|---|
| Display character mappings. | show tn3270 character-map {all | ebcdic-in-hex} |
To display the hexadecimal value of an ASCII character, perform the following task in EXEC mode:
| Task | Command |
|---|---|
| Obtain the hexadecimal value of an ASCII character. | show tn3270 ascii-hexval |
After you enter this command, type the ASCII character whose hexadecimal value you want to display.
When you create character mappings between extended EBCDIC or extended ASCII characters, you must configure the protocol translator for the correct data character bit length. The default mask used for TN3270 connections is a 7-bit mask. In certain situations, you must use an 8-bit display. When an 8-bit mask has been set by the line configuration command data-character-bits {7 | 8} or the EXEC command terminal data-character-bits {7 | 8}, you can temporarily configure the protocol translator to use the 8-bit mask by performing the following task in line configuration command mode:
| Task | Command |
|---|---|
| Temporarily configure the protocol translator to use the 8-bit mask. | tn3270 8bit display |
When you use a file-transfer protocol such as Kermit in 8-bit mode or you use 8-bit graphics, which rely on transparent mode, perform the following line configuration task to configure the protocol translator for the
8-bit mask:
| Task | Command |
|---|---|
| Configure the protocol translator to use the 8-bit mask. | tn3270 8bit transparent-mode |
The following sections provide examples that will help you define custom terminal and keyboard emulation files and will help you configure your system to use these files:
The following example allows a Televideo 925TM terminal to emulate an IBM-3270-type terminal. The file is part of the global ttycap command and is included in the system configuration file. Notice that a carriage return (^M) indicates the last character in the file.
ttycap ttycap1 \
v8|vi|tvi925|925|televideo model 925:\
:so=\EG4:se=\EG0:\
:hs:am:bs:co#80:li#24:cm=\E=%+ %+ :cl=\E*:cd=\Ey:ce=\Et:\
:al=\EE:dl=\ER:im=:ei=:ic=\EQ:dc=\EW:\
:ho=^^:nd=^L:bt=\EI:pt:so=\EG4:se=\EG0:sg#1:us=\EG8:ue=\EG0:ug#1:\
:up=^K:do=^V:kb=^H:ku=^K:kd=^V:kl=^H:kr=^L:kh=^^:ma=^V^J^L :\
:k1=^A@\r:k2=^AA\r:k3=^AB\r:k4=^AC\r:k5=^AD\r:k6=^AE\r:k7=^AF\r:\
:k8=^AG\r:k9=^AH\r:k0=^AI\r:ko=ic,dc,al,dl,cl,ce,cd,bt:\
:md=\E(:me=\E):ti=\E):te=\E(:\
:ts=\Ef:fs=\Eg:ds=\Eh:sr=\Ej:xn:\
:is=\El\E"^M\E3^M \E1 \E1 \E1 \E1 \E\
1 \E1 \E1 \E1 \E1^M
The following example allows a keyboard to emulate an asynchronous connection to an IBM 7171TM keyboard. The file is part of the keymap global configuration command and is included in the system configuration file.
keymap ibm7171 \
vt100av|vt100|vt100nam|pt100|vt102|vt125{ \
enter = '^m';\
erase = '^?'; reset = '^g'; clear = '^z' | '\EOM';\
nl = '^j'; tab = '^i'; btab = '^b';\
left = '\EOD'; right = '\EOC'; up = '\EOA'; down = '\EOB';\
home = '^h'; delete = '^d'; eeof = '^e' | '\E^?'; einp = '^w'; insrt = '\EOn';\
pfk1 = '\EOP' | '\E1'; pfk2 = '\EOQ' | '\E2'; pfk3 = '\EOR' | '\E3';\
pfk4 = '\EOw' | '\E4'; pfk5 = '\EOx' | '\E5'; pfk6 = '\EOy' | '\E6';\
pfk7 = '\EOt' | '\E7'; pfk8 = '\EOu' | '\E8'; pfk9 = '\EOv' | '\E9';\
pfk10 = '\EOq' | '\E0'; pfk11 = '\EOr' | '\E-';\
pfk12 = '\EOs' | '\E='; pfk13 = '\EOp\EOP' | '^f13';\
pfk14 = '\EOp\EOQ' | '^f14'; pfk15 = '\EOp\EOR' | '^f15';\
pfk16 = '\EOp\EOw' | '^f16'; pfk17 = '\EOp\EOx' | '^f17';\
pfk18 = '\EOp\EOy' | '^f18'; pfk19 = '\EOp\EOt' | '^f19';\
pfk20 = '\EOp\EOu' | '^f20'; pfk21 = '\EOp\EOv' | '^f21';\
pfk22 = '\EOp\EOq' | '^f22'; pfk23 = '\EOp\EOr' | '^f23';\
pfk24 = '\EOp\EOs' | '^f24';\
pa1 = '^p1' | '\EOS';\
pa2 = '^p2' | '\EOm';\
pa3 = '^p3' | '\EOl';\
}
The following example sets up a line with specific terminal and keyboard characteristics that are used during negotiation with a host upon connection. The line configuration commands in the example must follow the ttycap and keymap global configuration commands containing the emulation settings to be used.
line 3
terminal-type ttycap1
keymap-type ibm7171
The following example shows the configuration of the EBCDIC, ASCII character mappings listed in Table 3-1.
| EBCDIC | ASCII |
|---|---|
| a | x |
| b | y |
| c | z |
PT(config)# tn3270 character-map 0x81 0x78
PT(config)# tn3270 character-map 0x82 0x79
PT(config)# tn3270 character-map 0x83 0x7A
PT(config)# ^Z
The following example displays all nonstandard character mappings:
PT# show tn3270 character-map all
EBCDIC 0x81 <=> 0x78 ASCII
EBCDIC 0x82 <=> 0x79 ASCII
EBCDIC 0x83 <=> 0x7A ASCII
The following example shows the standard key mapping for d:
PT# show tn3270 character-map 83
EBCDIC 0x83 <=> 0x63 ASCII = `c'
EBCDIC 0x84 <=> 0x64 ASCII = `d'
The following example unmaps a specific key, first with the optional ascii-in-hex argument, then without the argument:
PT# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
PT(config)# no tn3270 character-map 0x80 0x78
PT(config)# ^Z
PT# show tn3270 character-map all
EBCDIC 0x82 <=> 0x79 ASCII
EBCDIC 0x83 <=> 0x7A ASCII
PT# conf t
Enter configuration commands, one per line. End with CNTL/Z.
PT(config)# no tn3270 character-map 0x82
PT(config)# ^Z
PT# show t3270 character-map all
EBCDIC 0x82 <=> 0x79 ASCII
The following example displays character mappings, then removes all mappings with the all keyword:
PT# show tn3270 character-map all
EBCDIC 0x81 <=> 0x78 ASCII
EBCDIC 0x82 <=> 0x79 ASCII
EBCDIC 0x83 <=> 0x7A ASCII
PT# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
PT(config)# no tn3270 character-map all
PT(config)# ^Z
PT# show tn3270 character-map all
|
|