Its a shame that a product as mature as MQ can't log who deleted a queue when, but it can give me 3 logs full of "Channel A started" "Channel A ending normally" plus about a million of those wonderful Connection-dropped-by-remote-peer TCP errors anytime some app ends without an MQDISC.
What's more important to the MQ Admin - the timestamp for an mq app ending in not the best way (but a way that the QM can handle 100%)? Or when and who changed the trigger interval to 5?
Mark, this capability needs to be present, ideally with an option as to whether you want it on or off, and what detail level. AMQERR01.LOG is great. How about AMQCONFG1.LOG? _________________ Peter Potkay
Keep Calm and MQ On
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
markt wrote:
Next time SupportPac MS0P gets updated (which will not be for a few weeks, when I'm back in the office) it will include the code to generate Command Events for PCF messages sent to the command server on the Distributed platforms - and the Explorer plugin in that SupportPac can also decode those events.
can you give us a heads up on when this update will take place? I would be happy to beta this one _________________ Michael
It's taken longer than I'd planned - too many road trips - but MS0P has now been updated with the Command Event API Exit and formatter. Also includes a little timestamp filtering.
just send me 2 MS03 output files and I will produce some demo output
Indeed it does. We've demo'ed MQDocument for this purpose and it works 100% as advertised. Highly recomended. It took a little scripting but every morning MQ Document emails me a report that shows what objects have changed in the last 24 hours (we run our MS03 and MQDocument jobs every 24 hours). _________________ Peter Potkay
Keep Calm and MQ On
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