MainframeKit

2059

MQRC_Q_MGR_NOT_AVAILABLE (X'080B')MQ REASON CODE

The program could not connect because the queue manager it named is not available to it right now.

MOST LIKELY

The queue manager is stopped, starting or ending.

FIRST CHECK

Check that the queue manager is running: dspmq on distributed, or the MSTR address space and console messages on z/OS.

TRY IT ▸

MainframeKit assistant

What it means

The queue manager is known but cannot be reached for a connection. For local programs it is usually not running. For clients, a channel definition problem can also give 2059, as can failing to reach any queue manager in a group.

Typical causes

  • The queue manager is stopped, starting or ending.
  • On z/OS, the batch job runs on an LPAR where that queue manager does not run.
  • On z/OS, a shortage of common storage (ECSA) or the ACELIM limit stops new connections.
  • A client's channel definitions or CCDT point to the wrong place.
  • In a multi-installation setup, the program loads the wrong MQ libraries.

How to fix it

  1. Check that the queue manager is running: dspmq on distributed, or the MSTR address space and console messages on z/OS.
  2. On z/OS, check the job runs on an LPAR where the queue manager is active.
  3. For clients, check the channel definition, channel status and both error logs.
  4. In multi-installation setups, check which MQ installation the program loads.

Example

Illustrative only; names and values are invented.

MQCONN failed  CompCode=2  Reason=2059  QMgrName=QM01
dspmq -m QM01
  QMNAME(QM01)  STATUS(Ended normally)