T.R | Title | User | Personal Name | Date | Lines |
---|
2254.1 | ACL$ doesn't allow you to | UTES09::EIJS | Simon Eijs @Utrecht, 7838-2558 | Mon Feb 15 1993 08:57 | 18 |
|
Hi,
I don't think so. One of our customers has a similar kind of setup (all
accounts belomging to one user the same UAF identifier) but ALL-IN-1
(or better Group Services and Drawer Management) couldn't handle this.
The way it did work in the end was to create a dummy UAF entry (e.g.
GROUP_ENGINEERS) and assign that identifier to the different UAF
entries. Not really an ideal solution.
The ACL$ doesn't handle the situation as described by you.
So I think the customer should not only create the groups again name by
name, by also change something in the UAF entries.
Ciao,
Simon
|
2254.2 | Write your own? | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Mon Feb 15 1993 10:10 | 9 |
| With some study of the Application Programming Books, you could
probably produce some code that would use UAI$ to loop through SYSUAF,
lookups in PROFIL to check the ALL-IN-1 account names, and the GROUP
functions to add the members to the Group.
Graham
PS Please spell ALL-IN-1 correctly, all in capitals, as it's a trade
mark. I've corrected your base note.
|
2254.3 | Depends what .0 meant by "identifier" | SCOTTC::MARSHALL | Spitfire Drivers Do It Topless | Mon Feb 15 1993 11:08 | 11 |
| Hmmm,
I read .0 to mean that they had a group of VMS accounts, all of whom had been
given a VMS rights identifier.
This should make it easy to turn this into an ALL-IN-1 group, as an ALL-IN-1
group is basically just a set of VMS accounts with VMS rights identifiers.
So some magic incantations with the group functions should be all that's needed?
Scott
|