[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

1345.0. "Problem with NETWORK.DAT" by HAN05::SCHNEIDER () Wed Sep 02 1992 16:13


  Hi,

 this is maybe a stupid question, so excuse me for asking, but I'm a little
 under pressure with my customer (Volkswagen in Germany).
 We have used the NETWORK.DAT to store addressees and in former ALL-IN-1
 versions one could use <GOLD><L> in the TO: field when creating a message to
 search for addressees and all the NETWORK.DAT entries were displayed.
 In ALL-IN-1 2.4 this not longer seems to be possible: a <GOLD><L> doesn't
 list the NETWORK.DAT entries.

 What's the trick with it ? Is it a bug or a feature ?

 Thanks in advance,

     Helmut

T.RTitleUserPersonal
Name
DateLines
1345.1IOSG::WDAVIESThere can only be one ALL-IN-1 MailWed Sep 02 1992 16:4218
    Um, that would be a bug - Network must be available - but as far
    as I know, Gold-L should work on V2.4 - so check out your
    configuration.
    
    However, note that there is some filtering done, whereby 
    Say the node is IOSG, and I'm on IOSG, then it won't display
    WDAVIES@A1@IOSG if an entry exists.
    
    Now if this is the case, then I believe there are some problem - I
    can't recall the exact details, whereby remote message routers and
    some other things can confuse it -
    
    Check out the OA$MTI* logicals - and see what is being masked out...
    and MR$NODE...
          
    This should be fixed in V3.0

    Winton
1345.3IOSG::WDAVIESThere can only be one ALL-IN-1 MailThu Sep 03 1992 10:1018
    Um - BE VERY CAREFUL !!!!!
                       
    The bug is that the filtering is done on 
    
    OA$PRIMARY_NODE  
    
    In V2.4 - this is flawed, because when there is a remote MR Node,
    OA$PRIMARY_NODE is set to MR$NODE (and thus a second Node). Thus when
    an index is done, the filtering filter outs the users from the remote
    node, not the local node!
                             
                             
    In V3.0 - The code was modified to use OA$PRIMARY_NODE if no
    Remote_MR, and then SYS$CLUSTER_NODE or SYS$NODE, if it was Remote MR.
    
    YOU MUST THINK ABOUT THIS!
    
    Please give an example of your set up, and I'll try to help.