Comments on: Stopping queue managers (when nothing else will) http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/ A place to talk with people who work on WebSphere MQ Sat, 28 Feb 2009 03:21:44 +0000 http://wordpress.com/ hourly 1 By: AIXπ » links for 2007-03-25 http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/#comment-174 AIXπ » links for 2007-03-25 Wed, 28 Mar 2007 19:07:43 +0000 http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/#comment-174 [...] Stopping queue managers (when nothing else will) « a Hursley view on WebSphere MQ (tags: by:dale_lane ibm websphere wmq) [...] [...] Stopping queue managers (when nothing else will) « a Hursley view on WebSphere MQ (tags: by:dale_lane ibm websphere wmq) [...]

]]> By: protocol7 » Blog Archive » links for 2007-03-24 http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/#comment-157 protocol7 » Blog Archive » links for 2007-03-24 Sat, 24 Mar 2007 12:18:05 +0000 http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/#comment-157 [...] Stopping queue managers (when nothing else will) (tags: ibm websphere wmq by:dale_lane) [...] [...] Stopping queue managers (when nothing else will) (tags: ibm websphere wmq by:dale_lane) [...]

]]> By: Franz Baumgartner http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/#comment-155 Franz Baumgartner Fri, 23 Mar 2007 13:36:24 +0000 http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/#comment-155 Thank you for the information. I recently opened a PMR to get the order of stopping a qmgr manually! The reason are discrepancies seen in SysAdminGuide and HACMP SupportPack MC91 (MQ v6). There is a good script in SupportPac MC91 (even if you don't have a HACMP installation, you can use it on Unix systems) to stop a qmgr in a sequence of controlled, immediate and preemptive commands waiting xx seconds for the next phase (command) to execute. The last brutal command is then to kill the qmgr processes using a process list of order. But this process list (including v5 and v6 processes) doesn't match the order in SysAdminGuide. IBM PMR stated, the SysAdminGuide is the right one, thus you have to reorder file hamqproc file matching SysAdminGuide order (see Dale's topic) See hamstart and hamqmstop scripts in MC91. Hope you can start and stop qmgrs without need to use last phase of killing processes. Franz Thank you for the information.
I recently opened a PMR to get the order of stopping a qmgr manually! The reason are discrepancies seen in SysAdminGuide and HACMP SupportPack MC91 (MQ v6).

There is a good script in SupportPac MC91 (even if you don’t have a HACMP installation, you can use it on Unix systems) to stop a qmgr in a sequence of controlled, immediate and preemptive commands waiting xx seconds for the next phase (command) to execute. The last brutal command is then to kill the qmgr processes using a process list of order. But this process list (including v5 and v6 processes) doesn’t match the order in SysAdminGuide.

IBM PMR stated, the SysAdminGuide is the right one, thus you have to reorder file hamqproc file matching SysAdminGuide order (see Dale’s topic)

See hamstart and hamqmstop scripts in MC91.

Hope you can start and stop qmgrs without need to use last phase of killing processes.

Franz

]]> By: Dale Lane http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/#comment-154 Dale Lane Fri, 23 Mar 2007 11:20:20 +0000 http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/#comment-154 The easiest way (and the way that is recommended in the Sys Admin Guide, I think) is to do a full process listing, filtered by the name of your queue manager. All queue manager processes will include the name of the queue manager in the full command. E.g. <code>ps -ef | grep QMNAME</code> This might cause you problems if you have similarly named queue managers (e.g. BOB and BOBBY - where doing a grep on "BOB" will show processes from both queue managers) In these circumstances, a more definitive way is to use <code>dspmq -c</code> which shows the PIDs associated with each queue manager. Hope that helps Dale The easiest way (and the way that is recommended in the Sys Admin Guide, I think) is to do a full process listing, filtered by the name of your queue manager. All queue manager processes will include the name of the queue manager in the full command.

E.g.
ps -ef | grep QMNAME

This might cause you problems if you have similarly named queue managers (e.g. BOB and BOBBY – where doing a grep on “BOB” will show processes from both queue managers)

In these circumstances, a more definitive way is to use dspmq -c which shows the PIDs associated with each queue manager.

Hope that helps

Dale

]]> By: Pankaj http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/#comment-153 Pankaj Fri, 23 Mar 2007 10:56:22 +0000 http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/#comment-153 Good Article. But most of the times i wonder which particular process belongs to which particular queue manager, if there are many other queue managers running and i want to stop only one particular queue manager. Is there any way to list/identify particular queue manager processes to kill? Good Article. But most of the times i wonder which particular process belongs to which particular queue manager, if there are many other queue managers running and i want to stop only one particular queue manager.

Is there any way to list/identify particular queue manager processes to kill?

]]>