Consultor Eletrônico

Alternative remote connection methods when VTA's are enabled

INTRODUCTION: Date Last Modified: 30-MAR-94
=============

This Product Services Technical Support Knowledgebase entry
explains some alternatives for remote logins on VMS systems
to access VTA terminal type when Virtual Terminals are
enabled.


BACKGROUND:
===========

Remote user logins do not by default connect as virtual
terminals, even when Virtual Terminals are enabled. Remote
users logging directly into the VMS system via hardware such
as modems or by making use of the SET HOST command will have
a device type of RTA. There are a couple of alternatives
that will allow remote users to connect as VTA devices.


ALTERNATIVE CONNECTION METHODS
==============================

Terminal Servers: If instead of connecting the modem
directly to the cpu, the modem is connected to a Terminal
Server and the user logs into the VMS system via the
Terminal Server the users terminal device will be VTA (Note:
the terminal server must support modem control such as a
DecServer200 or a DecServer500 - DecServer 300's do not
support modem control and therefore cannot be used).

SET HOST: If instead of using the SET HOST command the user
uses SET HOST/LAT, the users terminal device will be VTA.
The VMS system MUST have version 5.2 or higher of LATCP
installed (also referred to as LAT Master). This version of
LATCP was optional on VMS versions previous to 5.5, but is
required on version 5.5 or higher of VMS. Also, LATCP must
be configured so that inbound AND outbound connections are
enabled. Modify the LATSTARTUP.COM file to enable outbound
connections (inbound connections are enabled by default).

(Note: The user can determine right away which version of
LAT they are running by doing a MCR LATCP and looking at the
prompt which appears. If the prompt is LAT> then they are
not running LAT Master. If the prompt is LATCP and they
appear with a 'window' screen then they are running LAT
Master.)

Progress Software Technical Support Note # 13011