| 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,
The Application Probramming team here at the CSC has been asked to consider
taking on a Revenue Generation opportunity. I'm placing a brief
description of the specs here in hopes of getting some thoughts and
feedback from those who may have had experience with this.
The customer wants to move all the documents, mail messages, etc...
belonging to a large number of users from one system to another without
using the transfer user features in ALL-IN-1. They have ALL-IN-1 V2.4.
We have access to an Assets package called File Cabinet Extended which
packages the documents in each folder as attachments to a mail message and
then sends these messages to the other system. The user can then run the
option from this Asset on the other system to file these attachments in to
their file cabinet in the folder name which they were in on the first
system.
This is fine as far as the customer goes for most users. However, they
have some Vice-Presidents who want their accounts to be set up on the
second system exactly as they left the first system. They want their mail
messages in the shared directories nor refiled into their personal file
cabinets. Is there a reasonable way to do this without using transfer
user?
Any thoughts, ideas, comments, questions, etc... would be greatly
appreciated.
Thanks.
Laurie
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1943.1 | 1449 | UTRTSC::SCHOLLAERT | AJAX beats Kaiserslautern | Fri Dec 11 1992 07:35 | 9 |
Hello,
$ dir /tit=merg shows lots of topics on this issue.
Did you see 1449 ?
Regards,
Jan
| |||||
| 1943.3 | proposed steps to move messages | AIMTEC::BUTLER_T | Fri Dec 11 1992 15:44 | 40 | |
Below are the steps we are considering to move users to another system
of the same version. We are concerned here with mail messages and
other user folders. The non mail messages will be taken care of by
the asset package (.0). Please be critical and supply any information
you feel we might need.
proposed steps:
have users read all pending messages
delete old messages and those no longer needed
mail jaintor (have user EW)
all users off the system
cofy sdaf's to temp area
check for duplicates in sdaf's and remove
run sender/fetcher to clear messages (defered mail?)
shut off network
read manager's mail
remove duplicates in pending
sm_sdaf_master and sm_shared_dir_master to change file locations
The move has taken place and before any users get in:
run the assets package (.0)
need to check that it maintains attachments ?
rcf option puts attributes in pdaf?
creates identitical mail in new location
cab share on all mail messages in vp accounts
copy pdaf to sdaf
updates count for any all ready shared
moves attachments and updates counts
check for duplicates in sdaf's and remove duplicates
I am going back and insure that the customer would not prefer to
have the shared areas set up for all users. The more I holler
the more feedback I get :^).
Thanks,
Tim
| |||||
| 1943.5 | Not simple | IOSG::TALLETT | Gimmee an Alpha colour notebook... | Fri Dec 18 1992 11:15 | 28 |
All I can say is that transferring users is non-trivial (as I found
out!). Its rather like installation, at first glance you think
there's nothing to it, but when you open it up, its a can of worms.
The bit about reading pending messages is no big deal, just do a
GET_PENDING before you start and you don't need this restriction.
Things you DO need to worry about are
o Username conventions being different on the two systems
eg TALLETT on source, P_TALLETT on target.
o A1 subdirectory conventions being different. EG A1 on
the source and A1V3 on the target.
o VMS directory same as A1 subdirectory or on a different
disk.
o Shared areas being different on the two systems. The
source account may reference shared areas that don't
exist on the target system. (Don't forget attachments)
o Error recovery if things go wrong (disk space, crashes)
I'd recommend trying to understand what transfer user worries about
in order to find potential problems.
Heck, if it was easy, we'd all do it! :-)
Regards,
Paul
| |||||