Node install with MQ client and separate queue manager

[J-P Plourde]

While trying different installation combination, with hit a roadblock with this one.

We do a Node installation on a machine running MQ client, that connects to a separate QM before reaching the QM where the Entreprise node is connected.

Installation and registration to the Entreprise node worked perfectly. Channels and QM aliases are defined so MQ connecticty is correct.

Problem is that when trying to initiate a file transfer, the commands don't reach the client node because they are sent to the client node MIM.FTS (which was not in the queues.mqs generated by the install). However, client node is listening on MIM.FTS.NODENAME, as per queues.mqs definition.

Any insight ?

MIM 8.5.2 on Windows 2003 (32 bits).

[Ethan Beisher]

Can you list the queue definitions and queue manager aliases on each queue manager that is related to the client node?

[J-P Plourde]

Entreprise node QM;

LOCAL    ('MIM.COORDINATOR')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.COORDINATOR.DISP.CLIENT')    DEFPSIST(NO)    USAGE(NORMAL)
QLOCAL    ('MIM.COORDINATOR.DISP.SERVER')    DEFPSIST(NO)    USAGE(NORMAL)
QLOCAL    ('MIM.COORDINATOR.REPORT')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.COORDINATOR.TRACE')    DEFPSIST(NO)    USAGE(NORMAL)
QLOCAL    ('MIM.DIRECTORY.SERVICE')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.DIRMON.SERVICE')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.DIRMON.SERVICE.RECOVERY')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.ECHO')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.EXIT')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.FIXIT')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.FTS')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.FTS.DATA')    DEFPSIST(NO)    USAGE(NORMAL)
QLOCAL    ('MIM.FTS.ICC')    DEFPSIST(YES)    USAGE(NORMAL)
QMODEL    ('MIM.IMMEDIATE.MODEL')    DEFPSIST(NO)    USAGE(NORMAL)
QLOCAL    ('MIM.MERGE')    DEFPSIST(YES)    USAGE(NORMAL)
QMODEL    ('MIM.PERMANENT.MODEL')    DEFPSIST(NO)    USAGE(NORMAL)
QLOCAL    ('MIM.REJECTED.MESSAGES')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.STATUS')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.STATUS.EXCEPTION')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.STATUS.QUERY')    DEFPSIST(NO)    USAGE(NORMAL)
QMODEL    ('MIM.TEMPORARY.MODEL')    DEFPSIST(NO)    USAGE(NORMAL)
QLOCAL    ('MIM.TRANSFORMATION.SERVICE')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.USER.SERVICE')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.WSE.DISP.SERVER')    DEFPSIST(NO)    USAGE(NORMAL)
QLOCAL    ('MIM.WSE.JAVA.DISP.SERVER')    DEFPSIST(NO)    USAGE(NORMAL)
QLOCAL    ('MIM.WSE.JAVA.ECHO')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.WSE.JAVA.W3C.ECHO')    DEFPSIST(NO)    USAGE(NORMAL)
QLOCAL    ('MIM.WSE.JAVA.WEBSERVICE.REQUESTER')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.WSE.SCRIPT.ECHO')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.XMITQ')    DEFPSIST(YES)    USAGE(XMITQ)
QREMOTE    ('NODEB')    DEFPSIST(NO)     RNAME('')        RQMNAME('NODEB') XMITQ('XMITQ.TO.NODEB')
QLOCAL    ('XMITQ.TO.NODEB')    DEFPSIST(NO)    USAGE(XMITQ)

Node QM;

QREMOTE    ('ENT_NODEB')    DEFPSIST(NO)     RNAME('')        RQMNAME('ENT_NODEB')     XMITQ('XMITQ.TO.ENTB')
QLOCAL    ('XMITQ.TO.ENTB')    DEFPSIST(NO)    USAGE(XMITQ)
QLOCAL    ('MIM.DIRMON.SERVICE.NODEB')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.DIRMON.SERVICE.RECOVERY.NODEB')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.EXIT.NODEB')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.FTS.DATA')    DEFPSIST(NO)    USAGE(NORMAL)
QLOCAL    ('MIM.FTS.ICC')    DEFPSIST(YES)    USAGE(NORMAL)
QLOCAL    ('MIM.FTS.NODEB')    DEFPSIST(YES)    USAGE(NORMAL)
QMODEL    ('MIM.IMMEDIATE.MODEL')    DEFPSIST(NO)    
QMODEL    ('MIM.PERMANENT.MODEL')    DEFPSIST(NO)    
QLOCAL    ('MIM.REJECTED.MESSAGES')    DEFPSIST(YES)    USAGE(NORMAL)
QMODEL    ('MIM.TEMPORARY.MODEL')    DEFPSIST(NO)   

[Ethan Beisher]

It looks like you have an MQ routing error. Generally your client node name should not be the name of any of your queue managers.

- Change the name of your client node to something other than NODEB (let's say NODEB1

- Create a queue manager alias on ENTB that sends traffic routed for NODEB1 to NODEB using the MIM.XMITQ queue

QREMOTE    ('NODEB1')    DEFPSIST(NO)     RNAME('')        RQMNAME('NODEB') XMITQ('MIM.XMITQ')

- Make sure your MIM Transmit Queue Service is running

[J-P Plourde]

Made the change you proposed (that was our original setup - we changed it since it didn't work to begin with) but same results.

Is there a way we could re-configure the client node to listen to the MIM.FTS queue instead on MIM.FTS.ClientName. Not the best solution but it would make things work.

[Ethan Beisher]

You can install the node as a server node, but I do not recommend this. You need to get your WMQ Intercommunication correct.

I recommend you place a call to our Helpdesk. They can walk you through this process.

Ethan

[J-P Plourde]

Alright. We made a step further as it appear that the routing to the MIM.XMITQ needed a restart of the Coordinator processes after we made the change.

We can now see the that the messages are going through the MIM.XMITQ and Transfer Service process. However, the request now dies at the receive step;

<message2>MQ error opening queue :MIM.FTS.NODEB1(2,2085,MQRC_UNKNOWN_OBJECT_NAME)</message2>

 ...on the entreprise QM... and the data is now in the entreprise FTS.DATA queue. Opening a ticket.

[Ethan Beisher]

That looks better. Now you need to be able to get the messages over to the queue on NODEB. You can do this using a clustered queue or using a remote queue definition.