Unexpected CSQX202E messages with multi-instance queue
managers
MattLeming |May 15 2016 Updated
I was at an MQ conference in Germany a few weeks ago when a customer asked a question about multi-instance queue managers.
They had a sender channel configured, on a z/OS queue manager, using a pair of IP-addresses in the CONNAME field to a multi-instance queue manager running on Linux. In this particular case the multi-instance queue manager was running on the second IP-address out of the pair, and the customer was surprised that they got a CSQX202E message in the chinit logs. The message was output by the sender channel as a result of the failed attempt to connect to the first IP-address of the pair. The sender channel then successfully attempted to connect to the second IP-address in the pair and so started successfully.
The customer was surprised by this, but I investigated and confirmed that this is expected and that the same behaviour occurs on distributed but with a different message: AMQ9202.
Unfortunately the MQ KnowledgeCentre pages for these messages don't describe this behaviour. I will be getting them updated soon.
For reference, on z/OS if you try this out with a sender channel configured with something like CONNAME(9.78.95.164(1414),9.78.95.165(1414)) where the multi-instance queue manager is running on ip-address 9.78.95.165; you will get the following in the chinit job logs:
+CSQX500I !MQ21 CSQXRCTL Channel TO.LQ1 started
+CSQX202E !MQ21 CSQXRCTL Connection or remote listener unavailable, 808
channel TO.LQ1
connection 9.78.95.164
TRPTYPE=TCP RC=00000468 (ECONNREFUSED) reason=00000000
DISPLAY CHSTATUS confirms that the channel is actually running using the second ip-address:
CSQM201I !MQ21 CSQMDRTC DIS CHSTATUS DETAILS 854
CHSTATUS(TO.LQ1)
CHLDISP(PRIVATE)
XMITQ(LQ1)
CONNAME(9.78.95.165)
CURRENT
CHLTYPE(SDR)
STATUS(RUNNING)
SUBSTATE(MQGET)
STOPREQ(NO)
RQMNAME(LQ1)
END CHSTATUS DETAILS
CSQ9022I !MQ21 CSQMDRTC ' DIS CHSTATUS' NORMAL COMPLETION
If the sender channel is actually on distributed you get the similar messages in the queue manager error logs
15/05/2016 20:34:47 - Process(13660.1) User(MUSR_MQADMIN1) Program(runmqchl.exe)
Host(MATT_LEMING-PC) Installation(Installation7)
VRMF(9.0.0.0) QMgr(LQ2)
AMQ9002: Channel 'TO.LQ1' is starting.
EXPLANATION:
Channel 'TO.LQ1' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
15/05/2016 20:34:48 - Process(13660.1) User(MUSR_MQADMIN1) Program(runmqchl.exe)
Host(MATT_LEMING-PC) Installation(Installation7)
VRMF(9.0.0.0) QMgr(LQ2)
AMQ9202: Remote host 'sig-9-78-95-164 (9.78.95.164) (1414)' not available,
retry later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'sig-9-78-95-164
(9.78.95.164) (1414)' for channel TO.LQ1 was not successful. However the error
may be a transitory one and it may be possible to successfully allocate a
TCP/IP conversation later.
In some cases the remote host cannot be determined and so is shown as '????'.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
10061 (X'274D'). The reason for the failure may be that this host cannot reach
the destination host. It may also be possible that the listening program at
host 'sig-9-78-95-164 (9.78.95.164) (1414)' was not running. If this is the
case, perform the relevant operations to start the TCP/IP listening program,
and try again.
----- amqccita.c : 1209 -------------------------------------------------------
So if you do see these messages then it is to be expected when running in this sort of configuration.