Administration - IBM MQ V9.1 System Administrator
Administration - what the exam tests
This domain covers keeping IBM MQ V9.1 queue managers and objects operational: creating and starting queue managers, defining and altering MQSC objects, controlling listeners and channels, taking media images, exporting definitions, and reading queue and channel status. Questions tend to present a command or a status output and ask what happens next.
Core rules
- Lifecycle:
crtmqm QM1,strmqm QM1,endmqm -w|-i|-p QM1,dltmqm QM1. A queue manager must be ended before deletion;endmqm -pis preemptive and should be a last resort because it can leave in-doubt work. - MQSC:
runmqsc QM1acceptsDEFINE QLOCAL(APP.REQ) DEFPSIST(YES) MAXDEPTH(50000),ALTER,DELETE,DISPLAY ... ALL. Keywords are case-insensitive; parentheses are required. - Listeners and channels:
DEFINE LISTENER(TCP) TRPTYPE(TCP) PORT(1414) CONTROL(QMGR),START LISTENER(TCP),DEFINE CHANNEL(...) CHLTYPE(SDR),START CHANNEL,PING CHANNEL. - Recovery: linear logging plus
rcdmqimg -m QM1 -t qlocal(or-t qmgr) enables media recovery;dmpmqcfg -m QM1 -aexports object definitions for rebuild. - Status:
DISPLAY QSTATUS(APP.REQ) TYPE(QUEUE) CURDEPTH,DISPLAY CHSTATUS(...),DISPLAY QMSTATUS.
Worked example
Create QM1 with 8 primary and 4 secondary 4 KB-page log files, then an application queue: crtmqm -lp 8 -lx 4 QM1, strmqm QM1, then in MQSC DEFINE QLOCAL(APP.REQ) DEFPSIST(YES) MAXDEPTH(50000); START LISTENER(TCP);. Reasoning: -lp/-lx size the recovery log; DEFPSIST(YES) keeps messages across restart; MAXDEPTH prevents a runaway producer from filling the file system. DISPLAY QSTATUS confirms live depth, whereas DISPLAY QUEUE shows definition attributes only.
Traps
dltmqm fails while the queue manager is running. qm.ini edits need a restart. DISPLAY QUEUE does not show current depth. Deleting a queue with messages discards them unless you drain or browse first. endmqm -i can leave channels in doubt and is not a clean shutdown.