MQ Developer Certification

IBM MQ developer certification validates that you can design applications that put and get messages safely under syncpoint, implement request-reply without losing correlation, choose persistent versus non-persistent messages deliberately, and interpret MQRC reason codes instead of blaming the network team blindly. Administrators certify on channels and CHLAUTH; developers certify on MQMD fields, connection options, and why a poison message keeps cycling. If you write Java JMS or C MQI daily, much of the exam overlaps your job—but exams also probe edge cases: backout thresholds, publish with topic strings, client automatic reconnect, and idempotent consumers. This tutorial outlines typical developer objective domains, contrasts administrator certification, proposes hands-on coding labs, links to Mainframe Master tutorials for each skill, and suggests exam preparation habits. Download IBM's current developer exam guide before scheduling; objective numbers and weights change when IBM refreshes tests.

Developer Skill Domains

Connection and Bindings

MQCONN versus MQCONNX, client connection channel names, CCDT, bindings mode on same machine, and reconnect options. Understand when traffic uses SVRCONN and listener TCP port 1414. Connection broken 2059 after queue manager restart scenarios.

Message Descriptors and Properties

MQMD: MsgId, CorrelId, ReplyToQ, ReplyToQMgr, Persistence, Priority, Expiry. MQPMO and MQGMO options for syncpoint, fail-if-quiescing, and browse. How properties carry business metadata in 9.x JSON contexts at overview.

Syncpoint and Transactions

MQPUT and MQGET under syncpoint, MQCMIT, MQBACK. Unit of work boundaries. Why long transactions hurt operations. XA overview for exam scenario questions coupling database and MQ.

Patterns

• Point-to-point fire-and-forget and acknowledged processing.
• Request-reply with temporary reply queues or named reply queues.
• Publish/subscribe with topic strings and durability implications.
• Poison message and backout queue handling in application design.
• Idempotency when at-least-once delivery occurs.

Reason Codes to Know

Study Plan for Developers

1. Complete fundamentals: what is IBM MQ, queues, queue manager.
2. Code put/get lab in C or Java with persistent flag experiments.
3. Add syncpoint commit and rollback test.
4. Implement request-reply pair programs.
5. Publish/subscribe small topic demo.
6. Practice sample exam questions under time limit.

1
2
3
4
5
/* Conceptual MQI flow — study structure not memorizing every constant */
MQCONN -> MQOPEN -> MQPUT (with MQPMO_SYNCPOINT)
       -> MQCMIT or MQBACK -> MQCLOSE -> MQDISC
/* JMS: ConnectionFactory -> createQueueSession(transacted=true) */
/* compare persistent delivery mode 1 vs 0 */

JMS Versus MQI on Exams

JMS abstracts descriptors into Message objects; exams may ask equivalent concepts—delivery mode persistent maps to MQ persistence. Understand transacted session commit versus rollback. Know that JMS still uses channels and queue managers underneath.

What Developers Skip (But Should Skim)

Channel BATCHSZ tuning depth is admin work, but developers should know transmission queues exist when putting to QREMOTE. Skim clustering so exam scenarios about cluster queues make sense. Read administrator certification page to avoid security anti-patterns in code (hard-coded passwords, unlimited reconnect storms).

Explain Like I'm Five: Developer Certification

Developer certification proves you know how to send and receive letters correctly—write the address, ask for a reply when needed, and don't lose letters when someone says undo.

Practice Exercises

Exercise 1

Write put/get with syncpoint; rollback and prove message absent on queue.

Exercise 2

Implement request-reply using CorrelId matching.

Exercise 3

Map five MQRC codes to fixes without looking at notes.

Frequently Asked Questions

Test Your Knowledge