Posted: Thu May 07, 2009 8:27 am Post subject: Client channel PD
Knight
Joined: 29 Jan 2007 Posts: 500 Location: DC
Is there a way to analyze a client channel connection to determine a specific process id on the client platform connecting in on svrconn channel.
Have many client connection channels coming in from a server but can't determine the process making the connection. As there are many other mq processes on client platform.
Also doing stop chl(xyz) command on a client channel stops all connections with same name or puts them into stopping state ...
Client manual has no insight on adminining (how to stop client channels) and InterComm manual refers to Client manual. If a client app aborts and leaves channel up is disconnect interval only way it will go away? _________________ "Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding")
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
Using MQSC commands, you can't stop CLNTCONN channels, but you can stop instances of SVRCONN channel for a particular CONNAME. This will close the client channel MCA's at both ends.
The SVRCONN channel status on the qmgr side does not have process id of the client process but it does have a process name (RAPPLTAG), which may give a clue of the client app that is running.
On Windows, MQ client apps can be identified using Process Explorer, as they have AMQxxxx.dll loaded. _________________ Glenn
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum