NAME

vt3k − virtual terminal facility from HP-UX (HP 9000) to MPE (HP 3000). 

SYNOPSIS

vt3k [[-a| -I] input_file] [-l[i] [o] -f [logfile]] [-t] hostname

DESCRIPTION

vt3k provides direct login capability (via LAN) from HP-UX to MPE V or MPE XL.  Invoking vt3k from HP-UX establishes a connection to an HP 3000 running NS Virtual Terminal Services.  Upon successful connection, the HP-UX user receives an MPE logon prompt.  When the user logs off the MPE system, the connection is automatically terminated and the user is returned to HP-UX. 

Options

vt3k supports the following command-line options and arguments:

-a input_file Read command input from input_file instead of standard input, and restore input back to standard input (keyboard) at the end of the script.  The first line in input_file must be an MPE logon statement.  vt3k returns input control to the keyboard after the last command in the input file.  This is especially useful for an "automated" HP 3000 login and application invocation.  The last line in input_file can also be an MPE bye command.  This option cannot be used with the -I option. 

-I input_file Read command input from input_file instead of standard input.  Equivalent to the -a option, except that the connection to the HP 3000 is terminated when the end of input_file is encountered, whether or not an MPE bye command exists in the last line of input_file. This option cannot be used with the -a option. 

-li Log input to file specified by the -f option. 

-lo Log output to file specified by the -f option. 

-lio Log input and output to file specified by the -f option. 

-f logfile Log input and/or output as specified by the -l option to logfile. If logfile is not specified, send logging information to standard output. 

-t Enable standard HP-UX type-ahead capability while connected to MPE.  If this option is not specified, vt3k defaults to type-ahead “off”.  This option enables type-ahead between the user’s keyboard and vt3k only; it does not apply to the connection between vt3k and the application on the MPE system.  This option allows the user to take advantage of type-ahead features provided by HP-UX, but is not sufficient for MPE-iX applications that require SETVAR HPTYPEAHEAD TRUE.  This also means that screen-oriented applications using character reads fail when the -t option is used with vt3k. 

Supported Configurations

vt3k requires at least MPE V V-Delta-5, or MPE XL 1.2.  equipped with NS Services and NS LAN Link products. 

vt3k is supported on the following configurations:

• HP 2392 or HP 700/92 terminal connected via RS-232 to an HP 9000 Series 800 (connected via LAN to an HP 3000). 

• HP 9000 Series 300/400/700 workstation running hpterm. 

vt3k is not supported from a telnet or rlogin session. 

hpterm offers HP Block-Mode terminal emulation when using X-Windows on a Series 300/400 or Series 700 workstation. 

vt3k can cross gateways, but this requires a proxy server machine on the local network with routing information for systems not on the local network.  Contact the network administrator for information about proxy servers. 

Since HP 3000s use only IEEE protocol, ifconfig on HP-UX must be configured for IEEE in addition to Ethernet. 

The target HP 3000 must be running NS Virtual Terminal Services. 

To test whether an HP 9000 system and an HP 3000 are communicating, try a remote loop back (see rlb(1)) from HP-UX to the HP 3000 and ensure that dscopy (see dscopy(1)) is working between the two systems.

DIAGNOSTICS

Errors at the transport level are reported using NetIPC error codes.  The most common error is:

NSR_NO_NODE (40) node does not exist. 

Some possible causes are: the remote node is running; is on a different network; is running pre-UB-Delta-2 MPE; the node name is incorrect; or the remote node is not listed on the local proxy server.  Refer to the NS/HP 9000 User/Programmer Reference Manual for a complete list of error codes and corrective actions. 

The preferred way to kill vt3k is by using kill -15 which allows cleanup before the session is terminated. 

NOTES

To disconnect from a vt3k to the wrong HP 3000 by mistake, terminate the connection to the HP 3000 at the MPE logon prompt by typing :eof: in response to the MPE V logon prompt or bye in response to the MPE/XL logon prompt.  The connection should close with the message Connection Terminated (0). 

If an HP 3000 session is hung and the HP-UX system supports Job Control (C shell, Korn shell, and POSIX shell), first suspend the vt3k session, then run ps(1) to obtain the PID of the vt3k process.  Use a kill -15 PID to terminate the session.  A message stating that the process has been stopped should be echoed.  Put the suspended shell process back into the foreground, and the HP 3000 session should have terminated with the message Received signal 15.  (If X-Windows are being used, a second window can be used instead of suspending the foreground process.) 

Limitations

vt3k only supports line-oriented and VPLUS blockmode applications on the HP 3000.  VPLUS applications must use a FORMSPEC file to specify screen layout.  vt3k does not support non- VPLUS blockmode or screen-oriented applications.  vt3k does not support hybrid applications that mix VPLUS and MPE intrinsic calls for terminal communications. 

The Break key may not work if rlogin was used to get to the HP-UX system where vt3k was invoked. 

Character editors such as HPEDIT may run very slowly.  When using these editors, the vt3k -t option is recommended. 

vt3k may not transmit some control sequences such as XON/XOFF. 

EXAMPLES

To vt3k to a remote host, type:

vt3k remote_host

To vt3k to a remote host and enable typeahead, type:

vt3k -t remote_host

To vt3k to a remote host and log output to the file logfile, type:

vt3k -lo -f logfile remote_host

AUTHOR

vt3k was developed by HP. 

FILES

/usr/bin/vt3k
/usr/man/man1/vt3k.1

Hewlett-Packard Company  —  HP-UX Release 9.0: August 1992