Safeguard Administrator's Manual (G06.29+, H06.08+, J06.03+)

Managing User Groups
Safeguard Administrator’s Manual—523317-029
3-4
Using Wild-cards for Managing Group Members
This command adds the users TEST.PHIL and TEST.JUNE and the user alias
Group-Super to the group PROG4. The group owner, ADMIN.DON, has no
administrative control over the user and alias authentication records for these users,
but he does control their membership in the group PROG4.
Use the INFO GROUP command to verify the results of the commands:
=INFO GROUP PROG4, DETAIL
The display shows:
Now any access control list entry that contains the entry 144,* is interpreted by the
Safeguard software to include all members of group 144, including TEST.PHIL,
TEST.JUNE, and Group-Super.
Suppose that ADMIN.DON later decides that the user TEST.PHIL no longer needs
access to the protected files. He enters this command to remove TEST.PHIL from the
group:
=ALTER GROUP PROG4, MEMBER -test.phil
The minus sign at the beginning of the member list specifies that the users in the list
are to be removed from the group.
Using Wild-cards for Managing Group Members
The ADD GROUP command and the ALTER GROUP command support the following
wild-card characters for adding and/or deleting group members:
* : An asterisk (*) matches any number of characters (zero, one, or more).
? : A question mark (?) matches a single character.
For more information on using wild-card characters, see the Safeguard Reference
Manual.
GROUP NAME NUMBER OWNER LAST-MODIFIED
PROG4 144 16,24 23JUL94, 11:49
CREATION-TIME = 15JUL05, 2:03
CREATOR-USER-NAME = SUPER.SUPER
CREATOR-USER-TYPE = USER (255,255)
CREATOR-NODENUMBER = 86
AUTO-DELETE = OFF
DESCRIPTION = Maintenance programmers for Inventory System
MEMBER = PROG4.SUSAN
MEMBER = TEST.PHIL
MEMBER = TEST.JUNE
MEMBER = Group-Super
GROUP OWNER-LIST SECTION UNDEFINED!
Note. The attribute OWNER-LIST is supported only on systems running H06.25 and later H-
series RVUs and J06.14 and later J-series RVUs.
Note. These wild-card characters are supported only on systems running J06.08 and later J-
series RVUs and H06.19 and later H-series RVUs.