IBM MQ Explorer is the graphical face of queue manager administration for administrators who think in trees and property sheets rather than semicolons. Install it on a Windows or Linux workstation, add a connection to QM1 on localhost or a remote data center, expand Queues, and within minutes you see depth, channels in RETRY, and listeners that failed to start—without memorizing DISPLAY syntax. Under the hood Explorer sends PCF commands exactly like custom Java monitors; the beginner sees dialogs for DEFINE QLOCAL and wizards for channel pairs. Explorer does not replace disciplined MQSC scripting for production promotion, but it accelerates learning, incident response, and proof-of-concept labs. This tutorial covers installation and connections, navigating the object tree, common tasks (create queue, start channel, browse messages), TLS setup overview, differences from runmqsc and REST, performance on large estates, security cautions, and habits that prevent Explorer-only drift from documented infrastructure.
MQ Explorer ships with IBM MQ client installations or as a separate download per IBM packaging for your release. Install a version compatible with your queue managers—newer Explorer generally administers older queue managers within support policy, not the reverse. Launch Explorer, open New Connection, choose remote or local queue manager, enter name QM1, and for remote enter host, port, and server-connection channel name your site provides (for example SYSTEM.ADMIN.SVRCONN or a dedicated ADMIN.SVRCONN). Test connection before saving. Local bindings-mode connections on the same machine as the queue manager may use direct bindings where supported. Failed connections show MQ reason codes—compare to channel, listener, and CONNAUTH issues in other tutorials.
| Explorer action | Rough MQSC equivalent | Note |
|---|---|---|
| New → Local queue | DEFINE QLOCAL(...) | Dialogs set common attributes |
| Channel → Start | START CHANNEL(...) | Shows status colors in tree |
| Queue → Browse | No direct MQSC; uses MQI browse | Read-only inspection of messages |
| Export definitions | SAVEOBJECT / scripted DISPLAY | Useful for bootstrapping Git scripts |
The left tree lists queue managers, then categories: Queues, Channels, Listeners, Topics, Subscriptions, and more depending on version. Right-click context menus offer New, Alter, Delete, Refresh. Properties panels show attributes with descriptions valuable for beginners learning MAXDEPTH versus MAXMSGL. Search boxes filter by name prefix on large systems—use PAYMENT* instead of loading all queues. Channel status views show BINDING, RUNNING, RETRY with timestamps aiding correlation to network incidents.
Wizards guide channel pairs (sender/receiver) and listeners with common defaults. Experts still verify generated definitions match standards—wizards may set MCAUSER or SSL parameters your security team rejects. After creating objects in Explorer, run setmqaut on distributed systems before telling applications to connect. Document Explorer-made changes in change management; ad hoc prod edits without tickets are audit findings. Prefer exporting MQSC from Explorer when available and committing to Git for traceability.
123456Typical Explorer workflow after install: 1. Connect to QM_TEST 2. Create QLOCAL DEMO.IN (wizard) 3. Put test message (right-click queue) 4. Browse message to confirm 5. Export or hand-write MQSC for Git promotion to QM_PROD
Put test messages with arbitrary text or hex for format debugging. Browse shows messages without removing them (non-destructive browse). Do not browse production PCI queues from unsecured laptops. Test messages may need to match expected format (XML, JSON, fixed COBOL copybook) for application consumers to process them—random text is only for connectivity proof. Clearing queues is destructive—Explorer clear options require the same caution as CLEAR QLOCAL in MQSC.
When queue managers require TLS on admin channels, configure Explorer keystore with trust in partner CA and personal cert if mutual TLS is required. Cipher mismatches show as connection failures similar to application clients. Align with digital certificates and key repositories tutorials. Some sites forbid remote Explorer entirely—jump hosts or VPN plus bastion runmqsc only; know your policy before installing on laptops that leave the office.
MQ Explorer is the control panel with pictures for the queue manager—same machinery as runmqsc, but buttons instead of typed commands.
IBM MQ on Cloud and Cloud Pak for Integration offer web consoles with overlapping features. On-prem estates often still use classic Explorer. REST admin suits curl and Kubernetes operators. Pick one source of truth for changes—mixing undocumented Explorer clicks and REST patches causes drift. Training new hires: teach MQSC fundamentals even if they will mostly click Explorer, so incidents are fixable without GUI access.
Explorer stores connection definitions on the administrator laptop—protect the workstation disk encryption and screen lock. Shared admin passwords in saved connections are bad practice; use personal IDs with MFA on VPN. Explorer can delete production channels—restrict OS groups allowed to run Explorer against prod. Log changes via change tickets even when GUI makes it “easy.”
MQ Explorer is a picture menu to see and fix the message mailboxes on the computer instead of typing long commands.
Connect Explorer to a lab QM; create a queue and put one message; capture screenshot for runbook.
Find one channel in RETRY in Explorer; write equivalent DISPLAY CHSTATUS MQSC.
List three changes you would not make in Explorer on production without a ticket.
1. MQ Explorer sends:
2. Repeatable prod deploys prefer:
3. Remote Explorer needs:
4. Explorer test put should use: