Description of WebSphere MQ tasks
When a queue manager is running, you see some or all of the following batch jobs running under the QMQM user profile in the WebSphere MQ subsystem. The jobs are described briefly in Table 1, to help you decide how to prioritize them.
Table 1. WebSphere MQ tasks. Job name Function AMQALMPX The checkpoint processor that periodically takes journal checkpoints AMQCLMAA Non-threaded TCP/IP listener AMQCRSTA TCP/IP-invoked channel responder AMQCRS6B LU62 receiver channel and client connection (see note). AMQFCXBA Broker worker job AMQPCSEA PCF command processor that handles PCF and remote administration requests AMQRMPPA Channel process pooling job AMQRRMFA Repository manager for clusters AMQZDMAA Deferred message handler AMQZFUMA Object authority manager (OAM) AMQZLAA0 Queue manager agents that perform the bulk of the work for applications that connect to the queue manager using MQCNO_STANDARD_BINDING AMQZLAS0 Queue manager agent AMQZXMA0 The execution controller that is the first job started by the queue manager. It deals with MQCONN requests, and starts agent processes to process WebSphere MQ API calls AMQZMGR0 Process controller. This job is used to start up and manage listeners and services. AMQZMUC0 Utility manager. This job executes critical queue manager utilities, for example the journal chain manager. AMQZMUR0 Utility manager. This job executes critical queue manager utilities, for example the journal chain manager. RUNMQBRK Broker control job RUNMQCHI The channel initiator RUNMQCHL Sender channel job that is started for each sender channel RUNMQDLQ Dead letter queue handler RUNMQLSR Threaded TCP/IP listener RUNMQTRM Trigger monitor We can view all jobs connected to a queue manager, except listeners (which do not connect), using option 22 on the Work with Queue Manager (WRKMQM) panel. We can view listeners using the WRKMQMLSR command.