Process in MQ

AMQRRMFA:-

The repository process (for clusters).

Description:-
AMQRRMFA can end abruptly when two or more cluster receivers are
defined with the same name within the same cluster.

RUNMQLSR:-
The channel listener process.
Description:-
Use the RUNMQLSR command to start a listener process.
This command is run synchronously and will wait until the listener process has
finished before returning to the caller.

RUNMQCHI:-
The channel initiator process.
Description:-
Use the runmqchi command to run a channel initiator process.
The channel initiator is started by default as part of the queue manager.

AMQPCSEA:-
The command server.
Description:-
PCF command processor that handles PCF and remote administration
requests .

AMQHASMX:-(its in V5.3 and amqzmuc0 in V6)

Logger Process.
Description:-
Logger process amqhasmx (amqzmuc0 in V6) could eventually run out
of file descriptors some time after a disk full condition.
Logger process amqhasmx (amqzmuc0 in V6) could eventually run out
of file descriptors some time after a disk full condition

AMQHARMX:-(its in V5.3, amqzmuc0 in V6)

Log formatter,used only if the queue manager has linear logging .
Description:-
If the disk holding the log files for a queue manager becomes-full,
then the log formatting process amqharmx (amqzmuc0 in V6)may (correctly)
report probe HL062054, HL049110 and HL062054FDCs (error code
hrcE_MQLO_DISK), with FDCs also from the
logger process amqhasmx (amqzmuc0 in V6).

This condition may introduce a permanent state within the logger

whereby log files need to be renamed. Each rename leaks a file descriptor,
leading to eventual file descriptor exhaustion within the logger, which will get
reported via a large variety of FDCs, depending on where it is encountered.

Note that log files do not normally need to be renamed.

A workaround is to ensure that the queue manager is recycled if the
log formatter ever reports disk full (hrcE_MQLO_DISK) FDCs. Local fix
Recycled asap if the logger ever reports lack of disk space (the
hrcE_MQLO_DISK error code).

AMQZLLP0:-
Checkpoint processor.

Description:-
Like, amqzllp0 is the checkpoint processor that checkpoints all information at regular
intervals pertaining to the happenings within the queue manager.

AMQZLAA0:-
Queue manager agents.
Description:-
The amqzlaa0 processis is that there is one thread in an amqzlaa0
process which is responsible for each MQCONN connection handle. To avoid one
process with all the threads in, they are limited, so after 64 (default), we launch
another process to handle the next one. When a MQDISC disconnect occurs, the
thread is finished with and will (roughly, ignoring any cache/wait for reuse) end.
When all threads are gone, the process can end .

AMQZFUMA:-
Object Authority Manager(OAM process).
Description:-
Queue managers running the OAM store authorization data on a local
queue, called SYSTEM.AUTH.DATA.QUEUE. Authorization data is managed by the
amqzfuma process (amqzfuma.exe for Windows systems) .

AMQZXMA0:-
Processing controller.
Description:-
 AMQZXMA0 process (the execution controller) which is responsible
for creating the default objects.

AMQRRMFA:-
Repository process (for clusters)
Description:-
During the startup of the queue manager, the Cluster Repository
process (amqrrmfa) terminates when the Channel parameters are incorrectly
specified. The queue manager reports the missing amqrrmfa process and stays in
'starting' state. However, the earlier versions of WMQ (prior to v6.0.2.0) logs
AMQ9224 error and the queue manager starts normally.

AMQZDMAA:-
Deferred message processor.
Description:-
Because of this change in user id, the deferred message handler
(amqzdmaa process) fails to process messages, because the user id of messages
available in SYSTEM.PENDING.DATA.QUEUE and the user id under which the queue
manager processes are running do not match.

AMQQMPPA:-
Channel pooling
Description:-
AMQRMPPA will normally process up to 64 channels until you have
100*64 channels running at which point each AMQRMPPA will get loaded up to
100 channels. However, each AMQRMPPA may have many more than 64 queues
open .

