All geek questions in one place

Getting error: reason code 258 WebSphere MQ?

I have WebSphere MQ and WebSphere Message Broker installed on Linux, and when I run mqsicreateexecutiongroup , I get an error message:

BIP1046E: Unable to connect to the queue manager (failed to connect to the queue manager "NSPZPAI1" (error reason code MQ 2538)).

When I look for this reason code, I understand that this is an error that is not accessible to the host.
Can someone please tell me how to resolve this error?

When I run the runmqlsr command, I always get stuck. Can someone tell me how to start a listener?

+4
source share
2 answers

Do not start the listener manually or script. If you have a modern queue manager, define a listener like this:

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

The CONTROL(QMGR) attribute CONTROL(QMGR) tells QMgr to start the listener automatically when QMgr starts and kill the listener when QMgr is turned off. This ensures that the listener will always be launched when QMgr appears, even if QMgr is started manually, and not from a regular script load. Since the listener is a child of QMgr, it will always work with QMgr, so you don’t have to worry about lost listeners warning connections after restarting QMgr.

After defining the listener, you can also use the START LISTENER or STOP LISTENER MQSC commands to manually start and stop it regardless of QMgr. In the above example, I manually started listening, not rebooting QMgr. Any of these will work, but the START command is less intrusive.

+7
source

The listener starts with

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

It launches a listener that is waiting for connections. More information about the team here.

+1
source

Source: https://habr.com/ru/post/1440009/

More articles:


All Articles