Learn it on Mainframe Path. Do it with MainframeKit.Learn on Mainframe Path ▸
MainframeKit

2543

MQRC_STANDBY_Q_MGRMQ REASON CODE

A connect request reached a standby queue manager instance, which refuses connections. The application has to connect to the active instance instead.

MOST LIKELY

The client or application is pointed at the host of the standby instance instead of the active one.

FIRST CHECK

Check which instance is active by looking at the status of the queue manager on each host.

TRY IT ▸

Site search

What it means

The program reached a queue manager instance that is on standby rather than active. A standby instance is a second copy that waits to take over, and it does not accept connections, so the connect request is refused. The completion code is MQCC_FAILED, so the connection did not happen and no MQI calls can follow.

The fix is to connect to the active instance. The problem is about where the connection is pointed, so check which instance is active before changing the program's logic.

Typical causes

  • The client or application is pointed at the host of the standby instance instead of the active one.
  • A fixed connection to one host was kept after the active instance moved to another server.

How to fix it

  1. Check which instance is active by looking at the status of the queue manager on each host.
  2. Change the program or client so that it connects to the active instance.
  3. Check that the client connection name list or channel table lists both hosts, so the client can find the active one.
  4. If the active instance has just moved, check again before retrying the connection.

Example

Illustrative only; names and values are invented.

MQCONN failed  CompCode=2  Reason=2543 (MQRC_STANDBY_Q_MGR)  QMgr=QM01
Connect target: standby-host-02  (instance not active)