[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

1582.0. "can't remove remote or PAPER MAIL attendees" by TOPPER::BARHAM (Norbert:) Thu Oct 08 1992 17:40

    ALL-IN-1 3.0
    
    Has anyone noticed that, if you schedule an event with attendees in v3.0
    then you cannot later remove attendees (RA) that are either remote
    (USER@A1@NODE) or PAPER MAIL addressees. This was possible in 2.4 and
    is a *BIG* issue with one of our large customers.
    Any comments on a future fix? I think they will require a CSP if there is
    no fix in the pipeline.
    
    Thanks in advance.
    
    Clive
T.RTitleUserPersonal
Name		DateLines
1582.1SPR time.AIMTEC::WICKS_AXYLANA: Hound of the BackslashersThu Oct 08 1992 18:1716
    Clive,
    
    Please no comments about any PFP ...
    
    You are right (of course) that this is one of the opportunities for CSC
    job security that was added to the TM subsystem in v3.0 and of course will
    require an SPR from you as I don't think that the 'entire' TM
    development team follow this notesfile.
    
    I am sure that my 'dead products' consultant Dave Z can explain all.
    that is happening and any possible workaround but I can reproduce this
    problem on all my v3.x variant systems.
    
    Regards,
    
    Andrew.D.Wicks
1582.2Nice featureAIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Fri Oct 09 1992 22:154
        I agree with Andrew.  Submit the SPR.  I never played with this
        during field test.
        
        Dave Zaniewski
1582.3LOOKIN::BARHAMNorbert:Wed Oct 14 1992 11:517
    Sorry boys, it's going to be a bit higher than an SPR :-
    
    If you try and remove a PAPER MAIL addressee it goes into a loop that
    brings the processor to its knees. You can escape the loop with a
    Ctrl-C but your average user doesn't know that. CLD time me thinks.
    
    Clive
1582.4Do what is rightAIMTEC::WICKS_AXYLANA: Hound of the BackslashersWed Oct 14 1992 16:558
    Clive,
    
    No need to apologise to us, if it takes a CLD or two to get TM fixed
    then that's the right thing for the customer and DIGITAL.
    
    Regards,
    
    Andrew.D.Wicks
1582.5Problem is case-sensitivityIOSG::PARTONJHands, hold you poison or grapes?Tue Oct 20 1992 18:4416
    Clive,
    
    I'm looking into a solution for this problem which, as far as I'm 
    aware, centres around case-sensitivity. In the meantime I suggest the
    following workaround:
    
    Modify the following forms, changing the FMS attribute on field ATENDE
    to UPPERCASE ONLY:
    
    	SCHDMA
        SCHDMAUISCAN
        TMMERA
    
    Regards,
    
    Jonathan.
1582.6COMICS::BARHAMNorbert:Fri Oct 23 1992 17:2911
    Thanks Jonathan,
    
    Unfortunately the customer is only 50% happy as this will not cover all 
    cases. e.g. when users use NIcknames or DLM Create Distribution list
    from mail message, as these typically contain a mix of upper and lower 
    case addresses. We need to cater for all sources of lower case
    addressing as there will be many from previous versions of ALL-IN-1...
    
    Thanks
    
    Clive