IBM MQ support, 24/7

IBM MQ Support for Distributed Platforms, z/OS, Multi-Instance Queue Managers and OpenShift

Last reviewed by Tyler Eastridge

AceMQ supports IBM MQ 24/7 on Linux, AIX, Windows, IBM i, z/OS and OpenShift, alongside your IBM contract or on its own. Most calls start with one of three problems: channels stuck in RETRYING behind CHLAUTH or CipherSpec mismatches, a recovery log pinned by one long-running unit of work, or MQRC 2009 errors from an idle-timeout.

24/7 across Americas, EMEA and APAC, with response targets from 15 minutes, by plan, and a written root cause analysis on every P1.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ IBM MQ consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

IBM MQ problems we fix every week (MQRC codes and what they point to)

Retrying channels, broken connections, filling logs and dead letter messages: the reason code or file an engineer reads first for each.

Common IBM MQ production problems and how AceMQ resolves them
Symptom you're seeingWhat we check firstTypical resolution
Channel in RETRYING, messages backing up on the transmission queueAMQERR01.LOG reason code; CHLAUTH rules; CipherSpec mismatch between the two ends; MAXINST or MAXINSTC reached on the receiverCorrect the rule, align the CipherSpec, raise the instance limit where justified
MQRC 2009 (connection broken), intermittentClient heartbeat and keepalive against firewall or load balancer idle timeouts; it tracks traffic troughsAlign HBINT and keepalive below the intermediary's idle timeout
MQRC 2102 or 2192 and the log filesystem fillingThe oldest active log extent and the connection holding the oldest unit of workCommit in bounded batches in the application, resize logs from measured transaction time
Queue manager will not start after a storage eventqm.ini log path, permissions, mounts; whether linear log extents needed for media recovery are intactRestore paths and permissions, recover media in the right order
Messages on the dead letter queueThe DLH reason on the message header: 2053 queue full, 2085 unknown object name, 2035 not authorized point to three different fixesFix the cause the header names, then reprocess
Multi-instance queue manager failed over, clients did not followWhether the standby acquired the lock on the shared filesystem; whether the CCDT or connection name list includes both instancesDistribute a corrected CCDT; test failover from the client side
Clustered queue depth rising on one instanceCLWLPRTY, CLWLRANK, and whether the quiet instance's cluster-receiver channel is running; a partial repository that lost its full repository linkRestore the repository link, correct workload balancing attributes
TLS handshake failures after a certificate rotationKey repository contents, labels and trust chain; CipherSpec supported by both endsReissue with the full chain, align specs, add expiry alerting

Each P1 ends in a written root cause that cites the reason code, channel or log extent involved and what we changed.

A payments channel stuck in RETRYING? Request a quote and an MQ engineer answers within the hour.

Contact Us

Deployment coverage

Which IBM MQ deployments does AceMQ support, and who covers what?

DeploymentWhat AceMQ coversWhat the vendor coversExcluded
IBM MQ on Linux, AIX, Windows24/7 incident response, written RCA on P1s with AMQERR extracts, TLS and CHLAUTH, log and buffer tuning, cluster design, upgradesIBM supplies fix packs and fixes for entitled versions, and takes product defect cases (IBM)A patched IBM binary
IBM MQ for z/OSPage sets and buffer pools, queue-sharing groups, Coupling Facility structure sizing, shared message data setsIBM supports the product and the platformz/OS system programming outside MQ
IBM MQ on IBM iQueue manager operations and channel behaviour on IBM iIBM supports the platformOperating system faults
Multi-instance queue managers and RDQM HAFailover validation, client CCDT distribution, lock behaviour on shared filesystems, replication linksIBM supports the productStorage array faults
Red Hat OpenShift and the MQ Operator, Kubernetes (EKS, AKS, GKE)Queue manager pods, persistent storage and log behaviour, operator upgrades, client reconnectRed Hat and IBM support the operator and platform per their termsCluster control-plane faults
IBM MQ on Cloud, and MQ on AWS, Azure and Google Cloud virtual machinesThe configuration and workload layer you controlThe provider operates its managed serviceService-level faults
WebSphere MQ legacy versionsThe same operational support, plus migration planningNone stated on IBM's current pagesFeatures absent from the version

Support options

Who provides enterprise support for IBM MQ? IBM and independent support compared

IBM provides support for IBM MQ through Software Subscription and Support. Independent providers such as AceMQ support IBM MQ operations and troubleshooting on any version, alongside the IBM entitlement or without it. A subscription gives you the vendor's fixes; an independent contract gives you an engineer who joins the bridge.

