Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!mtunx!rutgers!mailrus!ames!lll-tis!oodis01!uplherc!nrc-ut!nrcvax!kvc
From: kvc@nrcvax.UUCP (Kevin Carosso)
Newsgroups: comp.os.vms
Subject: Re: Translating LTAnnnn: to terminal server and port names
Message-ID: <1495@nrcvax.UUCP>
Date: 5 Jun 88 06:19:18 GMT
Article-I.D.: nrcvax.1495
References: <8805291308.AA25063@ucbvax.Berkeley.EDU>
Reply-To: kvc@minnie.UUCP (Kevin Carosso)
Organization: Network Research Corp.  Oxnard, CA
Lines: 20

In article <8805291308.AA25063@ucbvax.Berkeley.EDU> SYSTEM@INDYVAX.BITNET writes:

>Now if we could only get DEC to put the server and port name in security
>alarms and LOGFAIL accounting entries when LAT terminals are involved...

They have -- in V5.  At least they've got it in SHOW TERMINAL as well
as intrusion records and more than likely security alarms as well.
I don't know about LOGFAIL accounting records, I'd check but am in
the middle of the V5 install right now.  I know they do not include the
information (called "Access Port Information") in regular process accounting
records since with virtual terminals you cannot know for sure where
a process was during the course of a session.

In addition, the access port name can be gotten with GETDVI. This works
from DCL as well, you can say "port = F$GETDVI ("LTAxx:", "TT_ACCPORNAM").
(In V5, of course)

        /Kevin Carosso                     kvc@nrc.com
         Network Research Co.              kvc@ymir.bitnet
                                           kvc@nrcvax.uucp