Robert wrote:

> Can someone point me in the right direction?  We would like to limit the
> VT-MGR connection (NS/VT) coming from the network (Reflections sessions) to
> a range of LDEV's (or at least specifying the beginning device range) .

There are no "obvious" solutions to your problem.  Since MPE/XL you have
no control over what were VTERMs (DSTERMs?) on the classic systems.  In
SYSGEN you can largely control assignment of non-network LDEVs, and
somewhat ironically network printers, but everything else is NMMGR plus
smoke and mirrors.

If you define "non-nailed" LDEVs, those are allocated from unused LDEVs
(not in SYSGEN) and they remain fixed.  DTC TAC connections are
allocated from the "non-nailed" pool.

NS/VT and Telnet/iX sessions will dynamically setup and teardown LDEVs
as needed.

You can, however, kludge yourself a solution to the problem with an
option logon UDC magic that determines if the session is NS/VT or not
(rather trivial, NS/VT sets some specific HP-variables you can see if
they are bound or not).  If you just want to identify NS/VT sessions,
that will do it.  If you want to limit them, you'll have to play some
more games.  Checking the number of accessors of the VTSERVER program
file "might" work, if you account for any "pooled" VTSERVERs you have
allocated.

Jeff Kell
Network Services/Information Security
University of Tennessee at Chattanooga

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *