| 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 |
Hello, During the ALL-IN-1 installation various ALL-IN-1 related accounts gets created. ALLIN1, A1$XFER_IN, A1$XFER_OUT,A1$SCRIPT, OAFC$SERVER, OAFC$DEFAULT. All except the ALLIN1 was created with account field of ALLIN1. The rest was created with account field DEFAULT. For billing purposes, customer like to change all of them to have account field of ALLIN1. Would there be any unforseable problem that we are not aware of if the ACCOUNT field is changed ? Thanks, ricardo
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3568.1 | go ahead; change it | IOSG::TYLDESLEY | Tue Nov 23 1993 16:20 | 16 | |
Hello Ricardo.
This is a result of the fact that Make_uic in Create User utilizes
the DEFAULT VMS account to produce the new VMS account. Looking in
Authorize on our systems shows that some of them have the UAF Default
field set, and some don't. It will have been set by our s. mangler.
I believe its only use is for billing purposes at the VMS level, and
(as person responsible for ALL-IN-1 user management :-) I can safely
say that ALL-IN-1 makes absolutely no use of this field...
... but I have been wrong before ;-)
No, seriously, there should be no impact on your ALL-IN-1 systems if
this field is changed via Authorize. If you want to use it within
ALL-IN-1 , the wonderful UAI$ will fetch it for you.
Cheers
DaveT
| |||||
| 3568.2 | Bugged. | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Tue Dec 14 1993 16:41 | 6 |
I don't think that the Installation uses the SM code to create its
accounts.
In any case, I've bugged it.
Graham
| |||||