Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcnc!ece-csc!ncrcae!ncr-sd!hp-sdd!ucsdhub!sdcsvax!ucbvax!instr.camosun.bcc.CDN!vsmith
From: vsmith@instr.camosun.bcc.CDN (Vaughn Smith)
Newsgroups: comp.os.vms
Subject: Any success with $SETUAI?
Message-ID: <7*vsmith@instr.camosun.bcc.cdn>
Date: Thu, 18-Jun-87 22:25:06 EDT
Article-I.D.: instr.7*vsmith
Posted: Thu Jun 18 22:25:06 1987
Date-Received: Mon, 22-Jun-87 01:23:04 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 22


> Second:  In my opinion, which you may choose to ignore or not, having a
> *system service* to muck with the UAF is stupid.  I can only see two reasons
> for having it:  1> So that you can have "group managers" who can bash their
> underlings' accounts,

We would like to use $SETUAI so that students could set the owner field on 
their accounts when they log in for the first time. The old program to do
this requires changing every time VMS changes the UAF. We get the following
on both VMS 4.4 and VMS 4.5A (LAVC):

%RMS-F-RNL, record not locked
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC
SETUAI$MAIN     SETUAI$MAIN                       195      0000005D  0000065D


Shouldn't the system service return an error and not leave it to RMS? The 
documentation on $SETUAI looks like too much like $GETUAI.

Thanks in advance.
Vaughn Smith.