Conference iosg::all-in-1_v30

    Fred -
    
    i've been transferring users at my customer site for a while. i just
    finished a project with 71 tranfers!
    
    the things i've learned i've put into a checklist:
    
    	night before the move on the sending system:
    
    	1. run EW on accounts to be moved
    		this could even be done just before the move itself on
    		an individual basis.
    	2. run TRM on accounts to be moved
    	3. make sure oa$transfer area is set up and has enough space.
    
    	day of move on sending system:
    
    	1. disuser the account at VMS level
    	    this will ensure that the user can't get into the account
    	     and accidently mess it up.
    	2. <newdir to the account and run EW if not run the night before
        3. make sure that the unread_mail_count is correct
    	   if it is not the account will not PAT properly
        4. start the PAT on the sending system
           remember to do 1 account at a time.  its takes longer, but if
    	    there is a problem and you need to restore the account, it will
    	    be easier to locate problems.
    	5. after PAT is done, <newdir to account and set up autoforward to
    	   the new system.
    	   also undisuser the VMS account.
    
    on the receiving system:
    
    	1. create the accounts ahead of time.  it can be done when accounts
    	   are transferred, but if anything goes wrong, its one less area
    	   to search thru for problems.
    	2. make sure logical oa$loaduser is set with enough space.
    	3. do the MAS-MAN
    	4. after the tranfer is done i like to newdir into account and
           read a few message, to make sure they all transferred ok.
        5. like with the PAT, only do 1 user at a time. 
    
    
    >>4. Someone also mentioned there was a ALL-IN-1 user document sizing tool. 
       How can I get hold of it ?
    
    	could this be the option LF (List Folder)?  this will tell you how
    many documents a user has.  its helpful cause it will help you guess
    how long the process might take.
    
    >>2. the time mnagement transfer utility
    
    	contact the wonderful people in the charlotte office and they can
    give you specifics on this.  my customer didn't want to take the extra
    money to pay for this. so when it came to transferring calendars,
    events transferred. but anything that had to do with remote users
    didn't. 
    
    
           

    
    Hi there!
    
    
>    1. Is there really a problem with V2.4 User transfer ? (If we do it right)
    
    Quite a few bugs were fixed in V3.0, but they were mainly "unusual" things
    that transfer user didn't expect. Stuff like spaces and quotes in
    usernames, VMS directory on a different disk to A1 directory etc.
    If PAT doesn't find anything strange in the account then it usually
    works. (The CSC may have other experiences!) It does take a LONG time,
    and it does use LOADS of diskspace 100,000 - 300,000 blocks. If it goes
    wrong it often leaves the source account badly damaged and you have to go
    into the internals to figure out how to restore it. Its usually easier to
    restore from backup. This was also fixed in V3.0.
    
    Create a dummy account with a few mail messages in it and get that
    working before you try the real thing.
    
>    2. Someone mentioned there's a TMTU (Time Management Transfer Utility). Is 
>       it available on the network ?
    
    Leah Phillips on SHALOT:: used to handle product management type issues
    for this package, although I'm not sure if she still does. It'll cost
    you though...
    
>    3. I've also seen many times on this conference that someone mentioned 
>       there's a STARS article for some valuable information. Is this a 
>       conference or what ?
    
    STARS is the official database used by the CSCs to store problems and
    solutions. Contact your friendly CSC and ask them to trawl it for
    V2.4 TU problems.
    
>    4. Someone also mentioned there was a ALL-IN-1 user document sizing tool. 
>       How can I get hold of it ?
    
    I think there is an undocumented script in the V3.0 kit to do this,
    I'll check.
    
>    5. How does CAB SHARE work to refile personal doc. to the shared area ?
    
    It moves a personal doc into the shared areas and updates your pointer
    to point to it. What do you need to know?
    
    All the advice in .1 is good advice. My one comment:
    
>	5. after PAT is done, <newdir to account and set up autoforward to
>    	   the new system.
>    	   also undisuser the VMS account.
    
    Setting up autoforward can be done automatically by PAT. Also I'd
    leave the account DISUSERED, since you don't really want the user
    changing stuff in his VMS account that you just moved.
    
    Regards,
    Paul

    Thanks for the quick replies. My query about CAB SHARE is that I wonder
    how CAB SHARE figures out which documents can be shared by which users?
    If CAB SHARE just refiles the personal messages to the share area, I
    wonder if it will save any disk spaces at all ?
    
    Also, can someone give me a rough figure on how long it is going to
    take to transfer a users with roughly 300 messages in the folder and
    2000 blocks of files? You can assume a VAX 4500 with RF72 disk and TK50
    as the media.  

    You spotted it! 
    
    CAB SHARE doesn't save any disk space at all; it does however shift the
    quota burden from the user to "the system" (i.e. ALLIN1). All it does
    is to move the text file out of the user's directory structure into the
    OA$SHARxyyyy: structure, and change pointers appropriately.
    
    There is, however, a function in v3.0 called CAB NEW_SHARER which makes
    the current user a(nother) sharer of a document which is already in the
    shared area. Clearly this can save disk space if used in the right
    applications.
    
    "Also, can someone ..." -- sorry, no idea.
    
    Dave.