AMQZXMA0:-
AMQZXMA0 process (the execution controller) which is responsible for
creating the default objects.

AMQZFUMA:-
MQ Object Authority Manager (security)
Description:-
AMQ5008: An essential WebSphere MQ process 4427 (amqzfuma)
cannot be
found and is assumed to be terminated.

It is very likely that the UNIX group for the userid who is trying to launch the MQ
Explorer does not exist in the local machine and a placeholder number is being
used.
For example, when you use "ls -l" on files in the home directory of the user, there
is a number, such as 102, instead of a group name.
This is the MQ Object Authority Manager process

Resolving the problem:

The root user should ensure that the placeholder group number
for the user in question is a fully registered group for the local machine, such as in
the /etc/group file.

AMQXLAA0:-
The prime process for the SPVI was IBM MQ Series LQM Agent
(amqzlaa0).
(Local Queue Manager)
Description:-
Well the simple approximate answer to the amqzlaa0 process's is
that there is one thread in an amqzlaa0 process which is responsible for each
MQCONN connection handle. To avoid one process with all the threads in, they are
limited, so after 64 (default), we launch another process to handle the next one.
When a MQDISC disconnect occurs, the thread is finished with and will (roughly,
ignoring any cache/wait for reuse) end. When all threads are gone, the process
can end.

AMQZLSA0:
handles socket connections to the queue manager

Description:-
The amqzlsa0 process is the local queue manager (LQM) socket agent
main program. It handles socket connections to the queue manager when the
application to queue manager connection is set to isolated bindings. If Default
Bind Type is set to ISOLATED, then applications and the queue manager run in
separate processes, and no resources are shared between them.

AMQZMUR0:
restartable process manager

Description:-
Amqzmur0 and Amqzmuc0 are the two processes that are
responsible for logging the transaction information into the log files. These are
called restartable (mur0) and critical (muc0) processes respectively.

AMQRMPPA:-
process pooling process and journal utility manager

Description:-
The common listener process is “runmqlsr”. This listens for the
incoming requests and hands over the request to a process called “amqrmppa”,
also called channel pooler. This is a threaded process and based on the number of
requests, more number of“amqrmppa” process will be spawned.
On the remote end, “amqrmppa” works on behalf of the application and returns
the service. Here is the simplified flow:
Application interacting directly with a queue manager:
APPLICATION ---> AGENT --->QMGR RESOURCES
Application connecting to a queue manager through another queue manager:
APPLICATION ---> SENDING MCA ---> RECEIVING MCA(LISTENER/AMQRMPPA) --->
AGENT ---> QMGR RESOURCES
Application connecting to a queue manager over CLIENTCHANNEL:
APPLICATION ---> TCP/IP ---> LISTENER/AMQRMPPA ---> AGENT---> QMGR
RESOURCES

AMQRRMFA:-
the repository process (for clusters)

Description:-
The repository information are stored in the form of messages inside
SYSTEM.CLUSTER.REPOSITORY.QUEUE. "amqrrmfa"is the process, called
repository process. This process is responsible for retrieving information from
the repository queue, updating the information, etc.

AMQZDMAA:-
deferred message processor
Description:-
The AMQZDMAA job will still go through a cycle of being shut down
and periodically restarted, until the Object Catalogue is repaired (for example, by
quiescing the
Queue Manager, deleting the Catalogue and restarting the Queue
Manager).

AMQPCSEA:-
the command server
Description:-
The Command Server (amqpcsea) is not running but all other
processes are
running. Applications and channels already connected are working but no new
connections or applications can start.

This is the command server process.

End the processes in the following order:

amqzmuc0 Critical process manager amqzxma0 Execution controller
amqzfuma OAM process amqzlaa0 LQM agents amqzlsa0 LQM agents
amqzmur0 Restartable process manager amqrmppa Process pooling process
amqrrmfa The repository process (for clusters) amqzdmaa Deferred message
processor amqpcsea The command server