7

I have WebSphere MQ and WebSphere Message Broker installed on Linux and when I execute mqsicreateexecutiongroup I get an error saying:

BIP1046E: Unable to connect with the queue manager (Could not connect to queue manager 'NSPZPAI1' (MQ reason code 2538)).

When I search for this reason code I understand that it is a host not available error.
Can somebody please tell me how to resolve this error?

When I run a runmqlsr command I always end up in a hang. Can somebody tell me how to start a listener?

T.Rob
  • 31,522
  • 9
  • 59
  • 103
Tanu
  • 369
  • 5
  • 7
  • 18

2 Answers2

9

Don't start the listener by hand or script. If you have a modern queue manager, define a listener object like so:

DEF LISTENER(LISTENER.1414)  TRPTYPE(TCP) +
    CONTROL(QMGR)            PORT(1414) +
    REPLACE

START LISTENER(LISTENER.1414)

The attribute CONTROL(QMGR) tells the QMgr to start the listener automatically when the QMgr is started and to kill the listener when the QMgr is shut down. This ensures that the listener will always be started when the QMgr comes up, even if the QMgr is started manually instead of from the usual boot script. Because the listener is a child process of the QMgr it will always come down with the QMgr so you don't need to worry about orphaned listeners preventing connections after a QMgr restart.

Once the listener is defined, you can also use START LISTENER or STOP LISTENER MQSC commands to manually start and stop it independently of the QMgr. In the example above, I've manually started the listener rather than reboot the QMgr. Either would work but the START command is less intrusive.

T.Rob
  • 31,522
  • 9
  • 59
  • 103
  • 1
    Right - the first time you define a listener you'll need to start it manually or reboot the QMgr. After that use START/STOP commands as needed to manage the listener independently from the QMgr. I've added that to my response. Thanks! – T.Rob Oct 16 '12 at 13:41
1

Listener is run using 

runmqlsr -t tcp -p <port> -m <queue manager name>.

It starts the listener which waits for connections. More details on the command are here

Shashi
  • 14,980
  • 2
  • 33
  • 52