| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
hi,
what VMS priv's should an account have in order to perform the transfer
user functions? the customer wants to transition this functionality
from the ALl-IN-1 manager to an administrator. right now the
administrator account has only NETMBX and TMPMBX VMS priv's.
is just the OA$ADMIN identifier enough?
ALL-IN-1 2.4, VMS 5.5-2
thanks - ann
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2743.1 | NETMBX,TMPMBX enough | IOSG::TYLDESLEY | Mon May 24 1993 11:33 | 18 | |
Hello Ann,
I don't have a V2.4 system to hand - the usual apology! - but from
memory, Admins have always been able to handle TU - because most of
the real work is done via the Manager and Transfer accounts.
If you check in the script OA$LIB:SM_NOMINATE, you'll find the things
that are required to be an Admin in V2.4, and I think you'll find that
OA$ADMIN is the key. You'll see that it checks the identifier, then
grants it. Nothing more should be required to do TU, if the calling
account has been nominated admin in the normal way.
I believe that it is a principle that we work to here, that admins
should not require any special VMS privs. to do their work.
Cheers
DaveT
| |||||
| 2743.2 | ANGLIN::HARRISA | user vicious | Tue May 25 1993 19:18 | 6 | |
thanks dave -
that's the way i thought it should work. maybe that script was
modified by me predicessor and not documented.
thanks! ann
| |||||