UNIX and Linux: ps -ef | grep amq interpretation
From Version 7.1, the interpretation of the list of IBM® MQ processes that results from filtering a scan of UNIX or Linux® processes has changed. The results can show IBM MQ processes running for multiple installations on a server. Before Version 7.1, the search identified IBM MQ processes running on only a single installation of the product on a UNIX or Linux server.
The implications of this change depend on how the results are qualified and interpreted, and how the list of processes is used. The change affects you, only if you start to run multiple installations on a single server. If you have incorporated the list of IBM MQ processes into administrative scripts or manual procedures, you must review the usage.
Examples
The following two examples, which are drawn from the product documentation, illustrate the point.- In the product documentation, before Version 7.1, the scan was used as a step in tasks to change the installation of IBM MQ. The purpose was to detect when all queue managers had ended. In Version 7.1 or later, the tasks use the dspmq command to detect when all queue managers associated with a specific installation have ended.
- In the product documentation, a process scan is used to monitor starting a queue manager in a high availability cluster. Another script is used to stop a queue manager. In the script to stop a queue manager, if the queue manager does not end within a period of time, the list of processes is piped into a kill -9 command. In both these cases, the scan filters on the queue manager name, and is unaffected by the change to multiple installations.