NAME.COM - a command procedure to determine what terminal server
and port a particular terminal is connected to.

Version: 2.1
Date   : April 19, 1988
Programmers: 
	Daniel A. Dinkin (Dan)		P. Joseph Callahan (Joe)
	Network Services Manager	Operations Manager
	(301)321-3320			(301)321-4085
	E7OPDAN@TOWSONVX.BITNET		E7OPJOE@TOWSONVX.BITNET

			Academic Computing Service
			Towson State University
			Towson, Maryland 21204

THIS COMMAND PROCEDURE IS *NOT* COPYRIGHTED AND MAY BE USED AND/OR MODIFIED
BY ANYONE AT ANYTIME.

INPUT: P1 = Terminal name (i.e. - LTA123)

OUTPUT: Terminal name
        Ethernet address
        DECnet address
        Port name

REVISION HISTORY:

        1.0 - Written to determine server and port using hard-coded
April 7, 1988  information.  Rejected non-terminal server devices,
               incorrectly supplied device names (i.e. - LTALTA123).
               and terminal server devices which were connected to
               printers.

        2.0 - Took out hard-coding of server names.  Now accesses
April 7, 1988  DSVCONFIG.DAT for the information.  This saves headaches
               when broken servers are swapped out for new ones.

        2.1 - It seems that LTA#'s above 1000 need to be handled
April 19, 1988 differently than LTA#'s below 1000.  A couple of 
               lines of code needed to be added to check for this
               condition and deal with it.

The output of the procedure is mentioned above.  Please note, however,
that the output is very modifiable based upon your need for the procedure.
In fact, I expect that for each different need, you will have to 
redesign the output.  This can be done in two ways.  Either determine
a parameter which will refer to the proper output or make a new
copy of the procedure for every different need.  The choice is up to
you.

There are dozens of possible uses for the command procedure NAME.COM.
The ones that we have come up with so far are:

1) Several terminals in our lab are designated as faculty only.  The
command procedure is executed at login and if the account is not a 
faculty account and the terminal is determined to be a faculty only
terminal, the user is logged out.

2) Our student monitors use a special menu driven account from which they
can log users out, monitor and manipulate batch and print queues, etc.
This account is setup so that it can only login at one terminal which is
directly connected to one node of our cluster and the terminal is setup
so that only operators can login to it.  If we put the terminal onto a
server instead of a DZ-11, the terminal name would change everytime the
student monitor logged in.  With NAME.COM, we don't have to worry about
that since the server and port number don't change.

3) Sometime in the future, we will be setting up a word processing lab
in which there will be several terminals connected to servers where
faculty and students will be able to login and use word processing
on the cluster.  To avoid an overload, we want to limit the word
processing to this set of terminals and no others.  Therefore, when a
user types in the command to start the word processing package, a check
will be made, and the user will be granted access only if they connected
to one of these special servers.