Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!rochester!rutgers!labrea!jade!ucbvax!LLL-ICDC.ARPA!OBERMAN
From: OBERMAN@LLL-ICDC.ARPA ("Kevin Oberman, LLNL,  422-6955, L-156", 415)
Newsgroups: comp.os.vms
Subject: User data area of SYSUAF.DAT
Message-ID: <8709221433.AA05427@ucbvax.Berkeley.EDU>
Date: Mon, 21-Sep-87 11:18:00 EDT
Article-I.D.: ucbvax.8709221433.AA05427
Posted: Mon Sep 21 11:18:00 1987
Date-Received: Thu, 24-Sep-87 04:39:11 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 28


 Joel M Snyder  writes:

>This, of course, doesn't help you much.  A couple of alternative are
>available.  One possiblity is to store your own date, call it "last-time-
>I-read-this-file" in the authorization file.  My opinion: bad idea. 
>Don't be mucking in the authorization file; some day, Digital will
>come around and cut your fingers off and won't even warn you.  

I don't think so. DEC has documented the proper method for accessing and
using the User Data Area oft the SYSUAF. I must admit that I can't find
the documentation right now, but I used it to design some internal software
and it worked fine. There is a pointer to the User Data area in each UAF
record.

Once DEC documents anything, they are prone to keep it around unless they
absolutely have to kill it. And then they are usually very good at documenting
the change.

					R. Kevin Oberman
					Lawrence Livermore National Laboratory
					arpa: oberman@lll-icdc.arpa
   					(415) 422-6955

Disclaimer: Neither my employer nor myself can take resposibility for the
accuracy of this information. I believe it is correct, but if it's not I can
only say "Sorry". I'm a rotten typist and a worse speller, so forgive any silly
errors.