MainframeKit

2537

MQRC_CHANNEL_NOT_AVAILABLE (X'09E9')MQ REASON CODE

A client could not connect because the server-connection channel is stopped or has hit a connection limit.

MOST LIKELY

The SVRCONN channel is in STOPPED state.

FIRST CHECK

Check the queue manager and client error logs for the matching message.

TRY IT ▸

MainframeKit assistant

What it means

The client reached the queue manager, but the channel would not accept it. Either the channel is stopped, an exit stopped it, or a limit on the number of channel instances was reached. It is also used in the Channel Not Available event.

Typical causes

  • The SVRCONN channel is in STOPPED state.
  • A channel exit ended the channel.
  • The per-client limit (MAXINSTC) or channel-wide limit (MAXINST) was reached.
  • The queue manager's limit on total channels was reached.
  • Programs leak connections and never disconnect.

How to fix it

  1. Check the queue manager and client error logs for the matching message.
  2. Run DISPLAY CHSTATUS(name) and DISPLAY CHANNEL(name) MAXINST MAXINSTC.
  3. Start a stopped channel with START CHANNEL(name).
  4. Find which clients hold the most instances and fix connection leaks before raising limits.

Example

Illustrative only; names and values are invented.

MQCONN failed  CompCode=2  Reason=2537  Channel=APP.SVRCONN  ConnName=10.0.0.10(1414)
DISPLAY CHSTATUS(APP.SVRCONN) CONNAME