MQSeries.net :: View topic

JuulV · Posted: Mon Mar 23, 2009 8:04 am Post subject: Asynchronous PUT and the API Exit

Hi,

A question on WMQ 7.0 features and the API Exit that I am hoping an API Expert or Hursley development person can shed some light on ...

With the introduction of the MQPMO_ASYNC_RESPONSE option, MQPUT(1) calls no longer have to wait until WMQ finished all of the PUT processing (including eventual hardening to disk, logging...), but with the consequences that:

(a) MQCC/MQRC both being zero no longer guarantees that messages really have been put; and
(b) that it often even will be impossible to tell which messages have been put or not (if I read the doc correctly, the only exception here is: if multiple persistent messages are written under syncpoint, and one of them fails, all fail when the COMMIT is attempted).

Given above, I'm looking for some advice on how to handle this in "alert generators" and "queue replicators" (Cressida has software in both these areas):

Should such softwares simply bypass these messages, as at the time that the PUT(1) call is processed, it's impossible to tell whether the message will eventually be produced or not?
Or should an alert be generated/the message be replicated, because the caller had the clear intention to produce the message?

Or????

All opinions are warmly welcomed,