Roger, Perhaps as the "Messaging Architect" you can request that they first develop a messaging API that must be used by all developers. This API, based on the values of environment variables, would be able to log anything and/or everything you might want it to at a particular time. Not only would this externally controlled logging system make a great debugging tool for developers, it would probably prove invaluable in shooting down a real program bug that only raises its ugly head under very specific circumstances and only in production.
I have implemented APIs like this for different clients in different messaging / store-and-forward systems more times than I care to remember. Each time, this simple interface has saved our butts during a real production problem. Each time, it proved the messaging system was working flawlessly, and that there was some other problem with the application - complex-conditional logic errors, errant pointers, "dynamic" static data, and compiler optimization errors, just to name four. Dave A. -----Original Message----- From: Roger Lacroix [mailto:[EMAIL PROTECTED] Sent: Thursday, April 29, 2004 11:16 AM To: [EMAIL PROTECTED] Subject: Re: Message Tracking Hi, I fully agree with you but sadly as the 'Messaging Architect' for one division I do not have the authority to request or mandate anything. I can only recommend things. I have written WMQ Naming Standards documents and WMQ Programming Standards documents for the client but it just goes over the newbie's head. So, this may be a difficult solution but it will give me fewer headaches. :) Regards, Roger Lacroix Capitalware Inc. http://www.capitalware.biz Quoting "Benjamin F. Zhou" <[EMAIL PROTECTED]>: > Roger, > > you seem want to show them evidence that THEY are nuts. it probably won't > work that way. Beside, with the time you need for one or more evidence > collector, you could have long taught all of them enough to be good-enough > MQ-developers. > > cheers, > > Benjamin F. Zhou > Technical Specialist > Messaging&Integration Supp. > Mercedes-Benz USA > x.2474 > > > > Roger Lacroix > <[EMAIL PROTECTED] To: > [EMAIL PROTECTED] > ALWARE.BIZ> cc: > Sent by: MQSeries Subject: Message Tracking > List > <[EMAIL PROTECTED] > C.AT> > > > 04/28/2004 11:48 PM > Please respond to > MQSeries List > > > > > > > All, > > I have tried to talk my current client into buying a message tracking > product > but of course they say they don't have the money!?!?! > > The problem is that the client has a lot of MQ development going on with a > lot > of newbie MQ/Java developers. And of course the newbie developers keep > telling > me that MQ lost their messages. This of course is driving me nuts!!! > > So I figured that I would create an API Exit to log the following: > - Queue Name > - Date / Time > - MsgID > - CorrelID > - GroupID > > >From a tracking point of view, I don't think logging the message data is > important but what other fields of the MQMD should be logged?? > > I figure I would use Perl or Java to summarize or correlate the information > in > the log file. Of course, the script would cross search between MsgID, > CorrelID > & GroupID for matches. > > Any comments - thoughts about this. > > Regards, > Roger Lacroix ===== David A. Awerbuch, IBM Certified MQSeries Specialist APC Consulting Services, Inc. Providing Automated Solutions to Business Challenges West Hempstead, NY (516) 481-6440 [EMAIL PROTECTED] __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
