| Ann,
Perhaps this STARS article can help...
Regards,
Jan
"How to Copy Files From One User to Another User Account"
COPYRIGHT (c) 1988, 1989, 1990 by Digital Equipment Corporation.
ALL RIGHTS RESERVED. No distribution except as provided under contract.
PRODUCT: ALL-IN-1 V2.2 and V2.3
OP/SYS: VAX/VMS
SOURCE: Customer Support Center/Atlanta USA
\by Faith Donohue - A890713778
\SRA901220002170 OA669 OA2606 OA2996
PROBLEM:
A user has left and the system manager wants to move the user's
ALL-IN-1 documents to another existing ALL-IN-1 user.
SOLUTION:
The WPCOPY script is meant for migrating a WPSPLUS user to ALL-IN-1,
but works well in most cases for merging 2 ALL-IN-1 users. However,
there may sometimes be some eccentricities in the copy process, due to
this fact. For example, the document titles may not be transferred,
this field may be blank on the recieving file cabinet.
With this in mind, you can use WPCOPY this way:
1. Make sure all the unread mail is read in the account
that you wish to copy files from. Delete unwanted files
and empty the wastebasket.
2. Log into the ALL-IN-1 manager's account.
3. Go into ALL-IN-1 and, from the WP menu, enter the
command:
<DO OA$LIB:WPCOPY
4. Answer the questions asked for the full directory
specification of the account to copy files from, then
answer the questions for the account to copy the files
to. (It needs the directory specification for both file
cabinets eg. device:[smith.a1] )
5. After verifying that the files have been successfully
copied into the destination account, you can delete the
source account from ALL-IN-1.
\
\ Here is an alternative solution that has some limitations. This second
\ method should NOT normally be used, but might be helpful for some
\ situations, and contains some useful information:
\
\ 1) Have the users read all of their new mail (EM RN), and delete un-needed
\ mail and documents to reduce the chances of having duplicate keys later.
\
\ 2) Use the VMS Convert utility to merge the DOCDB.DAT and DAF.DAT files.
\
\ $ CONVERT/FDL=OA$LIB:DOCDB.FDL/EXCEPTIONS=OTHER.DAT -
\ DOC1.DAT,DOC2.DAT DOCDB.DAT
\
\ Where DOC1.DAT is the DOCDB.DAT from one user account and DOC2.DAT is
\ from the other. The /EXCEPTIONS= allows for duplicate records that
\ may be encountered. This file should be read, because if duplicate keys
\ are found, the resulting file cabinet will NOT have the pointers to
\ some documents. You should be aware that the DOCDB.DAT may have multiple
\ records with the same key if a document has been cross filed. If the
\ documents associated with the duplicate keys are important, they can be
\ saved, the merge done, and then retrieved with DT SV FILE.WPL, then the
\ merge, then DT RV FILE.WPL.
\
\ The same procedure needs to be done for the user's DAF.DAT files, as the
\ DOCDB.DAT and DAF.DAT together make up a useable file cabinet.
\
\ The files in the first user's subdirectories (eg. [.DOC1] thru [.DOC9],
\ [.MSG], and [.UDP]) need to be be copied to the respective directories
\ for the target user, except for those that had duplicate keys. Do NOT copy
\ the files corresponding to the duplicate key records in "OTHER.DAT" above;
\ if you did this you would be writing over one of the target user's files!
\ After all files that should be moved, have been moved, insure that all
\ files have the correct ownership and file protections with:
\
\ $ DIRECTORY/SECURITY [...]*.*
\
\ Notice that this method is more work than the above method of using a
\ script. However, this method is a general method for merging 2 indexed
\ files, applied to an ALL-IN-1 problem. It also illustrates some of the
\ potential problems with merging file cabinets.
\
\ This second method is NOT the recommended one in most cases.
\
\\%QX902
\\OA1
\\ESDP ATL
|
| this .5 sounds like what we want. a couple of ?'s though -
1. what other/if any excentricities might happen?
2. if, for example, the documents lose their titles on the
receiving end, are the documents left in the original account so we
could try another way?
ann
|