[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

2008.0. "XMDK Only allows 32 accounts to transfer?" by WAYOUT::CLARKE (The Cat in the Hat comes back.) Tue Dec 22 1992 17:28

ALL-IN-1 V2.4 Patched up to 603, VMS 5.4

A customer has reported to me that using the multiple move disk option (from SM
MUA I XMDK) if one of the first 32 accounts fails with an error, then all the 
accounts from 33 upwards will fail with the same error when it is not valid.

I am off for my Christmas break now and do not expect a small Microvax with 
ALL-IN-1 V2.4 installed from Santa to enable me to troubleshoot this on 
Christmas day.

Bearing this in mind, could somebody who has used this option for more than 32
accounts confirm/deny this? This information would be useful even if you were
using a V3.0 environment.

Thanks

Aston
T.RTitleUserPersonal
Name		DateLines
2008.1A customer has the same problem in 3.0TINNIE::SETHIAh (-: an upside down smile from OzTue May 04 1993 04:1741
    Hi,

    It's a bit too late Christmas has come and gone but Santa is delivering
    late Christmas presents :-).

    A customer has reported the above problem on a 3.0 system with 20 users
    being moved.  Apart from the known problem where XMDK misses the first
    user on the list it seems that this is an additional problem in 3.0.

    What the customer found was that the error message in the logfile was:
    
    Get the next account
    Starting to process ALL-IN-1 username BOWIED
    Disable the VMS account
    Check for several ALL-IN-1 accounts sharing a VMS account
    VMS account is NOT shared
    Check the UAF directory has been set correctly
    Compare first element of profile with first of UAF directory
    Make spec for moving directories from the UAF entry
    Examine quota on source disk  <----
    Failed to move that account   <----
    
    This occured for every single user there after.
    
    Further on in the file the following error message was displayed:
    
    %OA-E-OAFE, Unknown, ambiguous, or invalid function """
    %OA-W-QUO_NODISKQUOTA, There is no diskquota entry for this user on
    this volume
    
    The customer checked for diskquota and found there was not a problem
    and managed to move users individually. 
    
    Is this a known problem or a new one ? I will SPR this if the customer
    wants me to or to save me paperwork can it be put on our database of
    known problems ?
    
    Regards,

    Sunil
2008.2This could be a bug. Customer does not want to raise SPRTINNIE::SETHIAh (-: an upside down smile from OzWed May 05 1993 02:0215
    G'day All,
    
    I asked the customer if he would like to SPR this and he has said no as
    they are moving to TeamLinks.
    
    I know this is not a bug reporting conference I just want ALL-IN-1'er
    to be aware that this could be a misfeature/bug in our greatest and
    dearest product.
    
    If it can be confirmed and added to the list of misfeatures /bugs to
    fix in IOSGland all the better :-).
    
    Regards,
    
    Sunil
2008.3I miss all those holidays in Mar/Apr/MayAIMTEC::WICKS_Aon the Streets of San FranciscoWed May 05 1993 04:3210
    sunil,
    
    if this were still a problem in a mythical PFR then I imagine we could
    QAR it if we were an FT site since that requires much less paper work
    and bureaucy - hypothetically with the approval of an IOSG based-mod
    that is assuming they aren't still on holiday.
    
    Regards,
    
    Andrew.D.Wicks
2008.4Fine with me!IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeTue May 11 1993 14:508
    Personally I'm happy to have it reported internally by anyone who cares
    to reproduce it first.
    
    However, if the customer doesn't want to raise it as a bug, then it
    will have much less significance reported internally if we can't tag it
    with "customer problem".
    
    Graham (Back from holiday :-) )
2008.5BUSHIE::SETHIAh (-: an upside down smile from OzMon May 24 1993 03:1213
    Hi Graham,
    
    The customer did not want to go any further and said no to SPRing it as 
    because they are moving to TeamLinks.  Well informally through this
    conference others will be aware of the problem and if it's reported by
    a customer maybe they could SPR it.
    
    Sorry mate I could get the customer to change their minds !!!!
    
    Regards,
    
    Sunil