[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

2464.0. "EM C Finds both profile and local Network entry" by KERNEL::COOPER (Suzanne Cooper UK Customer Support (833)3502) Wed Mar 24 1993 11:56

I have a question based on part of the explaination given in 497.5
    
>If you aren't using DDS, then ALL-IN-1 searches the profile, followed by
>NETWORK.DAT (plus other stuff irrelevant to this discussion).  As local users
>are stored in NETWORK (so that other nodes can pick them up as remote addressees
>via the UA housekeeping job) as well as Profile, you'd see all local users
>twice if you did a FIND for mail addresses.

>Obviously this isn't very good, so the searching code ignores all local users
>in NETWORK, based on the NODE field as already described.

    How does ALL-IN-1 use to search so that the local network entries get
    ignored?
    
    My problem is that on one node in the cluster all appears correct i.e.
    find in em c just finds the profile entry, but the other node find both
    the profile and network entry.
    
    Thanks in advance
    
    Suzanne
T.RTitleUserPersonal
Name
DateLines
2464.1What's in a (node) nameUTRTSC::SCHOLLAERTHolland - San Marino : double digits...Wed Mar 24 1993 12:329
    Hello Suzanne,
    
    I think ALL-IN-1 displays those records from NETWORK.DAT which contain
    a Node field not equal to the local node name. On a cluster
    the match should be cluster alias. 
    
    Regards,
    
    Jan
2464.2KERNEL::COOPERSuzanne Cooper UK Customer Support (833)3502Wed Mar 24 1993 13:096
    The node name field in profile is blank,  the Network records have the 
    cluster alias.  i.e there must be something set incorrectly so that the
    search doesn't identify that the network records belong to that
    node/cluster, hence my question.
    
    Suzanne
2464.3More on NETWORK records for the local node being omittedSCOTTC::MARSHALLSpitfire Drivers Do It ToplessWed Mar 24 1993 13:4915
The 'Node' field in the profile has nothing to do with this.  I don't even know
what it's for (although I'm sure Dave T will enlighten us :-), but don't worry
about it for this problem.

The search should omit any NETWORK records whose NODE field is the same as
OA$PRIMARY_NODE.  There is a subtle bug in this area (possibly fixed in a
PFR :-) if you have a remote message router.  I assume you don't, so this won't
be your problem.

As you say the problem only occurs on one node in the cluster, it seems most
likely that OA$PRIMARY_NODE is being incorrectly defined on that node.  Check
its value on all nodes in the cluster: assuming you have a local message router,
and are running ALL-IN-1 V3.0, its value should be the cluster alias.

Scott
2464.7ClarificationSCOTTC::MARSHALLSpitfire Drivers Do It ToplessWed Mar 24 1993 18:248
>> Scott's reply which started talking about the NODE field in the Profile
>> when all the previous replies were talking about the NODE field in NETWORK

Not quite.  .2 mentioned the profile field, which is why in .3 I said to
ignore it.  I know better than to mention obscure profile fields for no
reason :-)

Scott