Oh GACK! src-clean doesn't quite work that easily since cleandist rebuilds the

[unix-history] / usr.bin / tn3270 / tn3270.0

TN3270(1)                   386BSD Reference Manual                  TN3270(1)

N\bNA\bAM\bME\bE
     t\btn\bn3\b32\b27\b70\b0 - full-screen remote login to IBM VM/CMS

S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
     t\btn\bn3\b32\b27\b70\b0 [-\b-d\bd] [-\b-n\bn _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be] [-\b-t\bt _\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bn_\ba_\bm_\be] [_\bs_\by_\bs_\bn_\ba_\bm_\be [port]]

D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
     T\bTn\bn3\b32\b27\b70\b0 permits a full-screen, full-duplex connection from a UNIX machine
     to an IBM (or compatible) machine.  T\bTn\bn3\b32\b27\b70\b0 gives the appearance of being
     logged in to the remote machine from an IBM 3270 terminal.  Of course,
     you must have an account on the machine to which you connect in order to
     log in.  T\bTn\bn3\b32\b27\b70\b0 looks to the user in many respects like the Yale ASCII
     Terminal Communication System II.  T\bTn\bn3\b32\b27\b70\b0 is actually a modification of
     the Arpanet TELNET user interface (see telnet(1))  which will, in certain
     circumstances, interpret and generate raw 3270 control streams.

     The flags to t\btn\bn3\b32\b27\b70\b0 are as follows:

     -\b-d\bd          Turn on socket-level tracing (for super-user only) -\b-n\bn_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
                 Specify a file to receive network trace data output (from
                 commands "toggle netdata" and "toggle options", see
                 telnet(1));  the default is for output to be directed to the
                 standard error file.  -\b-t\bt_\bc_\bo_\bm_\bm_\ba_\bn_\bd_\bn_\ba_\bm_\be Specify a UNIX command to
                 process IBM 4994 style transparent mode data received from
                 the remote IBM machine.

     _\bs_\by_\bs_\bn_\ba_\bm_\be     The name of the remote system.  If the remote name is NOT
                 specified, the user will be prompted for a command (see be-
                 low).

     _\bp_\bo_\br_\bt        The port to connect to on the remote system.  Normally,
                 t\btn\bn3\b32\b27\b70\b0 attempts to connect to the standard TELNET port (port
                 23) on the remote machine.

     When t\btn\bn3\b32\b27\b70\b0 first connects to the remote system, it will negotiate to go
     into 3270 mode.  Part of this negotiation involves telling the remote
     system what model 3270 it is emulating.  In all cases, t\btn\bn3\b32\b27\b70\b0 emulates a
     3278 terminal.  To decide which specific model, t\btn\bn3\b32\b27\b70\b0 looks at the num-
     ber of lines and columns on the actual terminal (as defined in the TERM
     environment variable; see termcap(5)).  The terminal (or window in which
     t\btn\bn3\b32\b27\b70\b0 is running, on multiple window systems) must have at least 80
     columns and 24 lines, or t\btn\bn3\b32\b27\b70\b0 will not go into emulation mode.  If the
     terminal does have at least 80 columns and at least 24 lines, the follow-
     ing table describes the emulation:

                       minimum_size      emulated
                       (rows*columns)    terminal
                       --------------    ------------
                       27*132            3278 model 5
                       43*80             3278 model 4
                       32*80             3278 model 3
                       24*80             3278 model 2.

     Emulation of the 3270 terminal is done in the UNIX process.  This emula-
     tion involves mapping 3270-style commands from the host into appropriate
     sequences to control the user's terminal screen.  T\bTn\bn3\b32\b27\b70\b0 uses curses(3)
     and the /_\bu_\bs_\br/_\bs_\bh_\ba_\br_\be/_\bm_\bi_\bs_\bc/_\bt_\be_\br_\bm_\bc_\ba_\bp file to do this.  The emulation also in-
     volves simulating the special 3270 keyboard keys (program function keys,
     etc.)  by mapping sequences of keystrokes from the ASCII keyboard into
     appropriate 3270 control strings.  This mapping is terminal dependent and
     is specified in a description file, /_\bu_\bs_\br/_\bs_\bh_\ba_\br_\be/_\bm_\bi_\bs_\bc/_\bm_\ba_\bp_\b3_\b2_\b7_\b0, (see
     map3270(5))  or in an environment variable MAP3270 (and, if necessary,
     MAP3270A, MAP3270B, and so on - see mset(1)).  Any special function keys
     on the ASCII keyboard are used whenever possible.  If an entry for the
     user's terminal is not found, t\btn\bn3\b32\b27\b70\b0 looks for an entry for the terminal
     type _\bu_\bn_\bk_\bn_\bo_\bw_\bn. If this is not found, t\btn\bn3\b32\b27\b70\b0 uses a default keyboard map-
     ping (see map3270(5)).

     The first character of each special keyboard mapping sequence is either
     an ASCII escape (ESC), a control character, or an ASCII delete (DEL). If
     the user types an unrecognized function key sequence, t\btn\bn3\b32\b27\b70\b0 sends an
     ASCII bell (BEL), or a visual bell if defined in the user's termcap en-
     try, to the user's terminal and nothing is sent to the IBM host.

     If t\btn\bn3\b32\b27\b70\b0 is invoked without specifying a remote host system name, it en-
     ters local command mode, indicated by the prompt ``tn3270> ''. In this
     mode, t\btn\bn3\b32\b27\b70\b0 accepts and executes all the commands of telnet(1),  plus
     one additional command:

     t\btr\bra\ban\bns\bsc\bco\bom\bm      Specify UNIX command for IBM 4994 style transparent mode
                   processing.

     T\bTn\bn3\b32\b27\b70\b0 command mode may also be entered, after connecting to a host, by
     typing a special escape sequence.  If t\btn\bn3\b32\b27\b70\b0 has succeeded in negotiating
     3270 mode with the remote host, the escape sequence will be as defined by
     the map3270 (see map3270(5))  entry for the user's terminal type (typi-
     cally control-C); otherwise the escape sequence will initially be set to
     the single character `^]' (control right square bracket).

     While in command mode, any host login session is still alive but tem-
     porarily suspended.  The host login session may be resumed by entering an
     empty line (press the RETURN key) in response to the command prompt.  A
     session may be terminated by logging off the foreign host, or by typing
     ``quit'' or ``close'' while in local command mode.

F\bFI\bIL\bLE\bES\bS
     /usr/share/misc/termcap
     /usr/share/misc/map3270

N\bNO\bOT\bTE\bES\bS
     The IBM 4994 style transparent mode command is invoked when t\btn\bn3\b32\b27\b70\b0 re-
     ceives IBM 4994 style transparent output from the remote host.  Output
     and input pipes are created for communication between the two processes.
     The pipes are closed when a 3270 clear command is received from the re-
     mote hosts, signalling the end of transparent mode output.  Transparent
     mode is necessary for sending ASCII control characters over the 3270 ter-
     minal connection; ASCII graphics terminal support is accomplished this
     way.  Developers of t\btr\bra\ban\bns\bsc\bco\bom\bm commands should note that the t\btr\bra\ban\bns\bsc\bco\bom\bm stdin
     pipe end will be in CBREAK mode, with ECHO and CRMOD turned off.

E\bEN\bNV\bVI\bIR\bRO\bON\bNM\bME\bEN\bNT\bT
     T\bTn\bn3\b32\b27\b70\b0 checks the following environment variables: TERM, MAP3270,
     MAP3270[A...]. Information on these can be found in mset(1).  T\bTn\bn3\b32\b27\b70\b0 also
     checks SHELL, KEYBD and API3270.

S\bSE\bEE\bE A\bAL\bLS\bSO\bO
     mset(1),  telnet(1),  curses(3),  termcap(3),  termcap(5),  map3270(5),

     "Yale ASCII Terminal Communication", _\bS_\by_\bs_\bt_\be_\bm _\bI_\bI _\bP_\br_\bo_\bg_\br_\ba_\bm
     _\bD_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn/_\bO_\bp_\be_\br_\ba_\bt_\bo_\br'_\bs _\bM_\ba_\bn_\bu_\ba_\bl, IBM SB30-1911.

H\bHI\bIS\bST\bTO\bOR\bRY\bY
     The t\btn\bn3\b32\b27\b70\b0 command appeared in 4.3BSD.

B\bBU\bUG\bGS\bS
     Tn3270 is slow and uses system resources prodigiously.

     Not all 3270 functions are supported, nor all Yale enhancements.


     Error conditions (attempting to enter data in a protected field, for ex-
     ample) should cause a message to be sent to the user's terminal instead
     of just ringing a bell.

4.3 Berkeley Distribution        July 27, 1991                               4