IBM MQ V9.1 System Administrator study plan

IBM MQ V9.1 System Administrator · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Administration & Configuration

Install IBM MQ V9.1 on a Linux lab host and record every component (queue manager, listener, channels, sample programs) that gets created by default
Create three queue managers with crtmqm using different log configurations, then start and stop each with strmqm and endmqm and note the exact behavior of each shutdown mode
Map the relationship between queue managers, queues, channels, listeners, and namelists by drawing a diagram of your lab after creating one of each object
Run the MQ Explorer and the runmqsc command interface side by side and complete the same five object definitions in both to compare the output

A one-page lab inventory listing every object you created, the command used to create it, and the command that displays it

Week 2

Define local, remote, alias, and model queues and place a test message on each type to observe how each behaves
Configure a sender/receiver channel pair between two queue managers on the same host and confirm message flow with a trace-route message
Configure a server-connection channel and connect to it with a sample client program, recording the connection status in DISPLAY CHSTATUS
Set up a trigger monitor on an initiation queue and demonstrate a triggered application starting when a message arrives

A working two-queue-manager message path with a written explanation of every channel and queue definition along that path

Week 3

Write a runmqsc script that builds an entire queue manager's object set from scratch and re-run it against a fresh queue manager to prove it is repeatable
Configure a transmission queue, dead-letter queue, and default queue attributes, then verify each with DISPLAY commands
Back up a queue manager's configuration by exporting object definitions and restore them into a second queue manager
Adjust queue manager and channel tuning parameters and explain in writing what each change affects under load

A version-controlled runmqsc build script plus a restore log showing a successful rebuild of the same configuration on a second queue manager

Week 4

Locate and interpret queue manager error logs, FFST files, and trace output for a deliberately induced failure
Diagnose and resolve a channel that will not start by reading channel status and error messages rather than guessing
Resolve a full dead-letter queue scenario and explain the difference between a message sitting on a transmission queue versus one on a dead-letter queue
Practice starting and stopping queue managers in each mode and document which mode is appropriate for a hung queue manager

A troubleshooting log of at least five induced faults, each with the symptom, the diagnostic command used, the root cause, and the fix

Week 5

Diagnose a message build-up on a transmission queue by checking channel status, listener state, and remote queue manager availability in sequence
Use MQ trace facilities to capture a problem and identify where in the trace the failure appears
Recover a queue manager from a damaged log or inconsistent state using backup and recovery procedures
Collect and interpret queue statistics and accounting data to explain a performance problem

A written incident report for one simulated outage covering detection, diagnosis, recovery, and prevention

Week 6

Configure channel authentication records to block and to allow specific remote partners, then verify each rule with a connection attempt
Set up TLS on a channel pair using a self-signed keystore and confirm the channel starts with the correct cipher specification
Configure object authority manager permissions so that one user can inquire but not alter queue definitions, and prove it
Create a channel exit or security exit scenario and explain where authentication happens in the message path

A security configuration sheet listing every channel authentication rule, TLS setting, and authority record, with a test result for each

Week 7

Diagnose a channel that fails to start due to a certificate or cipher mismatch and document the exact error messages
Resolve an authorization failure by reading the authority event messages and correcting the relevant permissions
Review authority events and channel authentication events to detect an unauthorized connection attempt
Harden a queue manager by disabling default channels and administrative access you do not need

A before-and-after hardening report showing the security settings changed and the evidence that each change took effect

Week 8

Rebuild your full lab from scratch using only your own scripts and notes, timing how long it takes
Complete a timed practice set across all four domains and review every missed item against your notes
Revisit your weakest two domains and close the specific gaps identified in the practice review
Write a one-page command cheat sheet covering the administrative, configuration, diagnostic, and security tasks you are most likely to be asked about

A timed practice score record with a written gap analysis and a finalized one-page cheat sheet

Week 2: Two queue managers exchange messages over a configured channel, and you can explain every object in the path without notes

Week 4: You can diagnose a channel that will not start and a full dead-letter queue from symptoms alone, using logs and status commands

Week 6: A TLS-enabled channel starts successfully and channel authentication rules block and allow connections exactly as intended

Week 8: You rebuild the entire lab from your own scripts in under 90 minutes and score at or above your target on a timed all-domain practice set