I just can't resist asking - but isn't SYSTEM.CLUSTER.REPOSITORY.QUEUE just
a database of clustering info and SYSTEM.AUTH.DATA.QUEUE a database of
authorisation profiles? Tut tut   :-)

Regards
John.

PS. Please don't move this info into UDB - I like it the way it is...

-----Original Message-----
From: Paul Clarke [mailto:[EMAIL PROTECTED]
Sent: 21 August 2003 14:54
To: [EMAIL PROTECTED]
Subject: Re: Syncpoint question


Dave,

Don't tell me you're using a queue as a database ? tsk tsk     :-)

Paul G Clarke
WebSphere MQ Development
IBM Hursley





                      "David C.
                      Partridge"                To:
[EMAIL PROTECTED]
                      <[EMAIL PROTECTED]        cc:
                      RIMEUR.COM>               Subject:  Syncpoint question
                      Sent by: MQSeries
                      List
                      <[EMAIL PROTECTED]
                      .AC.AT>


                      21/08/2003 14:30
                      Please respond to
                      MQSeries List





A colleague of mine has raised a question which suggests there may be a
problem with a particular use of syncpoint processing.

Consider a queue containing a number of messages (say 3) each with a unique
correlid.   This queue is browsed by applications to extract certain
information.    There is also an update application.

The update application does a destructive get of the old messages and then
puts new messages all under a unit of work.   When the last new message is
put the whole UOW is committed.

My colleague is pretty certain that in this case there will be a window in
which a browsing application will not see a complete set of messages on the
queue (either old set or new set) and may in fact see no messages.   Is he
correct?

If he is correct, what is the best update strategy to ensure that a browsing
application will see either:

The old set of messages
or
The new set of messages

He has proposed the following as solution:

Do a sequential browse of all the existing messages (that are not control
messages) and record the message ids as a persistent control message on the
same queue using a correlid that won't occur in the messages of interest (we
can do this).

Put the new messages to the queue (either in or out of syncpoint)

Under syncpoint loop doing a destructive get of any control messages and
messages with message ids as specified in the data of the control message.

Commit.

Regards,
David C. Partridge
Security and MQ Products Manager
Primeur Group
Tel: +44 (0)1926 511058
Mobile: +44 (0)7713 880197

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


**********************************************************************

Click here to visit the Argos home page http://www.argos.co.uk

The information contained in this message or any of its attachments may be privileged 
and confidential, and is intended exclusively for the addressee.
The views expressed may not be official policy, but the personal views of the 
originator.
If you are not the intended addressee, any disclosure, reproduction, distribution, 
dissemination or use of this communication is not authorised.
If you have received this message in error, please advise the sender by using your 
reply facility in your e-mail software.
All messages sent and received by Argos Ltd are monitored for virus, high risk file 
extensions, and inappropriate content. As a result users should be aware that mail 
maybe accessed.

**********************************************************************

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

Reply via email to