Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-spam!ames!ucbcad!ucbvax!DAL.BITNET!AE
From: AE@DAL.BITNET (Aidan Evans, Dalhousie University)
Newsgroups: comp.os.vms
Subject: Re: DECserver query
Message-ID: <8706260848.AA08007@ucbvax.Berkeley.EDU>
Date: Thu, 25-Jun-87 08:29:00 EDT
Article-I.D.: ucbvax.8706260848.AA08007
Posted: Thu Jun 25 08:29:00 1987
Date-Received: Sat, 27-Jun-87 07:44:17 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 35


 We have DECserver 200/MC's connected to a Develcon Develswitch.  Some of
the parameters set for each port include:

    Autobaud enabled, Autoconnect enabled, Autoprompt enabled,
    Inactivity logout enabled, Modem control enabled, Security enabled

In order to use the DEFINE command, or to SET a port other than the
one to which you are connected, or to SET certain port characteristics
(e.g., to disable security) you must have first entered a "SET
PRIVILEGE" command, which prompts for a password.  There is a
documented default password given in one of the manuals; that password
has of course been changed with a "SET PASSWORD" command on all the
servers.

 On our servers, a you can change characteristics of the port to which you
are currently connected; these changes disappear when you logout of the
port.  Logout from the port is NOT synonymous with logging out of VMS.
After VMS logout you are still connected through the Develswitch to the
server port.  So that our users don't have to remember to logout of the
server as well as VMS, we have set the server "inactivity timeout" to the
minimum allowed, so that after one minute of no activity at the "Local>"
prompt, and with no active terminal sessions, the server logs out the
port.

 As for the LOCK command, if a port is locked, disconnecting the terminal
from the Develswitch disconnects from the server, and the lock is
released.  This is useful if you have forgotten the lock password you
used.

 Of course nothing is perfect.  I have noticed that the "inactivity
logout" seems to be inconsistent.  Sometimes it takes a full minute, but
it does range downwards to 10 or 20 seconds, or sometimes immediately.
Actually, we would prefer to be able to specify the timeout in seconds; on
our Control Data CYBER you get ten seconds before "inactivity logout".