- Home
- Skills
- APIs & Backend
- IBM MQ Diagnostics (MQ-Sentinel)
Works with the AI Agents you already use
IBM MQ Diagnostics (MQ-Sentinel)
Diagnose IBM MQ channels, DLQs, clusters and HA with cited root causes and IBM doc links. Read-only.
Free
IBM MQ Diagnostics (MQ-Sentinel)
Example session with this skill installed
Channel APP.SVRCONN on DEMO_QM keeps going into RETRYING. Can you check our channels and tell me what's wrong?
- Read your context and instructions
- Compiled the ibm mq diagnostics
I ran diagnose_failed_channels on DEMO_QM with MQ-Sentinel (read-only, demo data).
DEMO_QM: 3 channel problems. MQ 9.4.0.0, Native HA. 4 channels examined.
| Severity | Channel | Finding |
|---|---|---|
| 🔴 CRITICAL | INDOUBT.RCVR | Channel is in doubt |
| 🟠 HIGH | APP.SVRCONN | MQRC 2035 (NOT_AUTHORIZED) |
| 🟠 HIGH | TO.PARTNER | Connection error (reason 2009) |
🟠 APP.SVRCONN: MQRC 2035 (NOT_AUTHORIZED)
Root cause: the connecting principal failed authorization. Common causes: a CHLAUTH BLOCKUSER rule blocked the user, the resolved MCAUSER lacks +connect/+inq on the queue manager, or CONNAUTH credentials failed.
Evidence: status RETRYING, remote QM REMOTE_QM. Confidence: High.
Confirm it (read-only):
DISPLAY CHLAUTH('APP.SVRCONN') MATCH(RUNCHECK) ALL
DISPLAY CHSTATUS('APP.SVRCONN') ALL
DISPLAY QMGR CONNAUTH
DISPLAY AUTHINFO(*) ALL
IBM docs: 2035 (07F3) MQRC_NOT_AUTHORIZED
Possible fixes, depending on what the checks show (for you to review and run in a change window):
- MCAUSER missing permissions:
SET AUTHREC PRINCIPAL('mcauser') OBJTYPE(QMGR) AUTHADD(CONNECT, INQ). Replacemcauserwith the value fromDISPLAY CHSTATUS MCAUSER. - A BLOCKUSER rule matching the wrong user: narrow its
USERLISTto only the principals you mean to block. - CONNAUTH rejecting the credentials: check the
AUTHINFOconfiguration, thenREFRESH SECURITY TYPE(CONNAUTH).
🔴 INDOUBT.RCVR: channel in doubt
Root cause: uncommitted batches can't resolve on their own; manual resolution is needed after checking the remote QM.
Confirm: DISPLAY CHSTATUS('INDOUBT.RCVR') ALL CURLUWID LSTLUWID
⚠️
Only after confirming the batch state on the remote QM: RESOLVE CHANNEL('INDOUBT.RCVR') ACTION(COMMIT), or ACTION(BACKOUT). Choosing wrongly duplicates or loses messages.
🟠 TO.PARTNER: connection error (2009)
Root cause: network or TLS handshake failure to the remote endpoint.
Confirm:
DISPLAY CHSTATUS('TO.PARTNER') ALL
DISPLAY CHANNEL('TO.PARTNER') CONNAME XMITQ SSLCIPH
DISPLAY LSSTATUS(*) ALL
PING CHANNEL(TO.PARTNER)
IBM docs: AMQ9202E: Remote host not available
Next steps
- Run the read-only checks above, starting with APP.SVRCONN's CHLAUTH check.
- Decide on INDOUBT.RCVR with your messaging team before resolving anything.
- Nothing was changed on the queue manager. MQ-Sentinel only reads.
Connects securely to your tools. The creator never sees your data.
About this skill
Ask your agent why a channel is RETRYING, what MQRC 2035 means on your queue manager, why the dead-letter queue is growing, or whether your cluster or Native HA setup is healthy. You get a cited diagnosis: the evidence, the root cause, the DISPLAY commands to confirm it, links to the matching IBM Documentation pages, and possible fixes for you to review.
The skill drives MQ-Sentinel, a free, read-only MCP server for IBM MQ:
- 9 tools: channels, dead-letter queue (headers only, bodies never read), cluster, Native HA, RDQM, multi-instance, z/OS queue-sharing groups, and a full health check with an executive summary
- Read-only by design: only allowlisted DISPLAY commands reach your queue managers; suggested changes come back as text for you to run
- Every IBM documentation link it cites is checked daily
- Try it in demo mode with no IBM MQ, then connect your own queue managers, or a central team server with SSO
Includes ready-to-copy configs for Claude Code, Claude Desktop, Cursor and VS Code, a least-privilege MQ setup guide (setmqaut, CHLAUTH), and a reason-code reference.
Requires the free MQ-Sentinel MCP server: https://pypi.org/project/mq-sentinel/ · Source: https://github.com/pramodreddyboddu/mq-sentinel
Does it change anything on my queue managers? No. Only read-only DISPLAY commands are sent. Suggested fixes come back as text for you to review and run.
Do I need IBM MQ to try it? No. Demo mode uses built-in sample data with one queue manager, DEMO_QM. You only need uv.
Where do my MQ credentials go? In MQ-Sentinel’s own secrets folder. They never go in the skill, the agent config or the chat.
Which agents does it work with? Any agent that supports MCP. Configs are included for Claude Code, Claude Desktop, Cursor and VS Code.
Can my team share one server? Yes. Run MQ-Sentinel centrally with SSO; prod access follows each person’s SSO groups.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 29 days ago
- Free with an Agensi account
Requires
Permissions
The skill itself runs no code and only reads its own reference files. It calls tools on the separately installed MQ-Sentinel MCP server, which connects only to the IBM MQ queue managers listed in its inventory and sends only read-only DISPLAY commands. MQ-Sentinel writes its own audit log and reads its inventory and credentials folders on the user's machine or server; no credentials are stored in the skill.