Conference iosg::all-in-1_v30

    Here are the steps I suggest:

    1. Suggest that the system manager receive career counseling and some
       training.
    2. Do a complete backup of all the disks of the 3100 to the 4200 to
       migrate the users from the 3100 to the 4200.
    3. Make a backup copy of the PROFILE.
    4. Invoke the script provided at the end of this reply to change the
       physical device names to the corresponding logical name.  You need
       to define #PHY_NAME to be the physical name to be changed and
       #LOG_NAME to be the logical name to replace it.
    5. Repeat step 4 for each offensive physical device name.
    6. Either do a manual change to the templates or modify the script to
       operate on it.
    7. Use the Transfer Mail Area option to transfer the shared directories
       placed on DKA300 to the logical name for DKB300:.
    8. Remind the system manager that logical names are our friends and
       help make our lives better in the long term.
    9. Take credit for solving some big problems and get lots of revenue.

    Have fun,
    don

    ! CHANGE_PROFIL.SCP             Change device names in the PROFILE
    !
    ! This script changes all the profile entries which start with the
    ! value in #PHY_NAME to the value in #LOG_NAME.
    !
            FOR PROFIL WITH .DIRECT = #PHY_NAME DO -
             GET #DIRECT = #LOG_NAME OA$DIR:"*.*;".DIR[.DIRECT] \\-
             WRITE CHANGE PROFIL KEY=.%KEY,DIRECT=#DIRECT
    !
    ! [End]

    Hi,
    
    I tried the script in .1 but it did not turn out as it should.
    
    Now I have two servers, a VAXSERVER3100 and a VAX 4000-200. My
    vaxserver3100 is the original system and I installed ALL-IN-1 again on
    the VAX 4000-200.
    
    I copied the sysuaf, profile.dat and the users's directories over,
    created the change-profil.scp, logged into the ALLIN1 account of the
    new system, <get #phy_name = "DKB300:"
                <get #log_name = "user$disk1:"
                <do sys$manager:change_profil.scp
    
    It came back without any error but when I did an MGT MUA SEL MANAGER E,
    my directory is now USER$DISK1:
    
    old directory : DKB300:[allin1.mgr]
    new directory : USER$DISK1:
    should be     : USER$DISK1:[allin1.mgr]
    
    Is there something else I should do ?? I check the other user's
    directory and found the same thing.
    
    The funniest thing is when I tried the same thing on my trial system in
    the office, everything worked okay, but then I was using the same
    server, just did a backup of the profile.dat and replace the original.
    Now, in customer;s site, I have actually copied the profile.dat from
    the 3100 to the 4000-200. does that make a difference ?
    
    Am desperate, hope someone would response to this.
    
    
    ALso, on the new vax4000-200. I when into the profile.dat and had
    manually changed the directory of manager to USER$DISK1:[allin1.mgr]
    but when I tried to access EM or aby submenu, I received error -
    "error openning CAB$SDAF" - device not found, not mounted or not
    available.
    
    Any suggestions ? Will be going over to customer's site again tomorrow,
    hope will have some good news then.
    
    many thanks and regards for assisting so far,
    
    Angeline.

    It may be that the profile doesn't contain any entries for "DKB300:". 
    I suggest either turning on SCRIPT and SYMBOL trace and running the
    script again or trying the following:

                FOR PROFIL WITH .DIRECT = #PHY_NAME DO -
                 GET .USER

    This will return a list of the user profile entries which match the
    #PHY_NAME criteria.  If nothing appears after doing the above then that
    is the problem.  If one or more names (use GOLD W) appear then it may
    be that the WRITE to the profile failed.  You might want to add a check
    for OA$STATUS after it.  Looking at the output of the trace is probably
    in order if this is the case.

    The second problem you report sounds very much like A1CONFIG.DAT
    may contain the wrong devices.  You will need to use the A1CONFIG form to
    correct it.  At the least, OA$SHAR* sounds like it is not correctly
    set.

    Good luck,
    don

>    The second problem you report sounds very much like A1CONFIG.DAT
>    may contain the wrong devices.  You will need to use the A1CONFIG form to
>    correct it.  At the least, OA$SHAR* sounds like it is not correctly
>    set.

You can us forms SM_SDAF_MASTER and SM_SHARED_DIR_MASTER to
check/fix your OA$SHAR* logicals. 

    HI,
    
    I have finally successfully converted all the physical devices to their
    respective logical names.
    
    However, to do this, I had to go back to the Vaxserver3100 (original
    system), stopped the users for a while, did the conversion, copied the
    new profile.dat to the new system.
    
    It still did not work if I run the script from the Vax4000-200. I
    checked the GET .USER and GET.DIRECT and they showed the correct
    results, its only when I tried to do the WRITE CHANGE or the OA$DIR
    that it failed. Anyway, I do not have time to further check because the
    migration was supposed to be completed by end March !
    
    As for the second problem, sure enough that there was some problems
    with the OA$SHAR* directories.
    
    MANY THANKS for the assistance rendered. This notesfile has never fail
    me yet. keep it up.
    
    Regards,
    Angeline