CODEWITHSUNDEEP
javaibm-mqesb
Junaid Ahmed
Junaid Ahmed

Reputation: 31

How to connect Remote Q manager(on docker) from windows?

I have an environment of MQ on docker container. I have created Queue manager QM_TEST with the help of following link : https://www-01.ibm.com/support/docview.wss?uid=swg21623113

I can not connect the queue manager from MQ explorer from windows. Following error of channel is coming when connecting Q manager.

Could not establish a connection to the queue manager. Channel name not recognized (AMQ4871) Severity: 10 (Warning) Explanation: The attempt to connect to the queue manager failed. The queue manager did not recognize the channel name. Snap1 Snap2 Snap3 Snap4 Snap5

AMQ5052I: The queue manager task 'QPUBSUB-CTRLR' has started.

EXPLANATION:
The publish/subscribe utility task manager has started the QPUBSUB-CTRLR task.
This task has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62260.30) User(mqm) Program(amqzmuc0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.722Z)
                    ArithInsert2(1)
                    CommentInsert1(TOPIC-TREE)

AMQ5051I: The queue manager task 'TOPIC-TREE' has started.

EXPLANATION:
The critical utility task manager has started the TOPIC-TREE task. This task
has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62260.34) User(mqm) Program(amqzmuc0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.722Z)
                    ArithInsert2(1)
                    CommentInsert1(MULTICAST)

AMQ5051I: The queue manager task 'MULTICAST' has started.

EXPLANATION:
The critical utility task manager has started the MULTICAST task. This task has
now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62260.31) User(mqm) Program(amqzmuc0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.722Z)
                    ArithInsert2(1)
                    CommentInsert1(RESOURCE_MONITOR)

AMQ5051I: The queue manager task 'RESOURCE_MONITOR' has started.

EXPLANATION:
The critical utility task manager has started the RESOURCE_MONITOR task. This
task has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62260.33) User(mqm) Program(amqzmuc0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.723Z)
                    ArithInsert2(1)
                    CommentInsert1(PRESERVED-Q)

AMQ5051I: The queue manager task 'PRESERVED-Q' has started.

EXPLANATION:
The critical utility task manager has started the PRESERVED-Q task. This task
has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62299.5) User(mqm) Program(amqzmuf0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.723Z)
                    ArithInsert2(1)
                    CommentInsert1(QPUBSUB-QUEUE-NLCACHE)

AMQ5052I: The queue manager task 'QPUBSUB-QUEUE-NLCACHE' has started.

EXPLANATION:
The publish/subscribe utility task manager has started the
QPUBSUB-QUEUE-NLCACHE task. This task has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62299.7) User(mqm) Program(amqzmuf0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.724Z)
                    ArithInsert2(1)
                    CommentInsert1(PUBSUB-DAEMON)

AMQ5052I: The queue manager task 'PUBSUB-DAEMON' has started.

EXPLANATION:
The publish/subscribe utility task manager has started the PUBSUB-DAEMON task.
This task has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62299.7) User(mqm) Program(amqzmuf0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.724Z)
                    CommentInsert1(IBM MQ Distributed Pub/Sub Controller)

AMQ5975I: 'IBM MQ Distributed Pub/Sub Controller' has started.

EXPLANATION:
'IBM MQ Distributed Pub/Sub Controller' has started.
ACTION:
None.
----- cmqxzmup.c : 3951 -------------------------------------------------------
06/14/19 05:21:34 - Process(62260.32) User(mqm) Program(amqzmuc0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.726Z)
                    ArithInsert2(1)
                    CommentInsert1(Q-DELETION)

AMQ5051I: The queue manager task 'Q-DELETION' has started.

EXPLANATION:
The critical utility task manager has started the Q-DELETION task. This task
has now started 1 times.
ACTION:
None.
----- amqzmut0.c : 1629 -------------------------------------------------------
06/14/19 05:21:34 - Process(62299.8) User(mqm) Program(amqzmuf0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.731Z)
                    CommentInsert1(IBM MQ Distributed Pub/Sub Fan Out Task)

AMQ5975I: 'IBM MQ Distributed Pub/Sub Fan Out Task' has started.

EXPLANATION:
'IBM MQ Distributed Pub/Sub Fan Out Task' has started.
ACTION:
None.
----- cmqxzmup.c : 383 --------------------------------------------------------
06/14/19 05:21:34 - Process(62299.9) User(mqm) Program(amqzmuf0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.733Z)
                    CommentInsert1(IBM MQ Distributed Pub/Sub Command Task)

AMQ5975I: 'IBM MQ Distributed Pub/Sub Command Task' has started.

EXPLANATION:
'IBM MQ Distributed Pub/Sub Command Task' has started.
ACTION:
None.
----- cmqxzmup.c : 383 --------------------------------------------------------
06/14/19 05:21:34 - Process(62299.10) User(mqm) Program(amqzmuf0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.735Z)
                    CommentInsert1(IBM MQ Distributed Pub/Sub Publish Task)

