Conference iosg::all-in-1_v30

    Hallo,
    
    Andrew ,
    
    Sorry that it took so long for this info, but I was not in the office.
    I hope that this info can help you.
    
    
Order in which DDS entries were created

MBMAN> build dds sub/sur=jan/name=test1/orgunit=organ1
MBMAN> add dds buil
MBMAN> build dds sub/sur=joop/name=test2/orgunit=organ2
MBMAN> add dds buil
MBMAN> build dds sub/sur=jaap/name=test3/orgunit=organ0
MBMAN> add dds buil

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

DDS lookup when creating mail from EM menu before DDS sorting enabled


                              ALL-IN-1 Directories
--------------------------------------------------------------------------------
 Select an addressee from the following:
--------------------------------------------------------------------------------
 1   JAN                 ORGAN1                     ( TEST1                  )
 2   JOOP                ORGAN2                     ( TEST2                  )
 3   JAAP                ORGAN0                     ( TEST3                  )

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

DDS lookup when creating mail from EM menu after DDS sorting enabled

                              ALL-IN-1 Directories
--------------------------------------------------------------------------------
 Select an addressee from the following:
--------------------------------------------------------------------------------
 1   JAN                 ORGAN1                     ( TEST1                  )
 2   JOOP                ORGAN2                     ( TEST2                  )
 3   JAAP                ORGAN0                     ( TEST3                  )


Contents of OA$DATA:SYSTEM.PST

DDS_SORT                      1
DDS_SORT_KEY                  .SURNAME1
LMF_USER_COUNT                
LMF_USER_LIMIT                
OA$MTI_FETCHER_CONTROL        RUNNING
OA$MTI_RS_RF_ERROR            0
OA$MTI_SENDER_CONTROL         RUNNING
OA$MUA_QUEUE                  
OA$SHUT_TIME                  
PRINT_XP_MAX_FILES            100
PSPRINT_MAX_RETRIES           5
PSPRINT_WAIT_MINS             2
    
    Regards,
    
    Luc Bervoets - Cs Brussels

    
    I'm experiencing the same problem with sorting as Luc under versions
    2.4 and 3.0.  Does anyone have the solution?  Should a sort be added to
    the EMSADD form for partial lookups?  Any suggestions?   
    
    I need a response that will be valid for a customer system.
    
    The symbol DDS_SORT_KEY is set to .SURNAME1 on my customer's system.
    Is there a way to set this symbol to sort on multiple fields?  If so,
    please provide an example or point me to where it is documented.
    
    
    Thanks
    Sherald T.
        

    
    I'm experiencing the same problem with Mail Directory sorting as Luc
    described in note 1766 under versions 2.4 and 3.0.  Does anyone have
    the solution?  Should a sort be added to the EMSADD form for partial
    lookups?  Any suggestions?  DDS is primary on my customer's system.
    
    I need a response that will be valid for a customer system.
    
    The symbol DDS_SORT_KEY is set to .SURNAME1 on my customer's system.
    Is there a way to set this symbol to sort on multiple fields?  If so,
    please provide an example or point me to where it is documented.
    
    Please let me know if I can sort on multiple fields using a BIND/SORT
    if the symbol DDS_SORT_KEY cannot be defined to use multiple fields for 
    sorting.  I can't seem to find any scripts, boilerplate files, or forms
    to use as an example that does sorting on multiple fields and that
    makes me wonder if multiple field sorting is possible.
    
    
    Thanks
    Sherald T.
        

    First answer -- the "symbol EMMDSORT" that the user can set is in the
    user's symbol table (PST). So s/he would need to do
    
    <get $EMMDSORT = ".fieldname"
    
    (note the dot ----^ )
    
    to change the system setting (which, as you discovered, lives in a
    system symbol SYS$DDS_SORT_KEY).
    
    All the code (actually, named data on such forms as DDS$INDEX) does is
    to call BIND/SORT with the named key field. As far as I can remember,
    /SORT will only take a single key.
    
    I've tried it on our system (v3.0) and it works fine. I set $EMMDSORT =
    ".givenname1" and the names appear sorted by givenname.
    
    Perhaps you can see what's going wrong by turning on the debugger or
    tracing through the index - as I say, it's all done in the named data
    and so should be easy enough to follow. One thing to check is that the
    fieldname in SYS$DDS_SORT_KEY is valid - I think it's just ignored if
    not (and you'll get the names in the order as defined by MbMan).
    
    Dave.

    Hallo,
    
    Concerning this problem .
    
    When OA$DDS_prime = 2 DDS Sorting is working when use the option SMD
    ="Search Mail Directory".
    
    It doesn't work work when you press CR at the TO-field.
    
    Is it correct when I say that when OA$DDS_PRIME = 2 the output of CR or
    FIND key must be sorted also and not only with SMD or is it only
    possible with SMD.
    
    Regards,
    
    Luc.

    Luc,
    
    I would have expected it to work in both cases. being at the TO: field
    and using SMD is two different pieces of code but they should ideally
    perform similarly. Please SPR.
    
    regards,
    
    Andrew.D.Wicks