| 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
I am going to install a co-existing ALL-IN-1 V3.0 in our
client site and I want to make sure something before that.
1. All the account (A1$XFER_IN,A1$XFER_OUT,OAFC$DEFAULT,
OAFC$SERVER,A1$SCRIPT) seem to belong to the co-existing
system after the installation, right?
a. Does this mean that the user cannot perform account
transfer before the co-existing system is removed?
b. The installation guide suggest we should perform the
upgrade (from V2.4 to V3.0) before removing the
co-existing system, what will happen to these
account?
2. Obviously the user would not want the account in the
co-existing system go into the DDS but they still want to
test the search mail directory functions etc.
a. Will zero for the mail directory level prevent account
in the co-existing system going into the DDS?
b. Can I specify the mail directory level to be 1 and then
remove the UA (OA$node$ALLIN1) afterward?
c. What about I shut down DDS during the installation?
3. I have looked at a co-existing system somewhere and they use
A2 as the MR mailbox for the co-existing system. But when
I look at the installation guide, there isn't a question asking
the name of the MR mailbox, only the password of the MR
mailbox will be asked, then how can I specify the name of the
MR mailbox?
And, how can I find out the latest patch status for the
ALL-IN-1 version 3.0?
Thank you very much
Banquo
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2258.1 | Not that i've ever gone co-ex but... | AIMTEC::WICKS_A | WALES 10 England 9 | Mon Feb 15 1993 16:29 | 30 |
banquo,
1. obviously the new accounts A1$SCRIPT etc belong to the v3.0 system
since they didn't exist in v2.4. I thought that the XFER accounts
belonged to v2.4.
a) co-ex is for testing only, not for moving things to or from.
b) they get blown away and recreated for your newly upgraded v2.4
to v3.0 system.
2. the mail managment guide says 0 allows the user to do enquiries but
not updates - so from your v3.0 system you can still do lookups
in the dds database.
YOu won't be able to do updates unless you build a whole mirror
database with a UA called OA1$node$ALLIN1 and subscriber entries
owned by it but then these 'test' subscribers could be seen by
the v2.4 system as 'duplicate' and you don't want that do you?
Why would you want to shutdown DDS?
3. Don't know maybe it's a manual post-install task.
P.S they are literally tens of notes in this notesfile mentioning
that ALL-IN-1 v3.0-1 the first and so far only ALL-IN-1 v3.0
patch has shipped.
Regards,
Andrew.D.Wicks
| |||||
| 2258.2 | Mailbox name in A1CONFIG | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Mon Feb 15 1993 17:49 | 7 |
3. The installation defaults the mailbox name to be A1 (or A2 for co-ex
systems). If you want to change it, you can either edit the A1CONFIG
file, using the form of the same name, or you can redefine the mailbox
logical OA$MTI_MAILBX in the SITE startup file. I'm sure this is
documented somewhere.
Graham
| |||||
| 2258.3 | A word about Transfer User | IOSG::TALLETT | Gimmee an Alpha colour notebook... | Tue Feb 16 1993 09:06 | 9 |
It doesn't really matter where the transfer directories point
as long as the manager can write to them. As long as you don't
mix up the transfers, I would expect both systems to happily
share the same areas. Of course, when you do the upgrade, users
"in transit" would probably be affected.
Regards,
Paul
| |||||