AMQ5975I: 'IBM MQ Distributed Pub/Sub Publish Task' has started.

EXPLANATION:
'IBM MQ Distributed Pub/Sub Publish Task' has started.
ACTION:
None.
----- cmqxzmup.c : 383 --------------------------------------------------------
06/14/19 05:21:34 - Process(62321.1) User(mqm) Program(amqzmgr0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.746Z)
                    ArithInsert1(62332)
                    CommentInsert1(SYSTEM.CHANNEL.INITQ)

AMQ5022I: The channel initiator has started. ProcessId(62332).

EXPLANATION:
The channel initiator process has started.
ACTION:
None.
----- amqzmgr0.c : 2934 -------------------------------------------------------
06/14/19 05:21:34 - Process(62321.1) User(mqm) Program(amqzmgr0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.749Z)
                    ArithInsert1(62335)
                    CommentInsert1(SYSTEM.CMDSERVER.1)

AMQ5024I: The command server has started. ProcessId(62335).

EXPLANATION:
The command server process has started.
ACTION:
None.
----- amqzmgr0.c : 2943 -------------------------------------------------------
06/14/19 05:21:34 - Process(62332.1) User(mqm) Program(runmqchi)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.798Z)
                    CommentInsert1(SYSTEM.CHANNEL.INITQ)

AMQ8024I: IBM MQ channel initiator started.

EXPLANATION:
The channel initiator for queue SYSTEM.CHANNEL.INITQ has been started.
ACTION:
None.
----- amqrimna.c : 866 --------------------------------------------------------
06/14/19 05:21:34 - Process(62324.1) User(mqm) Program(amqfqpub)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:21:34.800Z)
                    CommentInsert1(QM_TEST)

AMQ5806I: Queued Publish/Subscribe Daemon started for queue manager QM_TEST.

EXPLANATION:
Queued Publish/Subscribe Daemon started for queue manager QM_TEST.
ACTION:
None.
----- cmqxfcxc.c : 1397 -------------------------------------------------------
06/14/19 05:22:16 - Process(62321.1) User(mqm) Program(amqzmgr0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:22:16.457Z)
                    ArithInsert1(62392)
                    CommentInsert1(TCP.LISTENER)

AMQ5026I: The listener 'TCP.LISTENER' has started. ProcessId(62392).

EXPLANATION:
The listener process has started.
ACTION:
None.
----- amqzmgr0.c : 2951 -------------------------------------------------------
06/14/19 05:22:25 - Process(62392.1) User(mqm) Program(runmqlsr)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:22:25.488Z)
                    ArithInsert1(1414) ArithInsert2(98)
                    CommentInsert1(bind)
                    CommentInsert2(TCP/IP)
                    CommentInsert3(:)

AMQ9218E: The TCP/IP listener program could not bind to port number 1414.

EXPLANATION:
An attempt to bind the TCP/IP socket to the listener port was unsuccessful.
ACTION:
The failure could be due to another program, including other MQ listeners,
using the same port number. The return code from the 'bind' call for port :1414
was 98. Record these values and tell the systems administrator.
----- amqclita.c : 748 --------------------------------------------------------
06/14/19 05:22:25 - Process(62321.1) User(mqm) Program(amqzmgr0)
                    Host(ibmmqdkrdev) Installation(Installation1)
                    VRMF(9.1.1.0) QMgr(QM_TEST)
                    Time(2019-06-14T05:22:25.493Z)
                    ArithInsert1(62392)
                    CommentInsert1(TCP.LISTENER)

AMQ5027I: The listener 'TCP.LISTENER' has ended. ProcessId(62392).

EXPLANATION:
The listener process has ended.
ACTION:
None.

Could not establish a connection to the queue manager. Channel name not recognized (AMQ4871) Severity: 10 (Warning) Explanation: The attempt to connect to the queue manager failed. The queue manager did not recognize the channel name.

Upvotes: 1

Views: 895

Answers (1)

Morag Hughson
Morag Hughson

Reputation: 7649

The error message is telling you that the channel has not been defined on the queue manager. If you believe that the channel is already defined on the queue manager, another reason could be that your client (MQ Explorer in this case) is not actually connecting to the queue manager you think it is connecting to. In which case, the channel is not defined because it is the wrong queue manager.

The default channel that MQ Explorer uses is not defined by default on a queue manager in order to ensure that it is not open to abuse by an unauthorized user.

If you look in the queue manager AMQERR01.LOG you will see a similar error message which also lists the channel name that does not exist.

To define the channel, use the runmqsc tool on the queue manager machine, and type in the following MQSC command.

DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN) DESCR('Channel for MQ Explorer connectivity')

Upvotes: 2

Related Questions