[fa.info-vax] VTA???

info-vax@ucbvax.ARPA (06/11/85)

From: *Hobbit* <AWalker@RUTGERS.ARPA>

*Thank* *You*!! for bringing this up.  I was thinking about this last night
myself.  Virtual terminals are fine and dandy, especially on network or
dialup connections, but the accounting file will never tell you where a
given login *really* came from.  Is there a fix, besides having a server
running somewhere that will add physical device names of any newly-created
virtual terminals to a file somewhere [a workaround I was thinking of 
writing...]??

The following is too much to hope for: VMS support of what TCP host a given
login came from.  Surprise me!  Anything like this in the works?

_H*
-------

info-vax@ucbvax.ARPA (06/11/85)

From: Richard Garland <OC.GARLAND@CU20B.ARPA>

remote Hosts for Logins:

TCP is not a VMS layered product.  I suggest you get your TCP vendor to
supply the information.

DECnet is a supported product, and you can get the remote host for logins.
Its in the accounting log and its kept in 2 places while a login is in
progress:  P1 space of the logged in process, and in the DECnet database.

This info can be obtained through a QIO call to the network management
(NETACP or whatever).  For details look at my Finger program (on this
machine via anonymous FTP CU20B:<OC.GARLAND.FINGER>*.*) or several other
similar programs floating around.

What DEC should do pehaps to make it a little easier is to put it into
GETJPI.

					Rg
-------

info-vax@ucbvax.ARPA (06/11/85)

From: Richard Garland <OC.GARLAND@CU20B.ARPA>

P.S. to Hobbits request:

I mentioned DECnet and TCP, I forgot LAT terminals:

Several people asked at DECus about LAT service which would identify
ports.  The LAT people said it was in "level II" protocol already
in the boxes and the VMS people had to utilize it.   The VMS people
said "true we don't do it , but its not in the boxes yet anyway"

Lets hope they get together and do it sooner or later.  Other services
such as dial-out were grouped with this same issue.
					Rg
-------