Conference iosg::all-in-1_v30

3516.0. "MDK problem is the user has a DMW's file cabinet" by GIDDAY::SETHI (Recompense injury with justice) Wed Nov 10 1993 00:43

    Hi All,                                                            
    
    For all those who don't like cross-posted note, I am sorry I just
    though that I would raise peoples awareness.
    
    At the bottom of the note I have a quick and nasty solution is there a
    better way around this problem from the ALL-IN-1 IOS point of view ?
    
    Regards,
    
    Sunil
    
         <<< ABBOTT::ABBOTT$DUA1:[NOTES$LIBRARY]MAILWORKS-VMS.NOTE;1 >>>
                               -< DEC MAILworks >-
================================================================================
Note 230.0   Move user to another disk problem if ALL-IN-1 IOS used   No replies
GIDDAY::SETHI "Recompense injury with justice"       37 lines   9-NOV-1993 19:16
--------------------------------------------------------------------------------
    Hi All,                          
    
    This is an interesting little problem that I feel engineering has to be
    made aware of as well as fellow ALL-IN-1'ers and DMW'ers.  A customer is 
    using TeamLinks as their UI and have DMW 1.2 installed and ALL-IN-1 IOS 
    3.0.
    
    The customer uses the ALL-IN-1 IOS System Managers option to move user
    to another disk.  This works fine until it comes to backing up the
    [.A1MAIL$] sub-directory you get the following error messages:
    
    %BACKUP-S-CREATED, created DSA1:[UABEEL.A1MAIL$]050N8H4N.X4H;1
    %BACKUP-E-OPENOUT, error opening DSA1:[UABEEL.A1MAIL$]0813E9CN.001;1 as
    output
    -RMS-E-PRV, insufficient privilege or file protection violation
    %BACKUP-E-OPENOUT, error opening DSA1:[UABEEL.A1MAIL$]0813E9CN.X4H;1 as
    output
    -RMS-E-PRV, insufficient privilege or file protection violation
    
    etc...
    
    Some files are copied others aren't the protections aren't always
    consistant for some reason on the files.
    
    Also it must be noted that the DMW's the users profile namely the
    MAIL_DIRECTORY attribute needs to be updated manually.  The customer
    could customise ALL-IN-1 IOS to take this into account.  However I feel
    that both engineering groups need to take into consideration the
    possiblity of a user having both types of File Cabs.
    
    The solution in this case would be for the customer to move the DMW's
    account and than move the ALL-IN-1 IOS account as a quick and nasty
    solution.  I will cross-post this in the ALL-IN-1 IOS conference.
    
    Regards,
    
    Sunil

    Hi All,
    
    The customer has raised the issue that this is a bug and would like to
    raise an SPR.  Do we have anything logged in our database for this
    problem ?
    
    Can any workarounds be suggested ?  Currently the customer has/will
    customise(d) ALL-IN-1 and add a line such as $ set proc/priv=bypass.  I
    don't think this is a good thing any comments would be appriciated.
    
    Regards,
    
    Sunil

    Hello sunil,
    
    I don't think it is reasonable to expect that ALL-IN-1
    has knowledge of the "tranfer user to other disk" functionality
    of other products. This is an easy one. Just a matter of file 
    protection. You will have to use bypass. But what about
    application which use an Rdb database in a users subdir which
    contains fixed disk names.....
    
    Regards,
    
    Jan
    

        PATHWORKS does an equivalent.  If you delete a PATHWORKS user, all
        subdirectries not associated with PATHWORKS are deleted as well.
        PATHWORKS says this is not their problem.
        
        Dave Zaniewski

    Hi Jan and Dave,
    
    Thanks for your input I just don't like using BYPASS if that the way
    around this problem than there is not much we can do.  I did give the
    customer the following alternatives:
    
    1. Write a command procedure/do manually the move of the DMW's account
       first than move ALL-IN-1 account.
    
    2. Have the ALL-IN-1 IOS and DMW's accounts on different disks as some
       of our customers are doing this because of the extra diskspace
       requirements of DMW's.
    
    Thanks again,
    
    Sunil