Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #248
Difficulty: Easy
ARPANET was designed to reliably transmit 911 messages, and to inform the host computer when it loses a message.
True or False?
Linux & Unix Commands - Search Man Pages

tn3270(1) [bsd man page]

TN3270(1)						      General Commands Manual							 TN3270(1)

NAME
tn3270 - full-screen remote login to IBM VM/CMS SYNOPSIS
tn3270 sysname DESCRIPTION
Tn3270 permits a full-screen, full-duplex connection from a VAX UNIX machine to an IBM machine running VM/CMS giving the appearance of being logged in directly to the remote machine on an IBM 3270 terminal. Of course you must have an account on the machine to which you wish to connect in order to log in. Tn3270 looks to the user in many respects like the Yale ASCII Terminal Communication System II. Tn3270 is actually a modification of the Arpanet TELNET user interface (see telnet(1)) that interprets and generates raw 3270 control streams. Emulation of the 3270 terminal is done in the Unix process. This emulation involves mapping 3270-style commands from the host into appro- priate sequences to control the user's terminal screen. Tn3270 uses curses(3x) and the /etc/termcap file to do this. The emulation also involves simulating the special 3270 keyboard keys (program function keys, etc.) by mapping sequences of keystrokes from the ASCII key- board into appropriate 3270 control strings. This mapping is terminal dependent and is specified in a description file, /usr/share/misc/map3270, (see map3270(5)) or in an environment variable MAP3270 (see mset(1)). Any special function keys on the ASCII key- board are used whenever possible. If an entry for the user's terminal is not found, tn3270 looks for an entry for the terminal type unknown. If this is not found, tn3270 uses a default keyboard mapping (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, tn3270 sends an ASCII bell (BEL), or a visual bell if defined in the user's termcap entry, to the user's terminal and nothing is sent to the IBM host. If tn3270 is invoked without specifying a remote host system name, it enters local command mode, indicated by the prompt ``tn3270>''. In this mode, tn3270 accepts and executes the following commands: open connect to a remote host close close the current connection quit exit tn3270 z suspend tn3270 status print connection status ? print help information Other common telnet commands are not available in tn3270. Tn3270 command mode may also be entered, after connecting to a host, by typing a special escape character (typically control-C). While in command mode, any host login session is still alive but temporarily 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. FILES
/etc/termcap /usr/share/misc/map3270 AUTHOR
Greg Minshall SEE ALSO
mset(1), telnet(1), termcap(3x), termcap(5), map3270(5), Yale ASCII Terminal Communication System II Program Description/Operator's Manual (IBM SB30-1911) BUGS
Performance is slow and uses system resources prodigiously. Not all 3270 functions are supported, nor all Yale enhancements. 4.3 Berkeley Distribution November 27, 1996 TN3270(1)

Check Out this Related Man Page

RLOGIN(1)						      General Commands Manual							 RLOGIN(1)

NAME
rlogin - remote login SYNOPSIS
rlogin [-8EL] [-e char] [-l username] rhost rhost [-8EL] [-e char] [-l username] DESCRIPTION
Rlogin connects your terminal on the current local host system lhost to the remote host system rhost. Each host has a file /etc/hosts.equiv which contains a list of rhost's with which it shares account names. (The host names must be the standard names as described in rsh(1).) When you rlogin as the same user on an equivalent host, you don't need to give a password. Each user may also have a private equivalence list in a file .rhosts in his login directory. Each line in this file should contain an rhost and a username separated by a space, giving additional cases where logins without passwords are to be permitted. If the originating user is not equivalent to the remote user, then a login and password will be prompted for on the remote machine as in login(1). To avoid some security problems, the .rhosts file must be owned by either the remote user or root. The remote terminal type is the same as your local terminal type (as given in your environment TERM variable). The terminal or window size is also copied to the remote system if the server supports the option, and changes in size are reflected as well. All echoing takes place at the remote site, so that (except for delays) the rlogin is transparent. Flow control via ^S and ^Q and flushing of input and output on interrupts are handled properly. The optional argument -8 allows an eight-bit input data path at all times; otherwise parity bits are stripped except when the remote side's stop and start characters are other than ^S/^Q. The argument -L allows the rlogin session to be run in litout mode. A line of the form ``~.'' disconnects from the remote host, where ``~'' is the escape character. Similarly, the line ``~^Z'' (where ^Z, control-Z, is the suspend character) will suspend the rlogin session. Substitution of the delayed-suspend character (normally ^Y) for the suspend character suspends the send portion of the rlogin, but allows output from the remote system. A different escape character may be specified by the -e option. There is no space separating this option flag and the argument character. With the -E option the escape can be turned off. SEE ALSO
rsh(1), rhosts(5). BUGS
More of the environment should be propagated. 4.2 Berkeley Distribution May 12, 1986 RLOGIN(1)

Featured Tech Videos