On Fri, 27 Oct 1995 11:54:04 +1000 you said:
>We have recently upgraded to MPE 5.0 and are now having a bit of trouble
>with ACD's.  We also have MPEX from Vesoft.  Under MPEX and version 4 of MPE
>a user could rename a file if that user had Write access to the file and
>group.  This now appears impossible with MPE 5.0 because of the ACD
>associated with the file.  As Account Manager I can remove the ACD's from
>the file, and then the user can rename it, but I don't want to have to do
>this all the time.  Is there any way to stop ACD's being attached to a file
>in the first place?
 
It isn't an ACD problem.  I can't speak for the MPEX side effects, but I can
elaborate on the ACD/Rename issue which effects EVERYONE on 5.0:
 
Prior to 5.0 (4.5?) if you tried to :RENAME a file and you weren't the file
creator, you got an error message and that was it; provided you had read and
write access to the original file, you could then :COPY it to the new file
and :PURGE the old one.  No big deal, either it worked, or you worked around.
 
As of 5.0 this changes.  If you have read/write access to the original file,
it makes an effort to allow you to rename the file (since you could anyway)
but tries to set an ACD to allow access to the original owner of the file.
But this is a "not yet ready for prime-time" routine, and while it succeeds
in the initial setting of the new ACD, it fails to rename the file (since
you aren't the creator).  The original file is left with this cryptic ACD
in place and you essentially have no access to the file.
 
I can't elaborate on details since I dealt with this nearly a year ago with
the 5.0 pull, and it's still a pending problem as far as I know.  Perhaps
someone else can give you specifics, but I suspect the problem you have
with MPEX is a side-effect of this behavior.
 
[\] Jeff Kell <[log in to unmask]>