...
> My original post was intended to indicate that the use of ACDs seems
> difficult to me.
>
> Example 1: when I want to see any ACD for my group I do a
> LISTFILE for the group with a "-2".  I get a list of every
> file in the group.  Not the intended list of only the ACD definitions.

Here is what I get:
 :listfile /SYS/PUB,-2
 PATH= /SYS/
 ------------ACD ENTRIES-------------- FILENAME
 NO ACDS                               PUB/


How is this different from your example?  Notice that the output
contains no individual files (just the pub.sys group) and that
is shows there is no acd for this group.  In fact, ACDs are not
supported for any MPE group, account or for root.  This is
unfortunate but true.  The POSIX shell will show you hard-
coded permissions for an MPE group, e.g.:
 $ls -ld /SYS/PUB
 drwxrwxr-x   2 MANAGER.SYS       SYS        62280 Jul  3 06:19 /SYS/PUB

Normally POSIX file permissions are derived from, and a subset of, an
MPE ACD. But in the case of groups, accounts and root this is not
true.  Permission to this objects cannot be altered.

> Example 2: I want to change every ACD which points to my
> group to instead point to another group but I can't just enter
> a command to do so.

I *think* MPEX may let you do wildcarded ACD changes; otherwise, you
will need to write a script/pgm. The HPACDINFO intrinsics may be helpful.
It appears that the search must be driven by filename rather than by an
ACD subject, and thus could be very slow.

regards,
 Jeff Vance, CSY

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *