Re: Support for API exits?

[Antony Boggis]

Title: Message

Ok, after much gnashing of teeth and pulling of hair I have the API exit working on WMQ 5.2 (CSD06).

 

There seems to be some issues if the queue manager whch the exit is to be used is set to auto start under Windows. I haven't fully investigated at this point. Setting the queue manager to manual start and then issueing the strmqm/strmqcsv works fine, then using the Services MMC to start the listener so that is properly runs in the background.

 

I found that for my purposes caputuring the MQPUT BEFORE and the MQGET AFTER, gives me all the data in and out of the server. I also modified the sample exit to only shown where Environment == MQXE_MCA_SVRCONN so that I only get data coming from clients across the server-connection channel.

 

Thanks to David for the pointers.

 

Tony Boggis.

(Newly) IBM Certified Solution Developer -- WebSphere MQ V5.3

-----Original Message-----
From: David C. Partridge [mailto:]
Sent: Friday, July 25, 2003 1:15 AM
To: [EMAIL PROTECTED]
Subject: Re: Support for API exits?

Tony,

 

The following are the minimum levels of MQ at which IBM will support the API crossing exit:

 

Solaris    MQ 5.2 CSD03

 

Windows NT etc, AIX, HP_UX, Linux, OS/400 etc     WebSphere MQ 5.3

 

It was actually shipped (as against supported) on most (if not all) the distributed platforms at MQ 5.2 CSD03.

 

Dave

-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED]On Behalf Of Antony Boggis
Sent: 24 July 2003 23:25
To: [EMAIL PROTECTED]
Subject: Support for API exits?

What is the minimum level of MQ for API exit support. Specifically under Win2000.

I have WMQ 5.2, CSD06. The sample API exit is there, but the amqmdain admin application and the MMC Services snap-in don't have the necessary support.

Any pointers?

tonyB.