Roger, I don't exactly agree with the link. I have always known an API exit as existing on Distributed platforms, and the API Crossing Exit being the exact same thing on the mainframe but for CICS only.
See the following quote from the MQ Glossary and Bibliography Manual: API exit. A user-written program that monitors or modifies the function of an MQI call. For each MQI call issued by an application, the API exit is invoked before the queue manager starts to process the call and again after the queue manager has completed processing the call. The API exit can inspect and modify any of the parameters on the MQI call. The API exit is not supported on WebSphere MQ for z/OS. API-crossing exit. A user written program that is similar in concept to an API exit. It is supported only by WebSphere MQ for z/OS and for CICS applications only. -----Original Message----- From: Roger Lacroix [mailto:[EMAIL PROTECTED] Sent: Thursday, April 29, 2004 12:02 PM To: [EMAIL PROTECTED] Subject: Re: Message Tracking All, I'll correct myself. :)) 'Api Crossing Exit' is the 'Api Exit' that I am referring to. Here is a quick explanation about it from IBM: http://www.mqug.org.uk/anonftp/021131%20-%20MQUTIL.pdf Regards, Roger Lacroix 416-566-7307 Capitalware Inc. http://www.capitalware.biz Quoting Roger Lacroix <[EMAIL PROTECTED]>: > Hi, > > Am I not sure but I believe 'Api Crossing Exit' is mainframe only. (Anyone!) > > Although, 'Api Crossing Exit' could be the 'Api Exit' that I am referring to. > Is it available on distributed platforms and configure at a queue manager > level > (and not channel attribute)? > > > Regards, > Roger Lacroix > Capitalware Inc. > http://www.capitalware.biz > > > Quoting [EMAIL PROTECTED]: > > > Roger, > > > > > > The api crossing exit which comes with WMQ addresses most of your concerns. > > Have you looked at it ? > > > > > > > > > > > > > > "Bullock, Rebecca > > (CSC)" To: > > [EMAIL PROTECTED] > > <[EMAIL PROTECTED] cc: > > > Subject: Re: Message > Tracking > > Sent by: MQSeries > > List > > <[EMAIL PROTECTED] > > n.AC.AT> > > > > > > 04/29/2004 08:49 > > AM > > Please respond to > > MQSeries List > > > > > > > > > > > > > > Roger, the only thing I have to say is to agree that you want to include at > > least part of the actual message data. That way, if the programmer has the > > wrong msgid or correlid or even ends up with duplicates (if, for example, > > he > > doesn't clear these fields before his next put), you stand a chance of > > finding the actual message based on the data itself. > > > > > > > > -----Original Message----- > > From: Roger Lacroix [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, April 28, 2004 11:48 PM > > To: [EMAIL PROTECTED] > > Subject: Message Tracking > > > > > > 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 > > > > 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 > > > > > > > > ************************************************************************** > > This e-mail and any files transmitted with it may contain privileged or > > confidential information. It is solely for use by the individual for whom > > it is intended, even if addressed incorrectly. If you received this e-mail > > in error, please notify the sender; do not disclose, copy, distribute, or > > take any action in reliance on the contents of this information; and delete > > it from your system. Any other use of this e-mail is prohibited. Thank you > > for your compliance. > > > > 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 > > > > > > > > > > > > > > > > This communication is for informational purposes only. It is not intended > as > > an offer or solicitation for the purchase or sale of any financial > instrument > > or as an official confirmation of any transaction. All market prices, data > > and other information are not warranted as to completeness or accuracy and > > are subject to change without notice. Any comments or statements made > herein > > do not necessarily reflect those of J.P. Morgan Chase & Co., its > > subsidiaries and affiliates. > > > > 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 > > > > 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 > 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 This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. 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
