dmpmqcfg

dmpmqcfg is the IBM MQ utility that answers a question every auditor asks: if this server burned down tonight, could you prove exactly how QM_PROD was configured yesterday? Exporting configuration is not optional in regulated industries—it is evidence. While runmqsc DISPLAY shows one object at a time, dmpmqcfg captures a structured dump of the queue manager repository suitable for diff tools, artifact storage, and documented restore procedures on supported releases. Beginners confuse dmpmqcfg with backing up messages; veterans run dmpmqcfg after every change window and store the file next to the change ticket. This tutorial explains what dmpmqcfg includes and excludes, common command options, pairing with crtmqm restore flows at overview level, DevOps automation patterns, security handling of exported secrets, comparison to scripted DISPLAY exports, and troubleshooting when export fails because the queue manager is down or authority is insufficient.

What dmpmqcfg Captures

The export typically includes object definitions the queue manager stores in its configuration repository: QLOCAL, QREMOTE, QALIAS, channels, listeners, topics, subscriptions, AUTHINFO, CHLAUTH records where exportable, and queue manager attributes reflected in configuration files. It may also produce or reference mq.ini and qm.ini fragments depending on options documented for your MQ version. It does not include CURDEPTH message bodies, log file contents, or TLS private keys inside keystores—you backup keystores separately through your secrets vault. Treat dmpmqcfg output as sensitive: channel CONNAME values, LDAP bind DNs, and architecture hints belong in restricted storage.

1
2
3
4
5
6
7
# Export configuration for queue manager QM1 (syntax per IBM MQ 9.x manual)
dmpmqcfg -m QM1 -o /backup/mq/QM1-$(date +%Y%m%d).mqsc
# -m — queue manager name to export
# -o — output file path; use dated names for retention
 
# Verify file size and spot-check contents
head -50 /backup/mq/QM1-$(date +%Y%m%d).mqsc

Common Options and Output Formats

IBM MQ evolves dmpmqcfg flags by release—always read the dmpmqcfg help text on your installation. Typical patterns include selecting output directory, choosing whether to include certain object types, and exporting in a format compatible with recreate workflows. Some sites export to MQSC-like text that operators can review in a diff tool; others ingest JSON or structured output into configuration databases. The learning goal is automation: a cron job or pipeline step that fails the build if production drift differs from the last approved export without a matching change record.

1
2
3
4
dmpmqcfg -h
# Read installed help for your exact flags
# Compare two exports after change window:
diff /backup/mq/QM1-before.mqsc /backup/mq/QM1-after.mqsc | less

Restore and Migration Context

Export supports migration when you build QM1_NEW with crtmqm using configuration derived from a tested export, then apply incremental ALTER for environment-specific CONNAME and ports. Never copy production CONNAME to lab without network isolation. Environment migration tutorial covers promotion discipline. dmpmqcfg proves what production looked like before ALTER; Git proves what you intended after merge. Both belong in CMDB-linked storage.

Operational Schedule

1. Nightly automated dmpmqcfg for all production queue managers.
2. On-demand dmpmqcfg before and after each change window.
3. Retain thirty to ninety days per policy; longer for annual audit.
4. Encrypt artifacts at rest; restrict read access to messaging ops.
5. Quarterly restore test in lab using export plus documented crtmqm steps.

Failures and Troubleshooting

• Queue manager not running—start with strmqm or export from standby documentation copy if policy allows cold file backup only.
• 2035 or permission errors—run as user with administrative authority on the queue manager.
• Disk full on output path—monitor backup filesystem separately from MQ log disk.
• Empty or truncated file—check script exit code; pipeline should fail closed.

Security and Compliance

Exported files may list channel names, partner IP addresses, and authentication object names. PCI and SOX environments classify exports as configuration evidence, not cardholder data, but still protect them from public ticket attachments. Redact when sharing with vendors. Pair export with dspmqaut or AUTHREC documentation so restore includes OAM grants, not only DEFINE objects.

Explainer: Photocopying the Blueprint

Messages are furniture in the rooms. dmpmqcfg is photocopying the architectural blueprint—the list of rooms and doors—not photographing the furniture inside.

Explain Like I'm Five: dmpmqcfg

dmpmqcfg is writing down all the rules about which mailboxes and tunnels exist so you can build them again if the post office building is rebuilt—even if no letters are copied in the notebook.

Practice Exercises

Exercise 1

Export QM lab config; ALTER one queue MAXDEPTH; export again; diff the two files.

Exercise 2

Add dmpmqcfg to a shell script with exit-on-error and dated filenames.

Exercise 3

List five object types you expect in export and verify each appears with DISPLAY after restore test.

Frequently Asked Questions

Test Your Knowledge