IBM support
AceMQ independent support
What it coversIBM MQ entitled versions: fix packs, new versions, product defect cases
What it coversIBM MQ, MQ Advanced, the MQ Appliance and WebSphere MQ, on distributed platforms and z/OS
Release streamsLong Term Support and Continuous Delivery; the 9.4 documentation lists 9.4.0 LTS and CD releases 9.4.1 to 9.4.5 (ibm.com/docs, read 17 Nov 2026)
Release streamsWe support the stream each queue manager is on
Product defectsIBM supplies the fix
Product defectsWe reproduce, work a PMR with IBM on your behalf and apply the fix
Configuration and operationsWithin IBM's scope as the plan defines
Configuration and operationsCore of our work: channels, logs, certificates, cluster behaviour, filesystems, clients
PriceIBM contract
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour

Short note: most of our IBM MQ customers keep the IBM entitlement and add AceMQ for the operational side. If the incident is a channel stopped by a firewall change or a buffer pool sized for last year's workload, a defect ticket does not help.

What's Included

Everything in your IBM MQ support contract

Queue managers, channels, clusters, logs and certificates are covered on distributed platforms and z/OS under a single agreement.

  • 01

    Emergency Incident Response

    Queue manager down, channels not starting, or messages stalled on a transmission queue. With response targets from 15 minutes, by plan, a senior IBM MQ engineer joins a live bridge with access to diagnose — not a ticket acknowledgement.

  • 02

    Root Cause Analysis

    Every P1 closes with a written RCA including the relevant AMQERR log extracts, the reason codes involved, the fix applied, and the configuration change that prevents recurrence.

  • 03

    TLS, CHLAUTH & Certificate Lifecycle

    Key repository management, CipherSpec selection as IBM deprecates older suites, CHLAUTH rule design, and certificate renewals planned before expiry rather than diagnosed at 2am after one.

  • 04

    Performance & Log Tuning

    Buffer pool and page set sizing, circular versus linear logging decisions, log extent sizing against transaction duration, and channel batch tuning against your actual message profile.

  • 05

    Cluster & High Availability Design

    MQ cluster repository topology, workload balancing behavior, multi-instance and RDQM failover validation, and disaster recovery runbooks that get tested rather than filed.

  • 06

    Version Upgrades & Migration

    Upgrades across LTS and CD release streams, WebSphere MQ legacy version migration, moves to MQ on containers or IBM MQ on Cloud, and migration off MQ to RabbitMQ or Kafka where that is the right call.

Why AceMQ

Why MQ teams keep AceMQ next to their IBM entitlement

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your queue manager names, your cluster layout, and which applications sit behind which channels — so a P1 call starts with diagnosis, not you reading out your topology.

  • No Tier-1 Triage Layer

    You reach a senior IBM MQ engineer directly by phone, email, or Slack. Nobody collects a problem description to pass along, and there is no queue between you and someone who can read an AMQERR log and a FDC file.

  • Distributed and z/OS, Both Deeply

    Most vendors staff one or the other. We support distributed platforms and MQ for z/OS, including shared queues on the Coupling Facility and the queue-sharing group behavior that has no equivalent on distributed.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am incident is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to wake up.

  • Proactive, Not Just Reactive

    Quarterly health checks on your queue managers plus certificate expiry tracking. A large share of the MQ outages we see are certificates nobody was watching, and that is a preventable class of incident.

  • Full-Stack, Not Just the Queue Manager

    MQ problems are frequently not MQ problems. We diagnose across the OS, filesystem and storage latency, network policy, load balancer idle timeouts, and the JMS or .NET client — which is where a surprising number of MQRC 2009s actually originate.

IBM MQ platforms we support

Queue managers on Linux, AIX, Windows and IBM i, z/OS with page sets and queue-sharing groups, multi-instance pairs and clustered topologies.

  • IBM MQ on Linux (RHEL, SUSE, Ubuntu)
  • IBM MQ on AIX
  • IBM MQ on Windows Server
  • IBM MQ for z/OS
  • IBM MQ on IBM i
  • Red Hat OpenShift & MQ Operator
  • Kubernetes (EKS, AKS, GKE)
  • IBM MQ on Cloud (managed)
  • AWS, Azure & Google Cloud VMs
  • Multi-instance & RDQM HA
  • Bare metal & on-premise
  • Air-gapped / no outbound access

Version coverage

IBM MQ versions we support

IBM MQ versions we support
IBM MQ versionRelease streamWhat AceMQ does on it
9.4LTS (9.4.0) and CD (9.4.1 to 9.4.5 listed in IBM's 9.4 documentation index)24/7 support; the target for upgrades
9.3, 9.2, 9.1, 9.0LTS and CD levels24/7 support and upgrade planning to the current LTS
8.0IBM MQ 8.0 (the rename from WebSphere MQ)24/7 support and upgrade planning
WebSphere MQ 7.x and MQSeries estatesLegacy24/7 support and migration planning

Source: IBM MQ 9.4 documentation index, ibm.com/docs/en/ibm-mq/9.4, read 17 November 2026. IBM MQ, WebSphere MQ and MQSeries are one product family; queue managers, channels and the programming interfaces carried through each rename.

In practice

Reading an MQ incident: the three files we ask for

On the first call we ask for three artefacts because they separate causes in minutes:

AMQERR01.LOG for the failing channel or queue manager. The reason code and timestamp separate a CHLAUTH block from a CipherSpec mismatch from a connection limit.

DISPLAY CONN output with the unit-of-work detail, when a log is filling. The oldest uncommitted unit of work almost always belongs to one application connection.

The .FDC file, when a queue manager process failed. It names the probe and the call stack IBM support will ask for anyway.

Consulting

IBM MQ consulting and professional services

IBM MQ consulting and professional services
DeliverableWhat you receive
Queue manager health checkLog, buffer pool and page set sizing review, channel configuration, certificate expiry list, cluster repository state, backup and recovery evidence
TLS and CHLAUTH reviewCipherSpec inventory, CHLAUTH rule set review, key repository clean-up, a renewal calendar
HA and DR designMulti-instance or RDQM failover validation, CCDT distribution, DR runbooks that are tested
Upgrade planLTS and CD stream choice, rehearsal, client compatibility, rollback
Cost and platform assessmentInventory of the MQ estate, licensing and support cost, a comparable model for RabbitMQ or Kafka, a business case
Migration planningPhased moves with parallel running and a rollback, where migration fits the estate

Escalation Path

Your first hour of an IBM MQ outage

You reach someone who reads AMQERR01.LOG daily, so the opening question is a reason code, not a scoping form.

  1. From 15 min (by plan)first responseEmergencyProduction down: persistent puts failing on a live queue manager, a queue manager that will not start after a storage event, or a core channel stopped
  2. 1 hourfirst responseCriticalSevere impact: log filesystem filling with MQRC 2102 or 2192, multi-instance failover that clients do not follow, TLS failures after rotation
  3. 4 hoursfirst responseHighChannels cycling in RETRYING, intermittent MQRC 2009, cluster workload skewed to one instance, dead letter queue growth
  4. Next Dayfirst responseStandardQuestions on CHLAUTH rules, CCDT design, buffer pools, page sets, release streams and client compatibility

A channel down on a payments flow and a question about buffer pool sizing do not share a clock; your plan sets each.

Want a named MQ engineer who knows your queue managers? Ask for a quote or write to us.

Contact Us

Pricing

What does AceMQ IBM MQ support cost?

IBM MQ support from AceMQ typically costs $24,000 to $72,000 a year. Pricing follows how many queue managers you run, on which platforms (distributed or z/OS), your clustering and HA design, and the response plan.

All prices are in US dollars (USD). Response targets start at 15 minutes by plan, around the clock, and quote requests get an answer within 1 hour. A contract that also covers Kafka, ActiveMQ or RabbitMQ earns a multi-technology discount.

Support In Practice

IBM MQ problems we have run to ground

IBM MQ support, migration and assessment work from AceMQ. Each card links to the full write-up: the queue manager estate, what AceMQ diagnosed or changed, and the result, so you can see how a similar problem was handled.

  • Consulting

    IBM MQ Cost Reduction and Modernization for Financial Services

    Financial Services Organizations

    AceMQ helps financial services organizations replace costly IBM MQ deployments with RabbitMQ, providing the commercial support and SLA guarantees that regulated industries require while dramatically reducing messaging infrastructure costs.

    IBM MQRabbitMQ
  • Consulting

    IBM MQ to RabbitMQ Migration for Insurance Carrier

    US Insurance Carrier

    AceMQ led the phased migration of a US insurance carrier's IBM MQ infrastructure to RabbitMQ, including legacy code refactoring and HIPAA-compliant data handling across Windows and mainframe queue environments.

    IBM MQRabbitMQKubernetes
All use cases

Support options

Four tiers of IBM MQ support.

AceMQ offers IBM MQ support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for queue managers your team runs, proactive monitoring that catches log, certificate and channel problems first, managed IBM MQ on your own infrastructure, and fully managed IBM MQ on AceMQ infrastructure. Any IBM MQ version is covered in all four, on distributed platforms and z/OS.

  • Tier 1

    IBM MQ 24/7 Support & Incident Management

    Your MQ admins run it, we take hard calls

    Best for: Messaging teams that operate queue managers themselves and want a senior engineer for channel, log and recovery problems.

  • Tier 2

    IBM MQ 24/7 Support with Proactive Monitoring

    Planned checks on logs, channels and certificates

    Best for: Estates where an expiring certificate or a pinned log extent should be found in review, not during a payment run.

  • Tier 3

    Managed IBM MQ on Your Infrastructure

    We operate your queue managers on your platforms

    Best for: Regulated shops that keep MQ on their own distributed or z/OS systems but want daily operation handled by specialists.

  • Tier 4

    Fully Managed IBM MQ on AceMQ Infrastructure

    We run your queue managers as a service

    Best for: Organizations that want reliable queuing without building a dedicated MQ operations team of their own.

FAQ

IBM MQ support questions

Still have questions about IBM MQ? Email an Expert

Who provides enterprise support for IBM MQ?

IBM supports IBM MQ through its subscription entitlement. AceMQ adds independent operations help on any version: channel faults, log and recovery problems, clustering, TLS and upgrades, available 24/7.

What does 24/7 IBM MQ support cover with AceMQ?

A senior engineer on a live bridge at any hour for P1s such as persistent puts failing or a payments channel down, a written root cause after every P1, and help with tuning, recovery and upgrades.

Can you support IBM MQ alongside our IBM contract?

Yes, and most customers keep both. IBM handles product defects and fixes. We handle why a channel stopped after a firewall change or how buffer pools should be sized, and we drive a PMR with IBM when a defect is involved.

Do you support IBM MQ for z/OS as well as distributed platforms?

Yes. z/OS uses page sets, buffer pools, queue-sharing groups on the Coupling Facility and shared message data sets, which differ from distributed queue files. We support Linux, AIX, Windows, IBM i and z/OS.

What does MQRC 2009 mean and how do you fix it?

It means the connection was broken. The most common cause is an intermediary such as a firewall or load balancer dropping idle sockets, and it looks intermittent because it follows traffic troughs. We align client heartbeat and keepalive with the intermediary's idle timeout.

Why is my channel stuck in RETRYING?

Check the AMQERR01.LOG reason code first: it separates CHLAUTH blocking the inbound connection, a CipherSpec mismatch between the ends and a receiver that reached its instance limit. Guessing wastes time; the code does not.

Why is my queue manager log filling?

Usually one long-running uncommitted unit of work pins the oldest log extent while other applications keep writing. More disk only delays it. We identify the connection, fix the commit pattern and size the log from measured transaction duration.

Is IBM MQ the same as WebSphere MQ and MQSeries?

Yes. MQSeries became WebSphere MQ, and WebSphere MQ was renamed IBM MQ at version 8.0. Queue managers, channels and programming interfaces carried through each rename, and we support all of them.

Can you help us upgrade IBM MQ?

Yes. We choose between the LTS and CD streams with you, check client compatibility, rehearse on a copy and keep a rollback. The first step is an inventory of queue manager versions and the release stream each is on.

What does an IBM MQ health check include?

Log, buffer pool and page set sizing, channel and CHLAUTH configuration, certificate expiry, cluster repository state, multi-instance failover test, backup and recovery evidence, and a ranked plan. Quotes are answered within 1 hour.

Who offers IBM MQ consulting and professional services?

IBM and its partners offer MQ consulting, and independent firms such as AceMQ consult on MQ without tying advice to a licence. AceMQ's engineers cover both distributed platforms and z/OS, and they are the same people who work the 24/7 rota. See IBM MQ consulting and the IBM MQ modernization guide.

Do you support end-of-life IBM MQ and WebSphere MQ versions?

Yes. We support versions past their IBM end-of-support date, including WebSphere MQ 7.x estates, with workarounds and mitigations where official fixes are no longer available. Regulated environments frequently cannot upgrade on the vendor's timeline. We will also give you an honest read on which specific risks that leaves open, so the decision to stay is a deliberate one.

Does AceMQ replace our IBM support entitlement?

No. IBM stays responsible for product defects and fixes, and most customers keep that entitlement. We take the operational problems and open a PMR with IBM when a defect is involved. You can also start with one scoped job, such as a health check or an upgrade plan.

What determines the price of IBM MQ support?

Contracts range from $24,000 to $72,000 a year (USD). We price by queue manager count, platform mix including z/OS, MQ version and release stream, clustering and multi-instance setups, and the response plan. Share your layout and we send a quote within 1 hour.

Let's talk

Find the Certificate Nobody Is Watching Before It Expires

Send us your queue manager versions, platforms and the channels that carry your critical traffic. We reply to quote requests within 1 hour.

A senior IBM MQ engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email an IBM MQ Architect