A WebSphere MQ message queue, QMQMMSG, is created in each queue manager library. Operating system messages are sent to this queue when queue manager jobs end and WebSphere MQ sends messages to the queue. For example, to report which journal receivers are needed at startup. Keep the number of messages in this message queue at a manageable size to make it easier to monitor.
The following examples show how an unmodified WebSphere MQ installation works when some of the standard jobs are submitted at queue manager startup time.
The first job that is started is the execution controller, AMQZXMA0.
Neither of these job descriptions exist, so WebSphere MQ looks for job description AMQZXMA0 in the product library QMQM. This job description exists, so it is used to submit the job.
By default, the routing entry with sequence number 9900 has comparison data that matches QMQMRUN20, so the job is started with the class defined on that routing entry, which is also called QMQMRUN20.
The next job that starts is the checkpoint process, AMQALMPX.
Neither of these job descriptions exist, so WebSphere MQ looks for job descriptions AMQALMPX and QMQMJOBD in the product library QMQM.
Job description AMQALMPX does not exist but QMQMJOBD does, so QMQMJOBD is used to submit the job.
By default, the routing entry with sequence number 9910 has comparison data that matches QMQMRUN35, so the job is started with the class defined on that routing entry, which is also called QMQMRUN35.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
amqwag0244 |