I85PREP
⌘ K
IBM MQ V9.1 System Administrator study materials
IBM MQ V9.1 System Administrator study resources

IBM MQ V9.1 System Administrator: Configuration - IBM MQ V9.1 System Administrator

IBM MQ V9.1 System Administrator · Work through your exam, one topic at a time.

All guide sections

Configuration - IBM MQ V9.1 System Administrator

Configuration - what the exam tests

This domain tests static configuration: qm.ini stanzas and attributes, queue and channel definitions, transmission queues, client connection definitions, and logging or multi-instance settings. The exam expects you to know which file or object carries a setting and when a restart is needed.

Core rules

  • qm.ini stanzas: Log (LogType=LINEAR, LogFilePages, LogPrimaryFiles, LogExtentFiles), Channels (MaxChannels, MaxActiveChannels), TCP (Port, ListenerBacklog), QMgr (MaxHandles), SSL (KeyRepository). Most changes are read at queue manager start, so restart after editing.
  • Queue types: QLOCAL stores messages; QREMOTE carries RNAME, RQMNAME, XMITQ; QALIAS points at TARGQ; QMODEL with DEFTYPE(TEMPDYN|PERMDYN) creates dynamic queues on open.
  • Channels: a sender channel needs CONNAME and XMITQ; the receiver channel on the remote queue manager must have the same channel name. A transmission queue is normally named after the destination queue manager. TRIGGER, TRIGTYPE, TRIGDPTH, INITQ(SYSTEM.CHANNEL.INITQ) start the MCA on demand.
  • Clients: CLNTCONN definitions plus MQCHLLIB/MQCHLTAB locate the client channel definition table; SVRCONN is the server side.
  • Logging choice: circular logging is simpler but cannot support media recovery; linear logging plus media images can.

Worked example

On QM1, route to QM2: DEFINE QREMOTE(APP.REQ) RNAME(APP.REQ) RQMNAME(QM2) XMITQ(QM2), DEFINE QLOCAL(QM2) USAGE(XMITQ), DEFINE CHANNEL(QM1.QM2) CHLTYPE(SDR) CONNAME('qm2host(1414)') XMITQ(QM2), START CHANNEL(QM1.QM2). On QM2 define QLOCAL(APP.REQ) and CHANNEL(QM1.QM2) CHLTYPE(RCVR). Reasoning: the remote queue resolves to QM2's queue, the queue manager puts to the XMITQ, and the sender MCA moves messages over the channel; both channel names must match or the receiver rejects the session.

Traps

Defining a remote queue but forgetting the XMITQ leaves messages stuck. A CONNAME typo produces RETRYING, not an immediate definition error. MaxChannels is not the same as MaxActiveChannels. Circular logging cannot be switched to linear by editing qm.ini alone; the queue manager must be recreated or converted per IBM's procedure. Not defining DEADQ on the queue manager loses undeliverable messages.