Procedures are the reusable JCL templates operators trust to start IBM MQ the same way every IPL, every recovery, and every drill. Instead of retyping dozens of DD cards under stress, the site maintains PROC members—subsystem startup, channel initiator, optional listener—that automation STARTs with one command. Misconfigured PROCs cause the queue manager to abend on launch, point STEPLIB at the wrong MQ release after SMP/E, or omit a DD the channel initiator needs for TLS key rings. Beginners should locate their site PROC library, compare it to IBM samples, and understand which PROC is safe to restart during the day versus which requires a change window. This tutorial explains PROC anatomy for MQ, common member names and purposes, customization discipline, integration with operations automation, restart sequencing after failures, and coordination with JCL batch jobs that are not PROCs.
PROC members live in partitioned data sets concatenated in JCLLIB ORDER or referenced by fully qualified DSN. Installation places IBM defaults; systems programming copies to MQ.PROCLIB or similar and updates JCLLIB in IKJEFT01 or automation tables. Version control may export PROC text to Git for review. When two PROC members share similar names, on-call engineers confuse them—naming standards matter.
| Procedure type | Purpose | Lifecycle |
|---|---|---|
| Subsystem start | Bring QM address space online | Start at IPL/recovery |
| Channel initiator | Run channel agents | Long-running |
| Listener | Accept inbound connections | Long-running |
| Utility wrapper | Call CSQUTIL with standard DDs | Batch |
| Recovery | Log replay, special start | Incident-driven |
Sites document dependencies—starting a listener before the queue manager fails predictably. Automation products encode the sequence with timeouts and alerts.
123456Operator actions (conceptual): S PROC=MQ1STRT,SUBSYS=... /* site-specific START syntax */ /* wait for CSQ1 active */ S PROC=MQ1CHIN,SUBSYS=... DISPLAY CHSTATUS(*) WHERE(CHSTATUS NE RUNNING)
After SMP/E apply, compare IBM sample PROCs to site copies with ISPF SUPERCOMPARE or Git diff. New DD statements may be required for features you enabled. Merge carefully—blindly keeping old PROCs misses security fixes; blindly overwriting loses site TLS DD names. Change advisory meetings should include MQ admin and systems programming.
PROCs use symbolic parameters like &QMGR or &SSID passed on START commands to reuse one PROC for test and prod with different parms. Document allowed values. Automation must escape special characters correctly. Wrong parm can start test configuration against production data sets—a severe governance failure.
MQ procedures are labeled switches on the operations panel. Flip START MQ1STRT and the right lights (address spaces) come on in the designed order.
A procedure is a saved set of instructions so operators do not retype everything when they need to wake up IBM MQ.
Map your site startup PROC names to their purpose in a table.
List dependencies that must be healthy before starting the MQ subsystem PROC.
Describe how you would diff PROCs after an SMP/E maintenance window.
1. A PROC is stored in:
2. START procname is issued by:
3. Site customization should:
4. Channel initiator PROCs often run: