HP3000-L Archives

October 1995, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
John Dunlop <[log in to unmask]>
Reply To:
John Dunlop <[log in to unmask]>
Date:
Tue, 31 Oct 1995 06:39:06 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
[This note has been sent to the following InterNet address(es):
[log in to unmask]]
 
 
Marilyn you wrote :
 
>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?
 
We had the same trouble but managed to workaround it  Add two parameters
to the MPEX RENAME command for MPE/iX 5.0 to prevent the adding of an
ACD and retention of the original FILEGROUP ID, the following should be added
to the MPEXMGR.PUB.VESOFT file to execute each time MPEX is run :
 
   :SETVAR VESOFTDEFAULTRENAME ";LOCALGROUPID;DELACD"
 
I hope this is of some help.
 
Cheers,
John Dunlop ([log in to unmask])

ATOM RSS1 RSS2