[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

3001.0. "DDS, TM Delete event calls selection list" by AIMTEC::WARRENS_R (I am successful IFF you are successful!) Tue Jul 13 1993 21:07

    Has someone seen or been able to reproduce an occurrence like the
    following:
    
    OA$DDS_PRIME = 2 (linked okay, etc.)
    allin1/nocust
    ALL-IN-1 V3.0(-1)
    
    TM EP C(reate and event)
    do all the date and time things, and add attendees.
    
    The attendees added will eventually cause the problem. So far the most
    reliable pattern of attendees is:
    
    first is local ALL-IN-1 user
    second is 'bad' (see below)
    third is local ALL-IN-1 user
    
    (whether or not the first and third really have to be local, is
    unknown.)
    
    The 'bad' address seems to be a remote mail address that is in the DDS,
    has a surname value equal to others (in this case there are three), and
    that the mail system is not ALL-IN-1 (say PROFS).
    
    ...
    Continue on with creating the event, and all works fine, the users are
    sent their event notices.
    
    However, the scheduler decides to DELETE this event.
    
    After the proper event is seleceted and displayed (including ALL the
    correct attendees), the user is placed on the DDS selection list to
    choose the user who is 'bad'. Actually an incorrect selection can be
    made at this time, with no error reporting.
    
    EMSDDS is invoked at this point, and a selection list is being built.
    
    But I have no clue as to why this would happen. Thus I cannot
    reproduce. If anyone can, I could use that to report the bug.
    
    Thanks
    
    Randy Warrens
T.RTitleUserPersonal
Name		DateLines
3001.1You don't want to know what TM does!IOSG::CHINNICKgone walkaboutWed Jul 14 1993 10:5226
    Hi Randy,
    
    I'll tell you what causes EMSDDS to pop up...
    
    This form is invoked from the MAIL address validation code to select
    DDS adresses where they are non-unique by surname. Looking at the TM
    code, I think that this has a call to the address validation routine. 
    
    I know that TM does some very strange things with address lists - for a
    delete it will be trying to send some cancellation mail - but I didn't
    expect that it would have any validation on the list at that point. 
    
    Looking at the code however, shows that the TM code does revalidate 
    addressees for reschedule type operations which includes cancellation
    of meetings.
    
    So... the question is how did the bad address get validated in the first
    place when you created the meeting? The create meeting form should be
    invoking the OA$MAIL_ADD_ADDR data-set to perform recognition and
    validation of the address.
    
    I'll let someone else speculate on that! My only suggestion is to make
    sure that ICF 14 is installed because it fixes some DDS problems.
    
    Paul
3001.2AIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Wed Jul 14 1993 14:025
        Thanks Paul!  That gives me a better clue where to look.  I
        thought this was the case based on some information Debbie H. sent 
        me.  I was going to investigate when time permitted.
        
        Dave pinch hitting for Randy
3001.3Please explain in layman termsTRIGG::VOGELSteve Vogel - Ralston/Eveready & Emerson Sales SupportFri Sep 10 1993 18:1215
    I have a customer that has just set DDS to PRIME and is seeing the
    issue listed in this note.  That is, when responding to a schedule
    request, the user (SMITH) is prompted to select his own Name/Address
    from a list of Smith(s) in DDS.  While this works (provide he picks the
    entry that is himself) they find it disturbing that the computer
    doesn't already know who they are.
    
    Could someone explain what's happening and whether or not the SURNAME
    is the only connection between ALL-IN-1 and DDS.  What about the ID
    number, doesn't it tie these together?
    
    Thanks,
    
    Steve
3001.4AIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Mon Sep 13 1993 14:0611
        Time management only writes the address into the ATTENDEE.DAT
        file.  That's how it determines who's attending the event.
        
        When you choose an address that is an ALL-IN-1 user, and your
        ALL-IN-1 naming convention is last name, you've got problems. 
        This address is unique in the ALL-IN-1 environment
        (OA$DDS_PRIME=0), but since global addressing (OA$DDS_PRIME>0)
        uses the surname and there may be 1000 SMITH's in your address
        list, it's no longer unique.
        
        Dave Zaniewski
3001.5Anything being done to fix this?TRIGG::VOGELSteve Vogel - Ralston/Eveready & Emerson Sales SupportTue Sep 14 1993 17:276
    Is there any engineering work being done to fix this annoyance?  I
    assume that it is not a simple fix if TM would need to use more than
    just the lastname.
    
    /Steve
3001.6What's wrong with using the user's profile?TRIGG::VOGELSteve Vogel - Ralston/Eveready & Emerson Sales SupportTue Sep 14 1993 17:404
    Why can't it get the user's name/address from his/her profile?
    
    /Steve
3001.7AIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Tue Sep 14 1993 18:393
        Because that's not a valid ALL-IN-1 address!
        
        Dave Zaniewski