[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

4297.0. ""Duplicate user ..." problem." by HGOCS::SIMONLAU () Tue Jun 28 1994 11:42

    Hi,
    
    A customer running ALL-IN-1 IOS v3.0 encounter the following problem:
    
    Sending mail from local node to a user ( say SIMONLAU ) at remote node
    in which another user ( say SIMONLAU1 - partial match with SIMONLAU ) had 
    been marked "DELETED" will get error "duplicate user ....." !!
    
    Note:
    1. The problem would not happen if SIMONLAU1 had not been marked
       "DELETED".
    2. The first no. of characters of two user account's name are
       identical, just like SIMONLAU and SIMONLAU1.
    3. The nodes has its own message router.
    4. The nodes share the same NETWORK.DAT.
    
    
    Any comment/idea ?
    
    Your input would be appreciated.
    
    Thanks
    Simon

T.R Title User Personal
Name Date Lines

4297.2 Confusing IOSG::MARSHALL A glitch in reality Wed Jun 29 1994 13:10 22

T.R	Title	User	Personal Name	Date	Lines
4297.2	Confusing	IOSG::MARSHALL	A glitch in reality	`Wed Jun 29 1994 13:10`	22
	Yes, .0 is clear, but why it behaves that way isn't clear! You say the two nodes "share" NETWORK.DAT. I don't understand this. Are the two nodes in a cluster? If so, then yes they are supposed to share NETWORK.DAT as it's in the cluster-wide directory OA$DATA. If they're not in a cluster, then do you have one disk for OA$DATA shared by two different systems? If you do, then it doesn't surprise me that ALL-IN-1 gets confused as I don't think it was designed to work in that configuration. For example, how do you decide what goes in the NODE field of each record? Which of the two nodes has Message Router? At what point does the "duplicate user" message appear? When you type the name in on the TO field, or when the message is sent? Is the error a message on line 24, or is it contained within a non-delivery notification? It sounds like one part of ALL-IN-1 is correctly ignoring the DELETED records, but another part is picking them up and getting in a mess as a result. But where this is happening and why I don't know. Maybe if you can answer the above questions I'll have a better idea what to look for. Scott

Yes, .0 is clear, but why it behaves that way isn't clear!

You say the two nodes "share" NETWORK.DAT.  I don't understand this.  Are the
two nodes in a cluster?  If so, then yes they are supposed to share NETWORK.DAT
as it's in the cluster-wide directory OA$DATA.

If they're not in a cluster, then do you have one disk for OA$DATA shared by
two different systems?  If you do, then it doesn't surprise me that ALL-IN-1
gets confused as I don't think it was designed to work in that configuration.
For example, how do you decide what goes in the NODE field of each record?
Which of the two nodes has Message Router?

At what point does the "duplicate user" message appear?  When you type the name
in on the TO field, or when the message is sent?  Is the error a message on
line 24, or is it contained within a non-delivery notification?

It sounds like one part of ALL-IN-1 is correctly ignoring the DELETED records,
but another part is picking them up and getting in a mess as a result.  But
where this is happening and why I don't know.  Maybe if you can answer the above
questions I'll have a better idea what to look for.

Scott