We run 1 qmgr (v6.0.2.4) on sles10 with to many queues on there. (We are splitting up to more then one qmgr)
In the near past we had a problem with a long running transaction that filled up our log files (and so disk space). This caused our qmgr to hang.
Now, the problem got fixed by contacting IBM (To find that long running transaction) but in the future I would like to be able to find that long running transaction myself.
Is there a simple tool to track down long running transactions from the logfiles/queue files or anything?
Just to close this toppic:
Found a way to track down the guilty process/app.
Connect to the qmgr with runmqsc and run command
"display conn(*) ALL" (And specify down to the connection needed)
or
Use mqmon to connect to your qmgr.
Open the connection list, add the log extent column and here you can see which connection uses which log file. Connection leads to app/process.
With adding the UOW columns you can see more details. _________________ Regards
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