Re: trigger or listener?

    Hi Rich,

    Our alternative, for the reason you describe and others, is to use
messaging and message queues.


                                                         Joe Sam

Joe Sam Shirah -        http://www.conceptgo.com
conceptGO       -        Consulting/Development/Outsourcing
Java Filter Forum:       http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International?    http://www.jguru.com/faq/I18N
Que Java400?            http://www.jguru.com/faq/Java400


----- Original Message ----- 
From: "Rich Duzenbury" <rduz-midrange@xxxxxxxxxxxxxxxxxxx>
To: "Java Programming on and around the iSeries / AS400"
<java400-l@xxxxxxxxxxxx>
Sent: Saturday, October 15, 2005 11:21 PM
Subject: Re: trigger or listener?


> On Wed, 2005-10-05 at 17:02 -0500, Glenn Holmer wrote:
> > On Wednesday 05 October 2005 11:50, Jose Luis Calvo wrote:
> > > One way to do that is using the best of the two alternatives, the
> > > trigger (may be in RPG) put an entry in a DTAQ, an have a Java
> > > program waiting in that DTAQ.
> >
> > Thanks for the replies; we're going to set up a trigger against the
> > database on the '400 that writes the record into a data queue.  A
> > program on the Linux server will read from that queue and write the
> > record into his (Postgres) database.  I'll let you know how it turns
> > out...
> Be careful with a data queue.  If your updates are important, I would
> discourage using it.  The reason is that if there are any data queue
> entries hanging around when the system ends (either normally or
> abnormally), they are cleared during the IPL.
>
> All the triggers I write save to a database file, and are pulled from
> there.  It's a bit more resource intensive, but IMO, safer.
>
> Regards,
> Rich
>