|  |     
    Glad that the problem went away. What you sugessted to them is that
    the save/restore request will now execute in the context of ABS account
    instead of the requester's account.
    
    I have a feeling that the problem may surface later (just my hunch).
    I think there are some problem with ABS which happens once in a blue
    moon (Don't you love this kind of problems???).
    
    Please have your customer upgrade to V2.1 as soon as it's available.
    After V2.1 goes out, we won't be able to provide support for V1.1 code
    base.  If the problem does come back, we will be in better position to
    take a look with V2.1 running.
    
    Thanks,
    Masami
    
    Thanks,
    Masami
 | 
|  |     
    We now know the cause of the problem.
    
    The customer is using MDMS V2.8 ECO2 + SLS$TAPMGRRQ_2821_ALPHA.EXE
    renamed SLS$TAPMGRRQ.exe in SLS$custom.  This remedial image contains
    some features that does not work well with ABS.
    
    Please do not use this image along with ABS. You get unpredictable
    results such as the one reported.
    
    The customer either has to back off the remedial image, or upgrade to
    V2.8A (in SSB now) MDMS to fix the problem.
    
    Thanks,
    Masami
 |