Conference iosg::all-in-1_v30

    Mario,
    
    value of OA$DDS_AREA_ROUTE? remember all Answer is doing is a reply to the
    FROM address so why does that get set wrong in the first place.
    
    v2.3? sigh! (:==:)
    
    Regards,
    
    Andrew.D.Wicks

Used for Message Router area routing?

Didn't work.

I set it by  running OA$LIB:SYSTEM_PST to write the symbol value in there.  
Am I barking at the wrong tree?

/Mario

    Mario,
    
    i'd no idea you were a dog? (:==:) i've said it 317 times but
    OA$DDS_AREA_ROUTE has nothing to do with area routing!! just go to
    EMC and do a <GET on it please....          
    
    Regards,
    
    Andrew.D.Wicks

Get returns blank.

Grrrrrrr...

/Mario

    what's OA$DDS_PRIME set to.
    

>                     <<< Note 3417.0 by CTHP12::M_MORIN >>>
>                    -< Answer doesn't go to cluster alias. >-
>
>ALL-IN-1 V2.3
>

Just to go over the basics again, to see if this rings a bell:

>A cluster with alias MOLVC has the ALL-IN-1 sender running on a node called 
>MOLIS.  Other nodes in the cluster are MOLIS2, MOLIS3, and MOLIS4.  When a 
>user sends mail remotely from this cluster to another node, the person on the 
>other end receives a broadcast message which says:
>
>	"New mail from user USERX @A1 @MOLVC"

The broadcast message (by the way, I'm assuming this is a typo - and the real 
message said 'New ALL-IN-1 mail from . . .') is generated from the ENVELOPE 
SENDER field. This is heavily manipulated by Message Router and will reflect 
the exact path taken by the message. In this case it's saying that it was 
transferred from the A1 mailbox on cluster MOLVC.

>When the user does an Answer from ALL-IN-1, it comes back with a TO address 
>of:
>
>	USERX @A1 @MOLIS
>
>Customer wants the TO address to come back with the cluster alias MOLVC 
>instead of individual node names.

When a user replies, the address is formed from the CONTENT FROM field on the 
message. This is generated by the ALL-IN-1 Sender according to the well-known 
rules. The one logical name not mentioned is OA$MTI_AREA - is this set to 
anything? If it is defined, then that will be used and appended to the 
sender's username. 

>We've already tried playing with OA$PRIMARY_NODE, MRLISTEN object ALIAS 
>OUTGOING, etc...  No success.
>

MR looks OK - it should be the A1 logicals. If OA$MTI_AREA is not defined, 
and OA$PRIMARY_NODE is set to the cluster alias you should get what you want. 
Or you can define OA$MTI_AREA to be "A1@MOLVC" Both of these methods should 
work - even in V2.3!

grahame

    >> We've already tried playing with OA$PRIMARY_NODE
    
    Hmmm, you shouldn't really 'play' with this logical; leave it to the
    value given by A1V23START.COM!  What is that value - is it the node
    name, or the cluster alias?  (I assume you're not using remote MR)
    
    The 'rules' for the addition of routing terms to an address are:
    - if OA$DDS_AREA_ROUTE is defined, append that to the username
    - otherwise, if OA$MTI_AREA is defined, append " @ " and OA$MTI_AREA
        to the username
    - otherwise, if using remote MR, append " @ " <mailbox> " @ " <mrnode>
        to the username
    - otherwise, append " @ " <mailbox> " @ " <local node> to the username
    
    <mrnode> is found from the logical OA$MTI_MR_NODE
    <local node> is found from the logical OA$PRIMARY_NODE
    
    With that info, you should be able to find the culprit in your case.
    
    Scott

Problem was resolved by rebuilding the DDS User Agent with the cluster alias 
instead of the individual node.

/Mario